Typically, the first time you connect to a network, Windows 10 will ask you to set a network profile. If someone could shed some light onto why the IP settings required that system variables be there, would be most helpful.How to set a network profile using Settings Once I added these two item and rebooted, I was then able to go back into the IP Settings and define STATIC definitions, reboot and reenter the definitions and they remained, so now the problem appears to be fixed. Soooo I went and edited START => CONTROL PANEL => SYSTEM => ENVIRONMENT VARIABLES => SYSTEM VARIABLES => Path Statement and realised that there was no definition for %SystemRoot% or %SystemRoot%\System32 This morning when I was going thru your suggestions and getting errors, I realised among other things that whenever I had to enter any commands from DOS Prompt I had to actually be in the direfctory that the command existed.!! Expand Components, expand Network, and then click Protocol This installs (amongst other things) netdiag (command line network tool)Ģ. The next thing after that is to install support tools from the XP cd root/Support/Tools run the setup.exe (choose a complete install). We are looking to see that the Winsock2 is not corrupted by any LSP that the Broadcom software or any other app may have added to winsock and stuffed it. The section headings will include the following names if the Winsock2 key is undamaged: You will have ten sections under Protocol.
Next follow these steps and post the output:Ĭlick Start, click Run, type Msinfo32, and then click OK.Ģ.Ğxpand Components, expand Network, and then click Protocol
I'm grasping at straws a bit here while I try and think of something better, but it's worth a try. Hmm, ok first try in a command window ipconfig/release (to release the DHCP lease) then open Local Area connection properties and set the static address.
0 kommentar(er)
