Quote:
Originally Posted by Lord Nikon
Try these commands from an ADMINISTRATOR command prompt (Click on Start, All Programs, Accessories then RIGHT CLICK on Command Prompt, then click on 'Run as Administrator')
netsh int reset all
(you will get a command prompt back in a couple of seconds with nothing visible reported, this is normal)
netsh winsock reset
(you will get a message telling you to reboot, this is normal, reboot the machine and then try connecting to the network again)
The problem is sometimes caused by a corrupt TCP/IP stack or Corrupt Windows sockets layer (winsock) - those commands above cause the windows system to reinitialise those layers and fix the problems caused by them. The 169.254 IP is a default IP when DHCP acquisition of an IP address has failed.
|
Many thanks Lord Nikon, I tried these but still had problems, I did an SFC and it came up with tons of files that couldn't be repaired, it also failed to load the desktop a number of times and kept blue screening.
I thought I might as well just restore it using the mfr's restore utility and that did the trick...
Goodness knows what the owner had done to it!!
Join CF
You are here: 
