"Ghost network" serious network adapter bug

[Kossu]

Hello,

Whenever I reboot my computer the network adapter has the tiny yellow mark on it displaying that theres limited or no connection. In network tab I can see 2 networks, 1 being my Home network like it should be and then there a ghost network called unidentified network. I cannot delete or poke at this network at all. While this network is active theres no connection to the internet. However I can access my router page and what not on local lan, and according to the package amount the connection works perfectly fine, it just doesnt load any actual webpages or is capable of connection to the internet.

See the pictures below to get a better picture of this. Only way to fix this temporarly is to disable and then enable the network connection, the ghost network will then go away and the network connection works fine, so how the hell can I remove this network permanently?

Thanks.

(build is 7100 atm, but it happend on earlier builds as well)

 

[Digger]

wired or wireless?

go to start type cmd... then type in "ipconfig /all" (without quotes) copy and paste that info here

 

[Digger]

also, my next suggestion would be to install the drivers for your network card from the manufacturer.

next suggestion... fill out your system specs

 

[TimMintz]

I am having EXACTLY the same problem. I tried installing the manufacturer drivers as you suggest and so far seems to be working. W7 showed a 10x driver and Broadcom had an XP rated 11x driver and it came up fine on the first reboot. Also of note I had to manually tell it to install the driver I wanted. It wanted to keep the other one.

Below are my system's stats and the ipconfig/all results. Maybe it will help someone else.
I've changed the ID info by the way.

Dell Optiplex 745
Intel Pentium D CPU 2.80GHz 2.79GHz
4.00 GB (3.24 GB usable)
Windows 7 32-bit Operating System
Broadcom NetXtreme 57xx Gigabit Controller



