Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows VistaWindows XPWindows MeWindows 98Windows 95Virtual PCInternet ExplorerOutlook ExpressWindows MediaSecurity
Related Topics
MS Server ProductsMS OfficePC HardwareMore Topics ...

Windows Forum / Windows Vista / Networking / May 2008

Tip: Looking for answers? Try searching our database.

Vista "local only" with 0.0.0.0 default gateway. Why Microsoft? Wh

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
DB - 13 Aug 2007 21:28 GMT
We're experiencing a problem on our company network, but only very
sporadically.  One machine will connect fine one day (wired and wireless),
but the next day show "local only".  Tried restarting, tried disabling and
reenabling the adapter (sometimes worked), uninstalled and reinstalled the
adapter, tried only
wired, tried only wireless, diabled IPv6...  The only thing I've noticed the
last two times this has happened is that our Default Gateway shows 0.0.0.0,
then right below that is the correct default gateway address.  I thought
maybe we were getting something weird from our 2003 servers.  However, I
switched to manual IP and put in the correct gateway.  It STILL showed
0.0.0.0 above the correct address.  The machines that connect okay do NOT
have 0.0.0.0 listed anywhere.

We have two different computers with this problem.  Both have the Intel 1000
network card and the Intel Pro/Wireless 3945 with the most current drivers.  
We also have these cards connecting fine with XP.  Clearly Vista is hosing
something up.  I've seen lots of reports of this problem but nothing from
Microsoft.  Hopefully it will be fixed with tomorrow's updates.

p.s. all our machines have Vista Business.
Barb Bowman - 13 Aug 2007 21:38 GMT
does http://support.microsoft.com/default.aspx/kb/933872/en-us apply
to you?

>We're experiencing a problem on our company network, but only very
>sporadically.  One machine will connect fine one day (wired and wireless),
[quoted text clipped - 16 lines]
>
>p.s. all our machines have Vista Business.
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
DB - 14 Aug 2007 04:48 GMT
Barb, I'm praying that it does.  I'll give it a shot on one of the more
troublesome machines to see if it corrects the problem.  My guess is that it
does not as setting the IP manually doesn't correct it and uninstalling and
reinstalling the adapter does not either.  But with the other strange
networking problems, I wouldn't be too surprised to find it works.

> does http://support.microsoft.com/default.aspx/kb/933872/en-us apply
> to you?
[quoted text clipped - 25 lines]
> http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
> http://blogs.digitalmediaphile.com/barb/
DB - 15 Aug 2007 22:40 GMT
Barb, thanks for the effort.  This appears not to fix our problem.  Rebooting
after installing did clear up the problem, until the next hibernate.  A
restart after that did not resolve it either.

We search on and pray for Microsoft to get their stuff together.

> does http://support.microsoft.com/default.aspx/kb/933872/en-us apply
> to you?
[quoted text clipped - 25 lines]
> http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
> http://blogs.digitalmediaphile.com/barb/
Barb Bowman - 15 Aug 2007 23:27 GMT
Is there anything interesting in Event Viewer?

>Barb, thanks for the effort.  This appears not to fix our problem.  Rebooting
>after installing did clear up the problem, until the next hibernate.  A
[quoted text clipped - 31 lines]
>> http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
>> http://blogs.digitalmediaphile.com/barb/

--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
DB - 03 Sep 2007 20:46 GMT
Nothing.  The only thing that is consistent among them all is the 0.0.0.0
address above our correct default gateway when viewing ipconfig /all.  We've
installed a bunch of different updates since then and the problem persists.  
The strange thing is we see it more often on a LAN connection than wireless

> Is there anything interesting in Event Viewer?
>
[quoted text clipped - 40 lines]
> http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
> http://blogs.digitalmediaphile.com/barb/
Barb Bowman - 04 Sep 2007 11:31 GMT
can you disable wireless on one of the machines, reboot, and post
the text output of ipconfig /all showing one of these?

>Nothing.  The only thing that is consistent among them all is the 0.0.0.0
>address above our correct default gateway when viewing ipconfig /all.  We've
[quoted text clipped - 45 lines]
>> http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
>> http://blogs.digitalmediaphile.com/barb/

--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
DB - 08 Sep 2007 05:14 GMT
Barb, I'll get that the next time we run into the problem.  It hasn't been as
prevalent over the last two weeks.  Until then, my question is, why does
Vista have a "Local only" mode at all?  And since it is there, why isn't it a
configurable option?  In XP, if you can get on the network, you can get on
the network, meaning through the network to the internet.  I've never seen a
problem like this in XP.  What is the reason for this "feature" in Vista?

I could see having the private network/public network security settings
trying to keep the computer "safe".  But I don't see the point in not having
this a checkbox or setting somewhere. A popup saying you've connected to a
potentially unsafe network, would you like to stay "local" or something.  
Because basically, once you're on the network, communication takes place in
standard protocols (tcp/ip, http, ftp...).  Can you explain why this is
happening to so many people??

