i have a win 7 machine with an Atheros L1 Gigabit Ethernet 10/100/1000Base-T Controller with latest drivers, the machine is upto date with all latest fixes etc. I have it connecting to a WRT310Nv2 router. Seemingly random, win 7 disconnects from the "Home Network" says its in a "public network", then resets the connection to an illegal 169 address. I have tried static ips, dhcp, all with the same results. This seems to have started shortly after i installed Vuze, so I uninstalled it but the problem persists. I know that the router is sound given that I have an XP machine attached with no issues of connectivity at all. I am at a complete loss and have tried everything, pleasse tell me i'm not the only one.
Tell me more
×
Super User is a question and answer site for
computer enthusiasts and power users. It's 100% free, no registration required.
|
|
I would try working my way up the OSI model starting with Layer 1.
With what you have said about trying everything, you probably did everything software wise. Most people don't think about changing out the cable. The copper wires in the CAT5/e cable could have been pulled out of the connector due to simple bending; or the cable could have been bent too much in one area, which would cause the connection to fade. With fiber cable, the cable can be bet very slightly and the connection will fade. I have had this happen at my data center before. Good Luck - |
||||
|
|
|
OK I want to make sure I understand this, even if you set a static IP on that interface it will still reset back to DHCP and 169.x.x.x? |
|||||||||
|
|
Is this the only NIC? In other words, is this a laptop with a wireless NIC as well as a wired NIC or a desktop with only wired NIC? Does this happen when you connect to a different port on the router - preferably one you know is good? |
|||
|
|
|
I haven't seen the behavior that you describe, but you might want to check through the advanced settings for your driver in the Device Manager to make sure you don't have any power-saving settings enabled for the NIC. I've seen a few cases where the NIC seemingly randonmly "goes to sleep" because it decides it's time to save some power. |
|||
|
|
|
Have you tried rolling back your system to before you installed Vuze? I had a similar problem after installing Adobe CS3 on my system. It turned out that the bonjour service that was installed with the software was causing the problem. I disabled the service, reboot the machine, and it started working again. I personally hate Bonjour, but to be fair, it was a 2-3 year old version of it. So make sure you have the latest version, and check for new services or startup commands that were installed with Vuze. Hope that helps. |
|||
|
|
|
It can have relationship with UPnP. Windows 7 use it for discover network. Try use non windows firewall to block upnp, i think it is UDP packet port 80 and not authorized incoming connections. Or you can try bootable linux distro. If it works it is not hardware problem. |
|||
|
|
