limited or no connectivity bug

Ubergrendle · Jan 4, 2005, 02:45 PM

Has anyone here suffered from the infamous "limited or no connectivity" bug with Windows XP SP2?

I just build an Athlon 64 3000+ system for my bro-in-law... Asus A8V Deluxe board... gigabit onboard.

Fully tested the system at my house, via my router and DSL. No issues. Downloaded all the service packs etc.

Take it to his house, try to setup the cable connection (direct connect) -- the cable modem never gets a receive signal. Drivers are installed properly, card is working...just won't send a signal.

I tried all the obvious stuff... reconfiguring, changing from DHCP to static IP and back...flush the winsock, unload/reload the driver, different driver versions, recycle the cable modem. Grrrr. I know this is not a mac-address issue (some ISPs cache the MAC address to prevent frequent swapping) as there is no signal leaving the ethernet card.

Lots of research has indicated that htis problem is systemic with WinXP sp2. I've got a short list of items to try, but all seem fairly cosmetic. The patch I downloaded + registry fix from Microsoft did not work either.

I'm wondering if other DH'ers have experienced this glitch? What did you do to fix it?

mkk · Jan 4, 2005, 03:19 PM

That the networking in XP+SP2 reports "limited or no connectivity" does not necessarily mean that there is any problem. If everything seem to work then just unmark that notification in the properties for that connection. For instance just being in the IP range 169.254.x.x will trigger the notification even if the network is doing well.

Ubergrendle · Jan 4, 2005, 03:59 PM

Quote:

Originally Posted by mkk

That the networking in XP+SP2 reports "limited or no connectivity" does not necessarily mean that there is any problem. If everything seem to work then just unmark that notification in the properties for that connection. For instance just being in the IP range 169.254.x.x will trigger the notification even if the network is doing well.

Thanks for your comment... I know that a 'false positive' can occur with the new network notification icon. Unfortunately the cable modem is not receiving any signal from the ethernet port. And I know the cable modem is working, since it works on the old P3 system sitting beside it.

Iridium · Jan 4, 2005, 04:10 PM

Quote:

Originally Posted by mkk

That the networking in XP+SP2 reports "limited or no connectivity" does not necessarily mean that there is any problem. If everything seem to work then just unmark that notification in the properties for that connection. For instance just being in the IP range 169.254.x.x will trigger the notification even if the network is doing well.

Interersting to know, I have seen this problem over at the inlaw's house and had no idea what was going on, they had full access with no speed loss to speak of. I will have to do some poking around and see if that is what it is all about.

mkk · Jan 4, 2005, 06:49 PM

Quote:

Originally Posted by Ubergrendle

Unfortunately the cable modem is not receiving any signal from the ethernet port. And I know the cable modem is working, since it works on the old P3 system sitting beside it.

Check if the ethernet port seem to be working in a local network. If it does, check if the card is set to automatically identify the type of connection and what it ends up at. Or if it is manually set to a certain mode(device manager). In most cases I've seen a cable modem does best at 10Mbit half duplex mode, wich should normally be set correctly by automatic identification.

Judas · Jan 4, 2005, 07:26 PM

This is a well known issue, if the machine was setup on a a router or another connection, and then moved to a new connetion without doing the nessary steps to get it to work, you end up with those problems..

Try this:

disconnect the power from your cable modem, then boot the computer, after which, go to start>Run and type CMD

now type this:

ipconfig /release

hit enter and it should release. Now plug your cable modem back in and wait a good minute (or better) just to make sure that the cable modem has gone through ALL it's startup functions and is attempting to get connectivity.

At this point, see if you have any connectivity. If nothing, open run and cmd

type:

ipconfig /renew

hit enter and wait a few second.. attempt to connect again. If nothing, i'd suggest rebooting your computer at this moment... IT should work, if not, you may have a bad ethernet cable.

riles9262 · Jan 4, 2005, 07:42 PM