> can you disable wireless on one of the machines, reboot, and post
> the text output of ipconfig /all showing one of these?
Barb Bowman - 08 Sep 2007 12:42 GMT
it is really a reporting mode of the current state of available
connectivity. and as part of normal diags and repair, in network and
sharing, if there is an X between the edge device and the Internet,
clicking the X calls the built in options that will attempt to
discover and then fix what is wrong with the connection. it gets
more complex with a dual homed computer two active NICs. I really
need the text output of ipconfig /all. Please post this as a reply
now even if it is working.

>Barb, I'll get that the next time we run into the problem.  It hasn't been as
>prevalent over the last two weeks.  Until then, my question is, why does
[quoted text clipped - 13 lines]
>> can you disable wireless on one of the machines, reboot, and post
>> the text output of ipconfig /all showing one of these?

--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
DB - 03 Oct 2007 17:29 GMT
Barb, here are 4 versions of ipconfig /all.
Our problem with Vista seems to almost exclusively occur with our wired
network.  75+ Vista machines setup identically work fine 99% of the time.  
There are 4-5 that seem to be more problematic than others.  I rebooted the
machine and connected wired and wirelessly and it was working fine.  I then
hibernated it and woke it up and turned the wireless off.  No internet.  
Turned on the wireless, still not internet.  Removed the network cable,
internet came back instantly.  Plugged the network cable back in, internet
goes away.  There were times when the Network and Sharing Center reported the
connection as being Local and Internet, but no internet was actually
avaialble.  We still have the problem after a reboot about half the time.  A
bit troubling since rebooting used to fix the problem and it wouldn't occur
again until hibernation (we do have all available updates installed,
including the ones you had us try).  We had tried disabling IPv6 on this
machine with no effect.  It had been turned back on before we did this.

Here are the ipconfigs from each situation.  You can see the problem is the
0.0.0.0 default gateway placed above the real default gateway.  Please let me
know if we can provide further information or if you need any clarification.  
The user of this particular Vista machine is trying to trade it in for a Mac.

C:\Users\fffff>ipconfig /all
***Fresh reboot.  Wireless and Lan both connected, Internet fine.  No
hibernate yet***

Windows IP Configuration

  Host Name . . . . . . . . . . . . : faculty1077
  Primary Dns Suffix  . . . . . . . : siprep.org
  Node Type . . . . . . . . . . . . : Hybrid
  IP Routing Enabled. . . . . . . . : No
  WINS Proxy Enabled. . . . . . . . : No
  DNS Suffix Search List. . . . . . : siprep.org

Ethernet adapter Local Area Connection 3:

  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . : SonicWALL VPN Adapter
  Physical Address. . . . . . . . . : 00-60-73-EB-93-CC
  DHCP Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection:

  Connection-specific DNS Suffix  . : siprep.org
  Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network
Con
nection
  Physical Address. . . . . . . . . : 00-1B-77-3F-F6-B9
  DHCP Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes
  Link-local IPv6 Address . . . . . : fe80::90ce:e913:bb05:41f6%9(Preferred)
  IPv4 Address. . . . . . . . . . . : 10.1.4.56(Preferred)
  Subnet Mask . . . . . . . . . . . : 255.255.0.0
  Lease Obtained. . . . . . . . . . : Tuesday, October 02, 2007 10:36:09 AM
  Lease Expires . . . . . . . . . . : Thursday, October 04, 2007 10:36:08 AM
  Default Gateway . . . . . . . . . : 10.1.1.1
  DHCP Server . . . . . . . . . . . : 10.1.1.11
  DHCPv6 IAID . . . . . . . . . . . : 151001975
  DNS Servers . . . . . . . . . . . : 10.1.1.11
                                      10.1.1.23
  Primary WINS Server . . . . . . . : 10.1.1.23
  Secondary WINS Server . . . . . . : 10.1.1.11
  NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

  Connection-specific DNS Suffix  . : siprep.org
  Description . . . . . . . . . . . : Intel(R) PRO/1000 PL Network Connection
  Physical Address. . . . . . . . . : 00-E0-B8-BB-F9-7E
  DHCP Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes
  Link-local IPv6 Address . . . . . : fe80::813e:9089:9f16:ad20%8(Preferred)
  IPv4 Address. . . . . . . . . . . : 10.1.4.33(Preferred)
  Subnet Mask . . . . . . . . . . . : 255.255.0.0
  Lease Obtained. . . . . . . . . . : Tuesday, October 02, 2007 11:16:58 AM
  Lease Expires . . . . . . . . . . : Thursday, October 04, 2007 11:16:57 AM
  Default Gateway . . . . . . . . . : 10.1.1.1
  DHCP Server . . . . . . . . . . . : 10.1.1.11
  DHCPv6 IAID . . . . . . . . . . . : 201384120
  DNS Servers . . . . . . . . . . . : 10.1.1.11
                                      10.1.1.23
  Primary WINS Server . . . . . . . : 10.1.1.23
  Secondary WINS Server . . . . . . : 10.1.1.11
  NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 6:

  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . :
