--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.
--But it's fine until hibernation.
After resuming from hibernate the 0.0.0.0 shows up.
--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?
--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.
--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,
--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?
--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)?
--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?
--To open a call with Microsoft, I believe that will cost me about $300
correct? If not, I'd be happy to.