Problem: The user reported that she could no longer get to her e-mail or to the internet. "It just stopped working 2 days ago and has not worked since."
Solution: Initial investigation revealed that her network connection was in that new limbo state, reporting that the local connection had "Limited or no connectivity". I think this is new with XP SP2, but I can't say with certainty (That would mean I'd have to do a little research which in turn might require me to read something. No way). Anyhow, I've seen this a couple of times, now, both involving machines that were set to get IP addresses from DHCP. In both cases the machines had "169" addresses, meaning they couldn't contact the DHCP server. Also, in both cases the problem boiled down to a bad network port.
Whatever, this new state of "Limited or no connectivity" does me no good, so far. For me, "Limited or no connectivity" has equated to NO connectivity. I spent a lot of time trying to detemine if there was something I could do to cure the problem. Both times I encountered this I couldn't even ping the default gateway, let alone the DHCP server. So, I think we would be better off if we just got the old familiar red X on the network icon, indicating that the connection is just plain broken. But, that's just my limited opinion.......
Thursday, October 21, 2004
Subscribe to:
Post Comments (Atom)
1 comment:
To fix that. re-enable the NIC in device manager and then remove the check for show icon when there is limited or no connectivty by right clicking on the conection in network connections and going to properties...
Post a Comment