isatap.{A5EBC489-3343-4B8A-BF52-886DB5DAC
59B}
  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 . . . . . . . . . . . :
isatap.{A5EBC489-3343-4B8A-BF52-886DB5DAC
59B}
  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. . . . . . . . . : 02-00-54-55-4E-01
  DHCP Enabled. . . . . . . . . . . : No
  Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 17:

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

Tunnel adapter Local Area Connection* 18:

  Connection-specific DNS Suffix  . : siprep.org
  Description . . . . . . . . . . . : isatap.siprep.org
  Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
  DHCP Enabled. . . . . . . . . . . : No
  Autoconfiguration Enabled . . . . : Yes
  Link-local IPv6 Address . . . . . : fe80::5efe:10.1.4.33%22(Preferred)
  Link-local IPv6 Address . . . . . : fe80::5efe:10.1.4.56%22(Preferred)
  Default Gateway . . . . . . . . . :
  DNS Servers . . . . . . . . . . . : 10.1.1.11
                                      10.1.1.23
  NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Users\fffff>ipconfig /all
***return from hibernate. Wireless turned off, LAN connected. No Internet***

Windows IP Configuration

  Host Name . . . . . . . . . . . . : faculty1077
  Primary Dns Suffix  . . . . . . . : siprep.org
  Node Type . . . . . . . . . . . . : Hybrid
  IP Routing Enabled. . . . . . . . : No
  WINS Proxy Enabled. . . . . . . . : No
  DNS Suffix Search List. . . . . . : siprep.org

Ethernet adapter Local Area Connection 3:

  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . : SonicWALL VPN Adapter
  Physical Address. . . . . . . . . : 00-60-73-EB-93-CC
  DHCP Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection:

  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network
Con
nection
  Physical Address. . . . . . . . . : 00-1B-77-3F-F6-B9
  DHCP Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

  Connection-specific DNS Suffix  . : siprep.org
  Description . . . . . . . . . . . : Intel(R) PRO/1000 PL Network Connection
  Physical Address. . . . . . . . . : 00-E0-B8-BB-F9-7E
  DHCP Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes
  Link-local IPv6 Address . . . . . : fe80::813e:9089:9f16:ad20%8(Preferred)
  IPv4 Address. . . . . . . . . . . : 10.1.4.33(Preferred)
  Subnet Mask . . . . . . . . . . . : 255.255.0.0
  Lease Obtained. . . . . . . . . . : Tuesday, October 02, 2007 11:20:44 AM
  Lease Expires . . . . . . . . . . : Thursday, October 04, 2007 11:20:44 AM
  Default Gateway . . . . . . . . . : 0.0.0.0
                                      10.1.1.1
  DHCP Server . . . . . . . . . . . : 10.1.1.11
  DHCPv6 IAID . . . . . . . . . . . : 201384120
  DNS Servers . . . . . . . . . . . : 10.1.1.11
                                      10.1.1.23
  Primary WINS Server . . . . . . . : 10.1.1.11
  Secondary WINS Server . . . . . . : 10.1.1.23
  NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 6:

  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . :
isatap.{A5EBC489-3343-4B8A-BF52-886DB5DAC
59B}
  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 . . . . . . . . . . . :
isatap.{A5EBC489-3343-4B8A-BF52-886DB5DAC
59B}
  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. . . . . . . . . : 02-00-54-55-4E-01
  DHCP Enabled. . . . . . . . . . . : No
  Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 17:

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

Tunnel adapter Local Area Connection* 18:

  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . : siprep.org
  Description . . . . . . . . . . . : isatap.siprep.org
  Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
  DHCP Enabled. . . . . . . . . . . : No
  Autoconfiguration Enabled . . . . : Yes

C:\Users\fffff>ipconfig /all
***LAN and Wireless both connected, no internet

Windows IP Configuration

  Host Name . . . . . . . . . . . . : faculty1077
  Primary Dns Suffix  . . . . . . . : siprep.org
  Node Type . . . . . . . . . . . . : Hybrid
  IP Routing Enabled. . . . . . . . : No
  WINS Proxy Enabled. . . . . . . . : No
  DNS Suffix Search List. . . . . . : siprep.org

Ethernet adapter Local Area Connection 3:

  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . : SonicWALL VPN Adapter
  Physical Address. . . . . . . . . : 00-60-73-EB-93-CC
  DHCP Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection:

  Connection-specific DNS Suffix  . : siprep.org
  Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network
