Networking DOA: Unidentified Network, Access: Local Only

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Upgraded from RC2 to RTM a week or so ago. Networking was working fine for a
week and then after a reboot the network is no longer accessible.

Network adapter reports: "Unidentified Network" and "Access: Local Only".
Trying to renew DHCP fails and the adapter gets assigned a private IP (169).
Disabling/reenabling the adapter makes no difference as does uninstalling and
re-installing it.

Also saw some posts elsewhere suggesting checksum issue (someone else who
had the problem ran a network sniffer and observed all outbound packets had
zero checksum) or power mode issue (Windows powering off the adapter when
entering low power mode and not resuming it) so I tried disabling both TCP/IP
checksum offload and also removing permission for Windows to power off the
adpater when entering sleep mode; neither resolved the issue. Saw another
post saying that putting the PC into sleep mode and then resuming temporarily
(until next reboot) solved the issue but this does not work for me either.

Adpter is a Broadcom NetXtreme Gigabit Ethernet, driver is b57xp32.sys,
v9.52.0.0, 15 May 2006.
 
Hi Barb,

First off, thank you for answering. At least now I know my posts aren't
going into the proverbial bit bucket!

Everything was just peachy until after the reboot and nothing in my network
configuration has changed but to answer your question regarding network
configuration.

The PC in question is connected (wired) to a Linksys BEFSR41 router running
as a hub. The Linksys hub is in turn connected (wired) to a BT 1800HG DSL
router (rebranded 2Wire router) providing DHCP service to the LAN.

There are two other computers connected (wired) to the Linksys hub and two
other computers connected to the BT router (1 wired, 1 wireless).

Network access from all of the boxes is fine. Even networking on the box on
which I have installed Vista works fine WHEN the box boots Windows XP
Professional off a separate partition. When it boots Vista RTM networking is
dead.

Note that Vista reports that the router is on but is not responding and
suggests checking the firewall, further adding that if it is a Windows
firewall then I should check the SymNetDrv Firewall Filter
OUTBOUND_TRANSPORT_V4 setting.

Even though I knew it was barking up the wrong try I humored it and disabled
the Windows firewall on the Vista box as well as the firewall on the router
and was not surprised that this made no difference at all.

I'll post another reply in a minute with any relevant event log entries
after i've rebooted the box into Vista. (I'm posting from that box now,
booted into Win XP).


Dave Bonnell
Corporate Architect
BMC Software, Inc
http://www.bmc.com/
 
you posted earlier that the driver was "Adpter is a Broadcom
NetXtreme Gigabit Ethernet, driver is b57xp32.sys,
v9.52.0.0, 15 May 2006"

seems like that is a fairly old driver. was this in the build? in
RTM? have you tried updating the driver?

Hi Barb,

I booted the box into Vista again, cleared all of the event logs and then
rebooted to get a fresh set of events. The only non-information events in
the logs where from NTP failing.

I then opened up System Information and it says that the adapter's driver is
stopped. Not much chance of things working if the driver isn't even running
I guess. Why it is stopped and how to get it started again I have no idea.
Its start mode is also Manual - not sure if that is normal.

I ran the network diagnosis tool, disabled/re-enabled the adapter but same
result. Nothing outstanding in the event logs from this action either.


-Dave
Click to expand...
--

Barb Bowman
MS Windows-MVP
Expert Zone & Vista Community Columnist
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
 
Hi Barb,

No, that driver was not part of the RTM image nor available on Windows
Update. I downloaded it separately from Broadcom's web site. (Ditto for
SATA raid drivers). That was the latest driver available at the time (and as
I said, worked fine for Beta 2, RC2 and even RTM for a while before it
suddenly stopped) but I see there is an update (11/01/2006) which i'll pull
down and try now.


-Dave
 
I just installed the latest driver from Broadcom's web site ...
xp_2k3_32-9.81d (service=b57w2k, driver=b57xp32.sys), v9.81.0.0, 11/10/2006.
No change ... network still "Unidentified Network" with "Access: Local Only"
after rebooting and System Information still reports that the b57w2k service
is "Stopped".


-Dave
 
Thanks for the info ... a little late for me but hopefully it will save
somebody else the pain of a complete re-install of Vista, which is what I
ended up doing after hitting a brick wall here 3 months ago.


-Dave
 
without seeing an ipconfig /all text output we can only guess

http://digitalmediaphile.wordpress.com/ipconfig-all-how-to-get-text-output/

before you post it, unbind IPv6 - see directions at
http://digitalmediaphile.wordpress.com/ipv6-how-to-unbind-from-a-nic-in-windows-vista/

if that does not work, I'd recommend replacing that router. In fact,
I'd recommend that you replace it anyway as it does not provide you
with proper security.



I tried snnoopy's fix and I am still in a "Local only" state with a
(private network). Here is my situation:

Just out of the box Dell Inspiron 1520 laptop with the Dell Wireless
1395 WLAN Mini-Card Rev 2.10. The Access Point is a Linksys BEFW11S4 ver
2.
After four hours today on the phone with Dell and Linksys, I now have
the latest driver for the WLAN Mini-Card and the latest firmware for the
Linksys access point, but still no connectivity.

I have one desktop and two other laptops, all running XP with good
wireless access (for a couple of years). It is the new laptop with Vista
that cannot successfully connect.

Any further suggestions?

Kelly
Click to expand...
--

Barb Bowman
MS-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
 
do you have the latest driver for the wireless?
http://support.dell.com/support/dow...-1&impid=-1&formatcnt=1&libid=5&fileid=236824

are you broadcasting the SSID ?

you really should replace that router. I don't have any other
recommendations.