ya you need to power cycle the modem as it's memory is likely still seeing the mac address of your other nic (on the other comp). Just disconnect the power for ten secs or so and plug it in, then reboot or do an ipconfig/renew after a couple mins.

PangingJr · Jan 4, 2005, 09:26 PM

this's very well known problem in the Google newsgroups, many of them points to the Windows Firewall settings, but some have reported that didn't help resolving the problem, some says deselect the Client for Microsoft Networks in network connections/properties helps them. and also, likes the others have already mentioned above.

Ubergrendle · Jan 5, 2005, 03:16 AM

thanks for your comments... unfortunately i've done most of what you've all suggested.

Judas, i've done the ipconfig release/renew, after reboots, with a recycled cable modem.

Ctrl-Alt-Del, i'll try monkeying with the Microsoft Networking settings. That's a tip I haven't read yet.

Will keep you apprised.

Jan 4, 2005, 02:45 PM	#1
Ubergrendle Semper ubi sub ubi Join Date: Nov 2004 Location: Toronto Posts: 702 Rep Power: 51	limited or no connectivity bug Has anyone here suffered from the infamous "limited or no connectivity" bug with Windows XP SP2? I just build an Athlon 64 3000+ system for my bro-in-law... Asus A8V Deluxe board... gigabit onboard. Fully tested the system at my house, via my router and DSL. No issues. Downloaded all the service packs etc. Take it to his house, try to setup the cable connection (direct connect) -- the cable modem never gets a receive signal. Drivers are installed properly, card is working...just won't send a signal. I tried all the obvious stuff... reconfiguring, changing from DHCP to static IP and back...flush the winsock, unload/reload the driver, different driver versions, recycle the cable modem. Grrrr. I know this is not a mac-address issue (some ISPs cache the MAC address to prevent frequent swapping) as there is no signal leaving the ethernet card. Lots of research has indicated that htis problem is systemic with WinXP sp2. I've got a short list of items to try, but all seem fairly cosmetic. The patch I downloaded + registry fix from Microsoft did not work either. I'm wondering if other DH'ers have experienced this glitch? What did you do to fix it? __________________ Veteran of the PC Microchannel / EISA wars of the late 1980s.

Jan 4, 2005, 07:42 PM	#7
riles9262 Driverheaven brewmaster Join Date: Oct 2002 Location: British Columbia, Canada Posts: 4,842 Rep Power: 72 System Specs	ya you need to power cycle the modem as it's memory is likely still seeing the mac address of your other nic (on the other comp). Just disconnect the power for ten secs or so and plug it in, then reboot or do an ipconfig/renew after a couple mins. __________________ A beer a day keeps the doctor away.

Jan 5, 2005, 03:16 AM	Thread Starter #9
Ubergrendle Semper ubi sub ubi Join Date: Nov 2004 Location: Toronto Posts: 702 Rep Power: 51	tried most of it thanks for your comments... unfortunately i've done most of what you've all suggested. Judas, i've done the ipconfig release/renew, after reboots, with a recycled cable modem. Ctrl-Alt-Del, i'll try monkeying with the Microsoft Networking settings. That's a tip I haven't read yet. Will keep you apprised. __________________ Veteran of the PC Microchannel / EISA wars of the late 1980s.

Jan 4, 2005, 03:19 PM	#2
mkk Cthulhu/Dagon 2012 Join Date: Oct 2003 Location: Gefle, Sweden Posts: 4,495 Rep Power: 132 System Specs	That the networking in XP+SP2 reports "limited or no connectivity" does not necessarily mean that there is any problem. If everything seem to work then just unmark that notification in the properties for that connection. For instance just being in the IP range 169.254.x.x will trigger the notification even if the network is doing well.

Jan 4, 2005, 09:26 PM	#8
PangingJr Member Join Date: Mar 2003 Posts: 5,989 Rep Power: 71	this's very well known problem in the Google newsgroups, many of them points to the Windows Firewall settings, but some have reported that didn't help resolving the problem, some says deselect the Client for Microsoft Networks in network connections/properties helps them. and also, likes the others have already mentioned above.