Con
nection
  Physical Address. . . . . . . . . : 00-1B-77-3F-F6-B9
  DHCP Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes
  Link-local IPv6 Address . . . . . : fe80::90ce:e913:bb05:41f6%9(Preferred)
  IPv4 Address. . . . . . . . . . . : 10.1.4.56(Preferred)
  Subnet Mask . . . . . . . . . . . : 255.255.0.0
  Lease Obtained. . . . . . . . . . : Tuesday, October 02, 2007 11:23:03 AM
  Lease Expires . . . . . . . . . . : Thursday, October 04, 2007 11:23:03 AM
  Default Gateway . . . . . . . . . : 10.1.1.1
  DHCP Server . . . . . . . . . . . : 10.1.1.11
  DHCPv6 IAID . . . . . . . . . . . : 151001975
  DNS Servers . . . . . . . . . . . : 10.1.1.23
                                      10.1.1.11
  Primary WINS Server . . . . . . . : 10.1.1.11
  Secondary WINS Server . . . . . . : 10.1.1.23
  NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

  Connection-specific DNS Suffix  . : siprep.org
  Description . . . . . . . . . . . : Intel(R) PRO/1000 PL Network Connection
  Physical Address. . . . . . . . . : 00-E0-B8-BB-F9-7E
  DHCP Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes
  Link-local IPv6 Address . . . . . : fe80::813e:9089:9f16:ad20%8(Preferred)
  IPv4 Address. . . . . . . . . . . : 10.1.4.33(Preferred)
  Subnet Mask . . . . . . . . . . . : 255.255.0.0
  Lease Obtained. . . . . . . . . . : Tuesday, October 02, 2007 11:20:44 AM
  Lease Expires . . . . . . . . . . : Thursday, October 04, 2007 11:20:44 AM
  Default Gateway . . . . . . . . . : 0.0.0.0
                                      10.1.1.1
  DHCP Server . . . . . . . . . . . : 10.1.1.11
  DHCPv6 IAID . . . . . . . . . . . : 201384120
  DNS Servers . . . . . . . . . . . : 10.1.1.11
                                      10.1.1.23
  Primary WINS Server . . . . . . . : 10.1.1.11
  Secondary WINS Server . . . . . . : 10.1.1.23
  NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 6:

  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . :
isatap.{A5EBC489-3343-4B8A-BF52-886DB5DAC
59B}
  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 . . . . . . . . . . . :
isatap.{A5EBC489-3343-4B8A-BF52-886DB5DAC
59B}
  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. . . . . . . . . : 02-00-54-55-4E-01
  DHCP Enabled. . . . . . . . . . . : No
  Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 17:

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

Tunnel adapter Local Area Connection* 18:

  Connection-specific DNS Suffix  . : siprep.org
  Description . . . . . . . . . . . : isatap.siprep.org
  Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
  DHCP Enabled. . . . . . . . . . . : No
  Autoconfiguration Enabled . . . . : Yes
  Link-local IPv6 Address . . . . . : fe80::5efe:10.1.4.33%22(Preferred)
  Link-local IPv6 Address . . . . . : fe80::5efe:10.1.4.56%22(Preferred)
  Default Gateway . . . . . . . . . :
  DNS Servers . . . . . . . . . . . : 10.1.1.11
                                      10.1.1.23
  NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Users\ffff>ipconfig /all
***LAN disconnected, Wireless connected, Internet is fine***

Windows IP Configuration

  Host Name . . . . . . . . . . . . : faculty1077
  Primary Dns Suffix  . . . . . . . : siprep.org
  Node Type . . . . . . . . . . . . : Hybrid
  IP Routing Enabled. . . . . . . . : No
  WINS Proxy Enabled. . . . . . . . : No
  DNS Suffix Search List. . . . . . : siprep.org

Ethernet adapter Local Area Connection 3:

  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . : SonicWALL VPN Adapter
  Physical Address. . . . . . . . . : 00-60-73-EB-93-CC
  DHCP Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection:

  Connection-specific DNS Suffix  . : siprep.org
  Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network
Con
nection
  Physical Address. . . . . . . . . : 00-1B-77-3F-F6-B9
  DHCP Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes
  Link-local IPv6 Address . . . . . : fe80::90ce:e913:bb05:41f6%9(Preferred)
  IPv4 Address. . . . . . . . . . . : 10.1.4.56(Preferred)
  Subnet Mask . . . . . . . . . . . : 255.255.0.0
  Lease Obtained. . . . . . . . . . : Tuesday, October 02, 2007 11:23:03 AM
  Lease Expires . . . . . . . . . . : Thursday, October 04, 2007 11:23:02 AM
  Default Gateway . . . . . . . . . : 10.1.1.1
  DHCP Server . . . . . . . . . . . : 10.1.1.11
  DHCPv6 IAID . . . . . . . . . . . : 151001975
  DNS Servers . . . . . . . . . . . : 10.1.1.23
                                      10.1.1.11
  Primary WINS Server . . . . . . . : 10.1.1.11
  Secondary WINS Server . . . . . . : 10.1.1.23
  NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . : siprep.org
  Description . . . . . . . . . . . : Intel(R) PRO/1000 PL Network Connection
  Physical Address. . . . . . . . . : 00-E0-B8-BB-F9-7E
  DHCP Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 6:

  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . :
isatap.{A5EBC489-3343-4B8A-BF52-886DB5DAC
59B}
  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 . . . . . . . . . . . :
isatap.{A5EBC489-3343-4B8A-BF52-886DB5DAC
59B}
  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. . . . . . . . . : 02-00-54-55-4E-01
  DHCP Enabled. . . . . . . . . . . : No
  Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 17:

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

Tunnel adapter Local Area Connection* 18:

  Connection-specific DNS Suffix  . : siprep.org
  Description . . . . . . . . . . . : isatap.siprep.org
  Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
  DHCP Enabled. . . . . . . . . . . : No
  Autoconfiguration Enabled . . . . : Yes
  Link-local IPv6 Address . . . . . : fe80::5efe:10.1.4.56%22(Preferred)
  Default Gateway . . . . . . . . . :
  DNS Servers . . . . . . . . . . . : 10.1.1.23
                                      10.1.1.11
  NetBIOS over Tcpip. . . . . . . . : Disabled
Barb Bowman - 03 Oct 2007 18:33 GMT
On one of the misfiring machines, can you reset the stack? then see
if you can recreate the issue on that machine?

1. Click on Start button.
2. Type Cmd in the Start Search text box.
3. Press Ctrl-Shift-Enter keyboard shortcut to run Command Prompt as
Administrator. Allow the elevation request.
4. Type
netsh int ip reset
in the cmd windows, and then press the Enter key.
5. Restart the computer.

>Barb, here are 4 versions of ipconfig /all.
>Our problem with Vista seems to almost exclusively occur with our wired
[quoted text clipped - 465 lines]
>                                       10.1.1.11
>   NetBIOS over Tcpip. . . . . . . . : Disabled

--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
DB - 03 Oct 2007 21:19 GMT
Barb, I'll give that a try next time it happens and I'm nearby.  Is this an
actual fix for it or just something to try?  I guess, if it works, will it be
permanent or will the problem return on the next hibernate?
I have tried uninstalling and reinstalling the LAN adapter.  Should that
reset the stack?  

Do you guys have any idea why the 0.0.0.0 shows up after a hibernate or
where it comes from?

> On one of the misfiring machines, can you reset the stack? then see
> if you can recreate the issue on that machine?
[quoted text clipped - 288 lines]
> >   Lease Expires . . . . . . . . . . : Thursday, October 04, 2007 11:23:03 AM
> >   Default Gateway . . . . . . . . . : 10.1.1.1
Barb Bowman - 03 Oct 2007 21:47 GMT
It's something to try. The only thing that is documented is a single
0.0.0.0 after hibernate and you already tried to documented fix.

>Barb, I'll give that a try next time it happens and I'm nearby.  Is this an
>actual fix for it or just something to try?  I guess, if it works, will it be
[quoted text clipped - 297 lines]
>> >   Lease Expires . . . . . . . . . . : Thursday, October 04, 2007 11:23:03 AM
>> >   Default Gateway . . . . . . . . . : 10.1.1.1
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
DB - 03 Oct 2007 21:28 GMT
Barb, I have a question that you may or may not be able to answer.  

As I understand it, with 2 NICs, Windows is supposed to check routes on each
NIC and evaluate the connections.  If the connection is faster on one than
the other, it uses that connection for that route.  In this case, the route
to the internet works on the WLAN but not on the LAN.  Shouldn't Vista be
able to evaluate that circumstance and use the faster LAN for local traffic,
but swith to the WLAN when going to a route outside the firewall (internet)?  
In our instance, this behavior would mask the problem and we may never have
noticed it, but it would still be desirable to no connection at all.

Thanks,

> On one of the misfiring machines, can you reset the stack? then see
> if you can recreate the issue on that machine?
[quoted text clipped - 288 lines]
> >   Lease Expires . . . . . . . . . . : Thursday, October 04, 2007 11:23:03 AM
> >   Default Gateway . . . . . . . . . : 10.1.1.1
Barb Bowman - 03 Oct 2007 21:50 GMT
yes, it's called a metric. I guess the real question is that if you
turn the wireless off and disable the NIC in device manager and then
do a cold power shut down and then power up, then go through the
hibernate/wake sequence, what happens?

>Barb, I have a question that you may or may not be able to answer.  
>
[quoted text clipped - 301 lines]
>> >   Lease Expires . . . . . . . . . . : Thursday, October 04, 2007 11:23:03 AM
>> >   Default Gateway . . . . . . . . . : 10.1.1.1
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
DB - 03 Oct 2007 23:08 GMT
Would it be your expectation that having one working route and one
non-working route, the metric should failover to the slower, working route?  
Because that definitely is not happening either.

> yes, it's called a metric. I guess the real question is that if you
> turn the wireless off and disable the NIC in device manager and then
[quoted text clipped - 283 lines]
> >> >
> >> >Ethernet adapter Local Area Connection 3:
Barb Bowman - 04 Oct 2007 09:52 GMT
probably not.