Microsoft Windows [Version 6.1.7100]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Tim & Tricia>ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Tim-Tricia-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Controlle
r
Physical Address. . . . . . . . . : 00-18-8B-0F-E9-9B
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : xx00::0000:x000:00x0:00x0%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.3.138(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Sunday, May 03, 2009 3:30:59 PM
Lease Expires . . . . . . . . . . : Monday, May 04, 2009 3:30:58 PM
Default Gateway . . . . . . . . . : 0.0.0.0
192.168.3.1
DHCP Server . . . . . . . . . . . : 192.168.3.1
DHCPv6 IAID . . . . . . . . . . . : 234887303
DHCPv6 Client DUID. . . . . . . . : 00-00-00-00-00-0x-00-00-00-00-0x-0x-x0-x0

DNS Servers . . . . . . . . . . . : 192.168.3.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{998xx888-x67x-44xx-x47x-23485x4xxxx0}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

C:\Users\Tim & Tricia>

 

[TimMintz]

Well that didn't fix it.
The same problem is back.

Any more insight you could provide would be greatly appreciated.

Tim

 

[Digger]

I am having EXACTLY the same problem. I tried installing the manufacturer drivers as you suggest and so far seems to be working. W7 showed a 10x driver and Broadcom had an XP rated 11x driver and it came up fine on the first reboot. Also of note I had to manually tell it to install the driver I wanted. It wanted to keep the other one.

Below are my system's stats and the ipconfig/all results. Maybe it will help someone else.
I've changed the ID info by the way.

Lease Obtained. . . . . . . . . . : Sunday, May 03, 2009 3:30:59 PM
Lease Expires . . . . . . . . . . : Monday, May 04, 2009 3:30:58 PM
Default Gateway . . . . . . . . . : 0.0.0.0
192.168.3.1
DHCP Server . . . . . . . . . . . : 192.168.3.1
DHCPv6 IAID . . . . . . . . . . . : 234887303
DHCPv6 Client DUID. . . . . . . . : 00-00-00-00-00-0x-00-00-00-00-0x-0x-x0-x0

DNS Servers . . . . . . . . . . . : 192.168.3.1
NetBIOS over Tcpip. . . . . . . . : Enabled

the 0.0.0.0 there puzzles me... why its alongside the 3.1. Can you verify that you have the correct gateway (filled in) in the tcp/ip settings of that adapter?

 

[TimMintz]

Everything is set to automatic, tcp/ip etc.

Here it is again. I just re-ran it a couple minutes ago.

IPv4 Address. . . . . . . . . . . : 192.168.3.138(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Monday, May 04, 2009 7:00:59 PM
Lease Expires . . . . . . . . . . : Tuesday, May 05, 2009 7:00:59 PM
Default Gateway . . . . . . . . . : 0.0.0.0
192.168.3.1
DHCP Server . . . . . . . . . . . : 192.168.3.1
DHCPv6 IAID . . . . . . . . . . . : 234887307

Below is after I disable and then enable the adapter and have internet access. Also of note is that I DO have local intranet access in the first (above) scenario.

IPv4 Address. . . . . . . . . . . : 192.168.3.138(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Monday, May 04, 2009 6:10:52 AM
Lease Expires . . . . . . . . . . : Tuesday, May 05, 2009 6:10:52 AM
Default Gateway . . . . . . . . . : 192.168.3.1
DHCP Server . . . . . . . . . . . : 192.168.3.1
DHCPv6 IAID . . . . . . . . . . . : 234887307

Thanks again for your help.

Tim

 

[deepfry]

I experience the same issue with the RC (it did not happen with the beta), my mainboard is an old MSI K7N2 that has the nforce 2 chipset and nforce ethernet card. I tried loading up the xp drivers I had but that didn't work, and the only way I am able to get around it is either disable and then re-enable the network adapter or just hibernate my computer when it's not in use. I am thinking of either trying a re-install of the RC or maybe finding different drivers from somewhere else....I used to have drivers that worked just fine on vista but I'm not sure where I got those now.

 

[Digger]

Internet Connectivity Evaluation Tool

 

[TimMintz]

Test 5 - UPnP Support Test Not supported

Result: The operating system is Windows Vista
The firewall is enabled
Exceptions are allowed by the firewall
UPnP is enabled by the firewall
UPnP services are running
UPnP Discovery is enabled
Detecting Internet Gateway Devices on the network
0 IGD(s) found
Failed to find any Internet Gateway Devices




All other Tests passed as Supported.


Tim

​

 

[johngalt]

FWIW - Since last week, in build 7077, I have been having a similar issue - on resuming from sleep / booting up the machine whatever, the NIC loses all connection to the Internet. This continues for about 10 minutes, after which all of a sudden it is there.

I just installed the RC a couple of nights ago, and thus far it does not seem to be doing it anymore - we'll see....

 

[jimbo45]

Hi all
99.99999% of problems like this aren't Router problems since often the problem doesn't exist in XP or even Linux based systems.

Unless your Router is "Donkeys years old" I would almost bet a zillion dollars to a bucket full of **IT that it's a network adapter problem -- particularly if the adapter is an "Integrated" one made by REALTEK or the VIA VELOCITY FAMILY GIGABIT ethernet type.

Often Windows reports these as working in device manager but you can't get any connectivity and it shows unknown network.

However your's is slightly a strange case as you at least get what looks like a proper LAN address, althoough the gateway address seems strange.

Try as an experiment to set the IP, DNS and default gateway manually and see what happens.

Then try switching off IPV6.

If neither of these work you've had it -- incompatble adapter. A get around is to use a really cheap USB==>LAN adapter (costs around 3 - 5 USD) if you want to use a wired lan on a laptop or use a wireless card. (You could also use the USB adapter on a desktop if you can get access to a USB2 port.

Enc picture of such a device.

(Believe me spending 3 - 5 USD is far better than trying to get a "recalcitrant" adapter to work).

Cheers
jimbo

 

[The Patient]

Same problem here. A temporary solution which works in my case is to open Network and Sharing Center, click Change Adapter Settings (near the top of the left hand pane), and disable and then re-enable the adapter. You'll have to do this again when you reboot, but at least you'll get Intertubes access til then.

YMMV. =)

Strangely, this problem occurs on a Dell Dimension E520, but not on a Dimension 4700 sitting right next to it, both of which have Intel cards. A third custom-built PC with a Realtek card doesn't have the problem either.

 

[Digger]

Strangely, this problem occurs on a Dell Dimension E520, but not on a Dimension 4700 sitting right next to it, both of which have Intel cards. A third custom-built PC with a Realtek card doesn't have the problem either.

I dont think that this is a strange problem at all. I've been doing a lil homework here recently. I take it that the E520 is the oldest of the pc's? (Forgive me as i kno nothing bout dells, wont touch'em). Ok, if so, what adapter is that pc using compared to the other dell pc? I'm sure even if its the same manufacturer its gotta be an older model, right. Next question, did windows install a 7 signed driver for that adapter on the E520?

 

[Digger]

FWIW - Since last week, in build 7077, I have been having a similar issue - on resuming from sleep / booting up the machine whatever, the NIC loses all connection to the Internet. This continues for about 10 minutes, after which all of a sudden it is there.

I just installed the RC a couple of nights ago, and thus far it does not seem to be doing it anymore - we'll see....

what kind of adapter john, model? did 7 install a driver for it in 77, if not how bout the RC?

 

[The Patient]

Digger -- Dells aren't my first choice either, but when someone's upgrading and offers me two free PCs, well ... it's hard to look a gift horse in the mouth, especially when I just need a couple of low-end media servers.

The 4700 actually predates the E520 by a couple of years, I think.

The 4700 has an Intel Pro/100 VE card, driver date 11/16/2007, version 8.0.47.1, signed by Microsoft (this one works fine).

The E520 has an Intel 82562V card, driver date 3/26/2009, version 9.13.4.10, signed by Microsoft (this one has the "ghost network" problem).

 

[Digger]

Digger -- Dells aren't my first choice either, but when someone's upgrading and offers me two free PCs, well ... it's hard to look a gift horse in the mouth, especially when I just need a couple of low-end media servers.

dont take that as bad, i just hate proprietary systems is all. I actually have a dell collecting dust that one day i hope to put home server on and sit in a closet. Couldnt tell you the model of it either, i know its a dino tho.

The 4700 actually predates the E520 by a couple of years, I think.

The 4700 has an Intel Pro/100 VE card, driver date 11/16/2007, version 8.0.47.1, signed by Microsoft (this one works fine).

The E520 has an Intel 82562V card, driver date 3/26/2009, version 9.13.4.10, signed by Microsoft (this one has the "ghost network" problem).

the driver date wouldnt necessarily mean that its an older card per se. tho its an indicator of that, but if dell decided to write a driver for that card because it was a popular system they sold, when they got their hands on win7, and maybe they havent wrote a new one for the 4700 as it maybe wasnt a widespread selling system and/or the demand for a newer driver is not needed/warranted.

my point of this is that i wondered if the E520 did have a newer "7ish" type driver. If not then i my next question was going to be how did you install, and what kind of driver did you install. But, looks like that may not be an issue. Also tho, you can look at it as maybe since thats a new driver for the E520, this is the reason for the issues you are seeing as well, bugs not flattened out yet for the newer driver.

a thought...

 

[viesoft]

Same

I am having the same problem. Not with Beta, but now with RC1. Net adapter is Intel PRO/100 VE. Random times, but usually when I reboot, i have the 'limited or no connectivity' icon, and two networks are present. One of them is the 'Unidentified' ghost network. The ipconfig reveals perfectly legimite settings, pulling a 192.168.1.* addy from the DHCP, correct gateway, correct DNS. To fix it, I have to go into network adapters, disable LAN, and re-enable it. This usually clears it up. What's up? This could be a deal breaker for Win 7 for some people.

 

[andych]

This could be a deal breaker for Win 7 for some people.

Why would it be a Deal Breaker for Win 7?

This would get back to similar "I hate Vista" mentality of a few years back.
Vista itself was fine....the fact that hardware manufacturers were slack with drivers initially gave Vista a bad rap.

It is not a Win 7 fault......everything is pointing at a driver issue for certain NIC's.

For the cost of a USB - Lan adapter or for that matter a PCI Lan card may solve your problem once and for all....

Also try sending in feedback to Microsoft and see what their response is....

 

[viesoft]

Not For Me

Let me explain myself. It would not be a deal breaker for me. I LOVE Windows 7. However, with the current public image of Microsoft to the 'not know much' consumer ... something like 'My internet doesn't work' is WAY too noticeable and bothersome of a problem, regardless of the underlying reason why. You know that the logical, behind-the-scenes reasoning of why something won't work never matters to the average pc user. They will only see that their internet does not work, and they will blame Microsoft. This is my only point.
​