I tried the unbind but that made no difference. Here is the IPCONFIG for
your comment:

Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Rachelsnana>ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : MMsDellLaptop
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : sd.cox.net

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : sd.cox.net
Description . . . . . . . . . . . : Dell Wireless 1395 WLAN
Mini-Card
Physical Address. . . . . . . . . : 00-16-44-75-72-6C
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.102(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Sunday, February 10, 2008
1:44:43 PM
Lease Expires . . . . . . . . . . : Monday, February 11, 2008
1:44:42 PM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 68.105.28.11
68.105.29.11
68.105.28.12
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling
Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 7:

Connection-specific DNS Suffix . : sd.cox.net
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . :
fe80::5efe:192.168.1.102%15(Preferred)
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 68.105.28.11
68.105.29.11
68.105.28.12
NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Users\Rachelsnana>
Click to expand...
--

Barb Bowman
MS-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
 
I read through and tried everything in this post thread to fix the same issue
on a friend's laptop. Unfortunately none of these suggestions worked. What
finally worked for me was to remove Norton 360 using the Norton Removal Tool
(http://www.softpedia.com/progDownload/Norton-Removal-Tool-Download-26173.html).
Once that product was removed from the laptop, all networking issues were
resolved. If you're still having an issue with this error in Vista, look at
your Internet Security Software first and if removing that doesn't work then
try the suggestions in this post.
 
I too am now having this issue. I have internet on my laptop (XP), gained
wirelessly through my linksys broadband wireless/wired router. I got my Dell
XPS (Vista 64, SP2) in July. It has a wired connection that worked fine up
until 2 days ago. I restored back before some update that came out and have
rebooted several times. Tried snoopy's suggestion, but every time I reboot, I
am right back on a "public network" despite having set it to private each
time. I already reset the router - and like I said I'm responding now via my
wireless connection through my laptop.

The only thing that has been out of the ordinary is that 2 times in the last
week my XPS has gotten "hung up" - lights are all on though it should have
shut down into sleep mode and the monitor won't recognize the PC.

I have a ton of work I need to do on my desktop - which is the powerhouse -
but I absolutely need the Internet access to get to my server to do any of my
work in the first place...
 
I think this may be my issue... I'll post and let you know if it works...
Incidentally, I now have "private" showing, but no internet. ipconfig shows
no entry in default gateway
 
I went to http://support.microsoft.com/default.aspx/kb/933872 thinking that
might be my issue. Nope... I downloaded the fix to my laptop, used the
sneakernet to get it to my desktop, and it said "This update does not apply
to your system" despite it being 64bit Vista. whatev?!
Incidentally, I have no default gateway in my ipconfig - for IPv4 or IPv6
(both set to detect...) in my desktop..
 
I have a similar problem. I have a home office wireless/wired network. Router
connected to SuddenLink's cable modem.
I am writing from my laptop which has internet wirelessly & wired - I
checked both.
I have a Mac attached to the same network. I have internet there as well.
My new Vista 64bit machine that I got in July has worked fine and I haven't
had any networking issues with it. I plugged the cable in and it was ready to
go...
Now, as of 2 days ago, I have no internet, and am connected to a public,
"unidentified network" with limited and local access. I cannot connect to my
other computers anymore either.
Troubleshooting I have done:
* I have taken wired connections from the laptop/Mac, known to be working,
and plugged them in the Vista machine. Not the cable.
* I uninstalled the driver for the NIC card. When restarted, it detected the
adapter and reinstalled the drivers. Not the NIC card.
* I pinged 127.0.0.1 with success. I can ping the auto IPv4 address
169.254.247.64 with success. I get error code 1231 with 192.168.1.1 (router) .
* I had all the auto stuff selected for both IPv4 & IPv6, so I did the
opposite... I put in all the manual DNS/gateway entries (192.168.1.103 –
laptop was on 101 & 102, 255.255.255.0, and the 2 DNS entries it had listed).
When I ipconfig it still shows an auto configuration for IPv4 at
169.254.159.231 and a subnet mask of 255.255.0.0 and no gateway. I did a
release and a renew. Same thing. I check the device manager & it still has my
manual entries. Incidentally, I had made the change AGAIN to “private†vs.
“public†for my unidentified, local, limited network. Nothing. So I restart.
I'm back where I started: I’m “public†with the same autoconfiguration
numbers and in the device manager my IPv4 is again set on Obtain
Automatically versus the manual entries I had saved. Every time I reset the
network to "private", it resets itself back to public after a restart.
* I did a netsh int ip reset and a netsh winsock reset
* I have unplugged both the router and the modem and even reset the router
and reconfigured.
* I restored to the last system checkpoint before the issue occurred - which
incidentally was before some Windows update was installed (hmm...)

I'm lost - and I don't know who to call. It doesn't appear to be a hardware
problem (Dell or LinkSys) or an internet problem (SuddenLink), but it could
be a software problem (Microsoft) to which I have found NO SOLUTION to on the
Web.

Windows IP Configuration

Host Name . . . . . . . . . . . . : Desktop_PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
Physical Address. . . . . . . . . : 00-24-E8-2E-F8-0B
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::2042:5e15:1b17:f740%14(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.247.64(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 301999336
DHCPv6 Client DUID. . . . . . . . :
00-01-00-01-11-E7-66-1D-00-24-E8-2E-F8-0B

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area
Network)
Physical Address. . . . . . . . . : 00-1E-4C-E6-3B-5C
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{5B680CC4-9A63-4F62-973A-09897CABC
F74}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 7:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 13:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{3D7B80A9-A9D7-4AA7-9C97-A840E55A5
E11}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
 
Back
Top