>Would it be your expectation that having one working route and one
>non-working route, the metric should failover to the slower, working route?  
[quoted text clipped - 287 lines]
>> >> >
>> >> >Ethernet adapter Local Area Connection 3:
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
DB - 04 Oct 2007 01:10 GMT
I spoke with our most troubled client and he's still having the problem. I'll
try resetting the stack tomorrow.

A read your last question again and I think we've already done that.  I
uninstalled the NIC and restarted and didn't allow it to reinstall.  We left
it like that for a couple of days with only the wireless active.  The machine
was definitely hibernated at least two times with no ill effects.

> yes, it's called a metric. I guess the real question is that if you
> turn the wireless off and disable the NIC in device manager and then
[quoted text clipped - 283 lines]
> >> >
> >> >Ethernet adapter Local Area Connection 3:
Barb Bowman - 04 Oct 2007 09:55 GMT
I'd still try with it disabled as opposed to uninstalled. Also, you
should look at what driver is installed for the Intel wireless
(there have been many issues) and what it is connecting to (router?
brand? model? firmware version?). I see Sonic Wall VPN in these
configs, and I know that there are some Sonic hardware devices that
have issues, some of which are alleviated with firmware fixes.

>I spoke with our most troubled client and he's still having the problem. I'll
>try resetting the stack tomorrow.
[quoted text clipped - 291 lines]
>> >> >
>> >> >Ethernet adapter Local Area Connection 3:
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
DB - 04 Oct 2007 17:33 GMT
When I get a chance I'll try with it disabled.

My problem with the driver/firmware/router issue is one of consistency.  We
have 69 identical machines all loaded with identical images.  If it was a
problem with one of our routers, our gateway or the intel software, you'd
think we'd see the problem across the board.  It seems to be a few machines
being very problematic, regardless of any of the above, and only on the LAN.  
To me that points to communication problems between the OS and the LAN
adapter.  We're using the latest drivers from Intel.  We were using an older
version a couple months ago that still had the problem.  In this case, since
the 0.0.0.0 shows up in the Default Gateway field, you'd think there must be
something in the DNS/DHCP causing this.  But it's fine until hibernation.  
After resuming from hibernate the 0.0.0.0 shows up.  I don't think that would
have anything to do with anything except the OS.  Our servers are definitely
not sending that address, so Vista must be picking it up somewhere else.  I
still have the feeling that it is some security measure put into Vista to
keep traffic to local only, but is getting messed up.  The Wireless traffic
passes seemlessly through the routers and gateway so it can't be a Vista
compatibility problem with those devices.

But, I'll let you know what I find out.  
By the way, is this information getting to Microsoft, or is this just you
trying to help out?  Either way I really appreciate it.

> I'd still try with it disabled as opposed to uninstalled. Also, you
> should look at what driver is installed for the Intel wireless
[quoted text clipped - 281 lines]
> >> >> >   Connection-specific DNS Suffix  . : siprep.org
> >> >> >   Description . . . . . . . . . . . : isatap.siprep.org
Barb Bowman - 04 Oct 2007 18:20 GMT
MVPs are volunteers. And it is just me. However, Microsoft official
staff do read these newsgroups.

>But, I'll let you know what I find out.  
>By the way, is this information getting to Microsoft, or is this just you
>trying to help out?  Either way I really appreciate it.
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
rkaine - 09 Oct 2007 18:44 GMT
I am having the exact same issue. Have followed this thread and others.
Have spent hours on the phone with Microsoft Technical Support.

Has there been any resolution?

Signature

rkaine

Barb Bowman - 09 Oct 2007 19:27 GMT
does http://support.microsoft.com/default.aspx/kb/933872/en-us apply
to you?

have you updated firmware on your router? please post some real
details.

>I am having the exact same issue. Have followed this thread and others.
>Have spent hours on the phone with Microsoft Technical Support.
>
>Has there been any resolution?
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
rkaine - 09 Oct 2007 22:12 GMT
I never put my computer into sleep mode.

I am running Vista 32-bit
I have an Nvidia nForce Networking Controller
I have a Linksys WRTP54G Wireless VOIP Router w/ the latest firmware.
I have another XP Pro, and two MACs that all use this router for DHCP
and they are having no problem whatsoever

The Vista PC however will not get an IP Address (gets the 169.#.#.#
address)

If I force a static IP address (192.168.150.120),
Gateway(192.168.150.1) and DNS (192.168.150.1,24.25.5.150,24.25.5.149)
and leave the Metric set to 'Automatic' I get 'Local Only' and the bogus
gateway of 0.0.0.0

If I set the Metric to 9999 (leaving everything else as listed above) I
can actually get 'Local and Internet' but I can't really get out to the
internet.

Signature

rkaine

