The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.

Windows 7 - Unidentified Network

RohanRohan Registered User regular
This is driving me up the wall. My desktop has a problem where it drops it's net connection every now and then. It's connected via ethernet cable to a Netgear DG834G router, which has an ADSL connection. I'm pretty sure I've posted about this before, but the problem keeps cropping up no matter how many times I fix it - the fix is always temporary. Windows reports an unidentified connection, gives the lan connection an IP of 169.167.xxx.xxx or whatever, then allows me access to the network, but not the Internet.

Looking around the 'net for this issue finds other people in the same boat, and there are several potential fixes. They are -

1. Some Apple service that comes with iTunes or QuickTime apparently causes this problem, and uninstalling it solves it. I don't have either installed.

2. Assign an IP address to the IPv4 protocol in adapter settings.

3. Do the above, then tell Windows to automatically assign an IP address.

4. Give the network adapter a network address.

5. Uninstall/reinstall/install new versions of the drivers for your network card.

6. Disable/enable the adapter.

7. Resetting the TCIP/IP stack.

The fixes that work most often involve assigning an IP address, then telling the computer to automatically assign one, and giving the adapter a network address. But the problem keeps re-appearing, and I'm to the point of tearing my hair out trying to solve it. I'm using the Atheros AR8121/AR8113/AR8114 network adapter that comes with my motherboard (Asus P5Q Pro).

This problem came up once on our media pc (also connected via ethernet) and simply assigning it a network address solved the problem, and it's not had a problem since then (four months ago). But the same problem just keeps cropping up on my desktop pc. I don't think it's my adapter as it'll be working fine for a while and then all of a sudden, in the middle of a browsing session for example, it'll happen. My flat-mate has the exact same motherboard in his machine and he hasn't experienced the problem yet. I've had both XP and Vista installed on this pc and they never had any such problems. It might not happen for months, I'll forget all about it, and then bang, it's back.

Searching the 'net tells me that it is a Windows 7 problem that has something to do with "the issue is that the ROUTE table contains a phantom persistent default route 0.0.0.0 to one of the network interface cards. This activates the "Unidentified Network" (Public) every time the network connection becomes active. Sharing permissions are turned off." I've no idea what this means; I'm technically competent with pc's (I've been building them for years) but this Microsoft network gobbledegook goes way above my head.

If any of you fine gents could help, I'd be very grateful.

...and I thought of how all those people died, and what a good death that is. That nobody can blame you for it, because everyone else died along with you, and it is the fault of none, save those who did the killing.

Nothing's forgotten, nothing is ever forgotten
Rohan on

Posts

  • ZxerolZxerol for the smaller pieces, my shovel wouldn't do so i took off my boot and used my shoeRegistered User regular
    edited March 2010
    The software that comes with iTunes/QuickTime that can cause this is called Bonjour, a zeroconf application. It's not exclusive to either product, so check remove apps on the control panel to make sure. (A buddy of mine had this happen to him at a LAN because, the night before, he installed Gizmo, which autoinstalled Bonjour.)

    Needless to say, I'm extremely weary of any Apple software on Windows.

    Zxerol on
  • RohanRohan Registered User regular
    edited March 2010
    Yeah, cheers man, already checked for that little program multiple times - it's definitely not on my system.

    Rohan on
    ...and I thought of how all those people died, and what a good death that is. That nobody can blame you for it, because everyone else died along with you, and it is the fault of none, save those who did the killing.

    Nothing's forgotten, nothing is ever forgotten
  • stigweardstigweard Registered User regular
    edited March 2010
    If it's not a laptop, I'd set a static ip outside of the dhcp range of the router (but still in the same subnet). It sounds like there is a problem in the chain there somewhere. It could be a port on a switch, the dhcp server on the router, a bad cable, a bad nic, or a flaky driver.

    eg: Router normally gives out an ip between 192.168.2.2-100. Then use 192.168.2.101 with a netmask of 255.255.255.0 and set the gateway to the ip of the router.

    stigweard on
  • mfc144mfc144 Registered User regular
    edited March 2010
    I've had the same/similar problem.
    I have a D-Link router.
    For me it would happen if my machine went to sleep/hibernates. When it woke up, it would get some weird ip address, and it would say Unidentified Network, and I would have no internet access. If I right clicked the little taskbar icon and selected troubleshoot, it almost always resolved it.
    My solution was to change the power settings to not allow it to sleep anymore.
    Sorry I don't have much more in the way of a solution. I hope you're able to figure it out.

    mfc144 on
  • RohanRohan Registered User regular
    edited March 2010
    I doubt it's the router, because there are three other pc's hooked up via ethernet and apart from the media pc one time months ago, none of them are having this problem. Will give it a try, though, thanks.

    Rohan on
    ...and I thought of how all those people died, and what a good death that is. That nobody can blame you for it, because everyone else died along with you, and it is the fault of none, save those who did the killing.

    Nothing's forgotten, nothing is ever forgotten
  • Mr. ButtonsMr. Buttons Registered User regular
    edited March 2010
    The likely problem is a bad NIC (I'll assume that you've done things like switching the used port on the router and possibly tried using another ethernet cable... I'll also assume that you've followed the steps you listed in the OP). The likely solution is to just install a new NIC and not have to worry about this problem any more. Thankfully these things are cheap and shouldn't run you more than $15. Install new one, disable onboard one (in your BIOS I believe), and you should be good to go.

    Mr. Buttons on
  • Lezard ValethLezard Valeth Registered User regular
    edited March 2010
    The likely problem is a bad NIC (I'll assume that you've done things like switching the used port on the router and possibly tried using another ethernet cable... I'll also assume that you've followed the steps you listed in the OP). The likely solution is to just install a new NIC and not have to worry about this problem any more. Thankfully these things are cheap and shouldn't run you more than $15. Install new one, disable onboard one (in your BIOS I believe), and you should be good to go.

    This. The IP address 196.169.x.x is a fabric default address used when the NIC is unable to connect to the network.

    Lezard Valeth on
    firma1m.th.jpg
Sign In or Register to comment.