limited or no connectivity
Posted 18 September 2004 - 10:22 PM
Posted 01 October 2004 - 09:39 PM
just go to network connections
right click on lan, properties
and remove check at bottom to notify when limited or no connectivity
Posted 04 October 2004 - 12:41 PM
While all my clients are calling me day and night, I cant wait any longer for that stupid fix. Im just going to format the HDD and waste 40 hrs of work... all thanks to Microsoft!
Thanks for nothing Billy!
Posted 07 October 2004 - 04:10 PM
Posted 11 October 2004 - 12:06 PM
Posted 11 October 2004 - 12:59 PM
Posted 14 October 2004 - 09:23 PM
Posted 15 October 2004 - 10:33 AM
Posted 21 October 2004 - 06:35 AM
Problem fixed without touching computer with this message.
Posted 23 October 2004 - 09:38 PM
No need to do anything else.
The main problem is the 169.254.x.x address after installing XP SP2.
For a safer side you can also reset the router (like unplug from wall and plug it in)
Posted 25 October 2004 - 11:08 AM
Posted 27 October 2004 - 12:00 AM
Thanks Bill for a load of rubbish in SP2!
Posted 27 October 2004 - 06:12 PM
Hope this helps someone.
Posted 01 November 2004 - 10:47 PM
here is the fix to the problem...
forget applying the patch fix for SP2
Just uninstall SP2, it really just got the firewall software from Microsoft, not really worth having. As I am sure you would have your own firewall software.
I have a sneaking suspicion that Microsoft has treaked the code for DHCP handling in SP2. So another way to get around this would be to hardcode the IP address of your PC using private IP addresses.
For fool-proof, just use 192.168.0.1~192.168.0.255 with subnet mask 255.255.255.0
Posted 03 November 2004 - 11:07 PM
I have been dealing with the same issues since updating to SP2. And only one other person noticed the same thing, it seems the DHCP Server isn't working right, or not compatible with something. I have trekked all over the net searching and following every thread.
Many say it worked for me and this and that. Well not here.
The winsocksfix doesn't work...I resetted TCP/IP which microsoft says TCP/IP cant be uninstalled and installed so this resetting of TCP/IP is how they achieve the same action.
The regpatch didn't help.
What I have noticed though, is DHCP isnt working so XP assigns this alternative IP which is how XP knows to display 'Limited or no connectivity'...when it see's that IP a flag goes up and we have a warning.
Though surfing the net with this warning present, my surfing didn't appear to suffer...I went to some sites to benchmark dloading of 200mb files to see xfer rate, and I was doing 378kb /s using a DSL modem.
Manually configuring a static IP works! But really all that is really doing is being as that other address isnt used a flag doesnt go up.
So using 192.168.1.x just lets XP know everything is normal.
BUT, during my escapades in trying to resolve this issue using the winsocksfix and the regpatch and resetting tcp/ip and so on, at one point my surfing capabilities suffered greatly.
Going to google.ca would 50% of the time result in the page could not be loaded...and going to other big pages with java, a lot of the buttons wouldnt load so you had to refresh so that more data would get cached till you could get all the components on that page.
Uninstalling SP2 is a big mistake as you will be exposed to spyware and trojans and virus' that will exploit security vulnerabilities. SP2 patches these security holes.
Besides that isnt a solution, that is avoiding the problem.
My advise, don't play with these winsocksfix and registry patches and tcp/ip reset methods. Don't muck about because nothing is wrong except Microsofts own DHCP server. Just manually configure a static IP.
Right click on your NIC and go properties...select the tcp/ip internet protocol and go properties...on the general tab change the obtain ip address automatically and enter 192.168.1.2 or 192.168.2.2, either is fine, then the subnet 255.255.255.0
Thats it, dont go nowhere else close these and restart so things will be flushed and cleared and surf away.
Go to some broadband ISP site and go to technical support and do a speed test. just to verify everything is okay.
Even if you didn't make a static IP, and your connection warns the 'limited or no connectivity' message and did this speed test, you should find your service is not impaired.
But because DHCP is not working, it's not assigning an IP address, and if one doesn't get assigned then it uses the *damaged line* IP address of 169.254.216.51 and a subnet of 255.255.0.0
Its simply a reflex...simple logic...if DHCP doesn't assign an IP address then it must not be able to communicate with the modem...so the modem or cable must be damaged...but no, not the DHCP itself.
Posted 04 November 2004 - 03:42 PM
(netsh int ip reset resetlog.txt)-rebuilds tcp/ip
(ipconfig /flushdns)-flushes the dns
(ipconfig /registerdns)-registers dns, must be done after flushing
These commands may work, also you could try to rebuild the nic.
Posted 04 November 2004 - 07:43 PM
The netsh basically reinstalls the TCP/IP Stack.
Posted 07 November 2004 - 12:07 PM
Just one thing to add: in addition to IP address and subnet mask, make sure you also specify a default gateway (the IP address of your router ie. probably 192.168.1.1). I didn't do this at first and could connect to my router, but not get on the internet. Was very scared at first that this solution didn't work either, but after a bit of playing around it now seems to be fine... fingers crossed.
Posted 12 November 2004 - 11:02 AM
I tried all remedies without any luck. The sp2 patch KB884020 with the regfix, resetting IP stack with the netsh.. command. But with no luck. Even configuring my wireless adapters with a fixed IP didn't help.
But, just now, i saw some ligth at the end of (my) tunnel. I changed the SSID of my wireless network and... I was able to connect both machines in no time to the new SSID. Did several repairs and restarts only to find out that IP addresses were being acquired correctly.
Now I even changed back the net SSID to the old one and both portables are able to connect without any problem, properly receiving their IP address from the dhcp server.
I'will keep on diagnosing this problem, and keep my findings posted here.