Barb Bowman - 10 Oct 2007 10:07 GMT
Is the NVidia firewall on and active?

>I never put my computer into sleep mode.
>
[quoted text clipped - 15 lines]
>can actually get 'Local and Internet' but I can't really get out to the
>internet.
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
Barb Bowman - 04 Oct 2007 18:22 GMT
I don't disagree with anything you've said. All that is documented
is
http://support.microsoft.com/default.aspx/kb/933872/en-us.

>But it's fine until hibernation.  
>After resuming from hibernate the 0.0.0.0 shows up.
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
DB - 12 Oct 2007 00:16 GMT
Barb, I ran this on one of the less troublesome machines.  It usually
responds to a reboot and has only had the "local only" problem a couple of
times in the last month.  Anyhow, I ran that command and rebooted and it was
fine after that.  I'm hoping to get my hands on the most consistently
problematic machine tomorrow to see if it will fix that one as well.

Thanks,

> On one of the misfiring machines, can you reset the stack? then see
> if you can recreate the issue on that machine?
[quoted text clipped - 7 lines]
> in the cmd windows, and then press the Enter key.
> 5. Restart the computer.
Barb Bowman - 12 Oct 2007 10:48 GMT
thanks for the update. please let us know how it goes with the other
computer.

>Barb, I ran this on one of the less troublesome machines.  It usually
>responds to a reboot and has only had the "local only" problem a couple of
[quoted text clipped - 15 lines]
>> in the cmd windows, and then press the Enter key.
>> 5. Restart the computer.

--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
DB - 09 Nov 2007 20:39 GMT
Barb, it did not work.  I've tried it on three machines.  It always worked to
correct the problem after the required reboot.  However, all three have
reverted to the problem at different intervals.

Any other ideas?

> thanks for the update. please let us know how it goes with the other
> computer.
[quoted text clipped - 25 lines]
> http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
> http://blogs.digitalmediaphile.com/barb/
Barb Bowman - 09 Nov 2007 21:11 GMT
the only other thing I can think of is something I found specific to
the Intel 3945 wireless

http://support.intel.com/support/wireless/wlan/sb/cs-006205.htm

>Barb, it did not work.  I've tried it on three machines.  It always worked to
>correct the problem after the required reboot.  However, all three have
[quoted text clipped - 31 lines]
>> http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
>> http://blogs.digitalmediaphile.com/barb/

--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
DB - 12 Nov 2007 23:16 GMT
Barb, I didn't look at the link yet, but we're experiencing the problem with
our LAN adapters, not wireless.  Any idea where I should go next?  Do you
know if Microsoft is trying to correct this (meaning ALL of the local only
problems)?

> the only other thing I can think of is something I found specific to
> the Intel 3945 wireless
[quoted text clipped - 43 lines]
> http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
> http://blogs.digitalmediaphile.com/barb/
Barb Bowman - 13 Nov 2007 14:38 GMT
don't know what MS is including in Vista SP1, but one question -
have you removed Sonic Wall from the mix as a test?

>Barb, I didn't look at the link yet, but we're experiencing the problem with
>our LAN adapters, not wireless.  Any idea where I should go next?  Do you
[quoted text clipped - 48 lines]
>> http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
>> http://blogs.digitalmediaphile.com/barb/

--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
DB - 13 Nov 2007 23:57 GMT
We have updated our Sonicwall firewall, but not removed it.  But the problem
is getting the 0.0.0.0 entered on the local machines as the default gateway,
so it appears to be a Vista issue, possibly a Windows 2003-Vista DHCP issue.  
Since it almost always happens after a hibernation, I don't think there is
any re-communication to the DHCP servers anyhow, leading me to think it is
exclusively a Vista problem.

I don't foresee a time when I'll have access to any of the problematic
machines and be here on a weekend, when it would be safer to take down the
firewall.  I could make the time, but again, with it being a Vista issue, I
don't see the point.

Barb, thanks for your help.  I've seen hundreds, possibly thousands, of
forum posts regarding the "local only" problem, each containing multiple
users.  And despite people saying Microsoft engineers browse these forums
(and others), I have not seen one response from an actual engineer or anyone
at Microsoft.  This really concerns me.  I'm just hoping with how pervasive
this problem is, and that it is clearly a Vista problem, that it is addressed
in SP1.  Do you know of a way for us normal folk to find out what is being
included in SP1?  Or to even find out what's being worked on?  

> don't know what MS is including in Vista SP1, but one question -
> have you removed Sonic Wall from the mix as a test?
Barb Bowman - 14 Nov 2007 10:43 GMT
as you know, the only 0.0.0.0 documented issue I'm aware of is
http://support.microsoft.com/default.aspx/kb/933872/en-us

have you considered opening a support ticket with Microsoft on this
issue? that really is the "official" support channel.

Typically, a service pack is an accumulation of hot fixes that have
already been made available.
http://www.microsoft.com/downloads/details.aspx?familyid=090deaf6-2eaa-4aaa-8b3b
-2e199db4a97d&displaylang=en

is the best I can offer.

>We have updated our Sonicwall firewall, but not removed it.  But the problem
>is getting the 0.0.0.0 entered on the local machines as the default gateway,
[quoted text clipped - 19 lines]
>> don't know what MS is including in Vista SP1, but one question -
>> have you removed Sonic Wall from the mix as a test?
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
DB - 16 Nov 2007 17:19 GMT
To open a call with Microsoft, I believe that will cost me about $300
correct?  If not, I'd be happy to.

> as you know, the only 0.0.0.0 documented issue I'm aware of is
> http://support.microsoft.com/default.aspx/kb/933872/en-us
[quoted text clipped - 36 lines]
> http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
> http://blogs.digitalmediaphile.com/barb/
Barb Bowman - 16 Nov 2007 18:04 GMT
I had thought that you might have a support agreement - you
mentioned some 80 computers. But you can try personal support "for
one computer"
http://support.microsoft.com/oas/default.aspx?&gprid=11732&

http://support.microsoft.com/oas/default.aspx?ln=en-us&prid=10300&gprid=436974

>To open a call with Microsoft, I believe that will cost me about $300
>correct?  If not, I'd be happy to.
[quoted text clipped - 39 lines]
>> http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
>> http://blogs.digitalmediaphile.com/barb/

--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
rkaine - 10 Oct 2007 14:49 GMT
Yes, but I've tried turning it off and it doesn't matter.

Signature

rkaine

Robert L (MS-MVP) - 10 Oct 2007 16:44 GMT
You may need to clean the routing table first. This link may give more
details.

Vista: local only with 0.0.0.0 default gateway
3. You may want to clean the routing table. To do that, use "route print"
command to check if the Default Gateway is 0.0.0.0....
http://www.chicagotech.net/netforums/viewtopic.php?p=3037#3037

Signature

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com

> Yes, but I've tried turning it off and it doesn't matter.
Alex_H - 09 May 2008 19:10 GMT
I too am having this exact problem on my brand new home system. Im
running Windows Vista 64, and have all the problems seen above. I am
always eventually getting it sorted by some method or another, but it
can take me up to an hour to finally sort it, either by resetting the
connection, or in one instance completly disconnecting every form of
power to the system including the network cable and let it sit idel for
5 minutes.  Switching the PC on,  letting vista fully boot, and then
plug in the network cable.   Its a very odd problem, and to be honest
its making me like Vista less and less as each day passes.

What gets me is that for the first week of us, I never saw the problem,
then on Tuesday this week it began to appear, but each day it seems to
get worse and worse.  

I would appreciate any help people can give, so just let me know what
kind of infomation you would like.

Thanks and regards,

Alexander

Signature

Alex_H

alexb - 10 May 2008 08:54 GMT
I have the same problem as you guys. The problem started when I got a
new router (BT Homehub). I have two computers, computer 1 (Vista
Business) is connected to the router via wifi, computer 2 (XP Pro)
connects to computer 1 and shares its internet connection. When I had
the old router I used internet connection sharing, but the day I got the
new router that no longer worked (no internet on computer 2), so I
switched to bridging the wireless and Ethernet connections, which works,
but every time I boot up computer 1 I get the "local only", 0.0.0.0
problem and have to perform a combination of restarting the bridge
connection and automatically finding a new IP address before the
internet works again. Unfortunately I can't go back to the old router,
I'm stuck with this one...

Signature

alexb

Hourglass93 - 20 May 2008 16:43 GMT
After suffering with Vista for a month, I have decided to return to XP.
I have followed advice from numerous sources, including this forum and
have found little relief even after installing SP1.  The aggrevation of
having to wipe the OS from the new computer should more than offset the
aggrevation of having to reset my network adaptor everytime I start the
computer multiplied over a few years...or the incredibly slow iPod
sync'ing over the LAN.

I think Vista is aesthetically pleasing and I like the new organization
of the OS.  Just wish it worked properly :(

Signature

Hourglass93

alexb - 21 May 2008 08:09 GMT
I haven't solved this yet but I came across 'this'
(http://support.microsoft.com/kb/928233) Microsoft support page this
morning, which sounds like it might be worth looking into. I haven't
tried it myself yet as I have 4 different adapters listed under
Interfaces and I'm not sure which relates to my bridge, but I'll have a
go after work...

Signature

alexb

Gigabyter64 - 22 May 2008 07:25 GMT
I am having similar problems on 2 vista 64 systems on my home network,
it seemed to start after SP1 install for me. I intermittent loose my
manual gateway setting only. I used latest network driver from microsoft
for nforce to try & fix but still no fix. I installed network controller
from nvidia's website & all was fixed.To verify this I reinstalled the
driver from microsoft & problem started up again & only intermittent. my
situation was not from hibernation though but fresh startups.

Signature

Gigabyter64

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.