Here we go (again):
Issue:
You see ?Unidentified local access only? message under Vista.
Supposed fix:
Microsoft says to put a registry fix in to address the issue. This doesn?t work. You start tearing your hair out (if you have any left...)
Everyone is blaming Microsoft.
But guess what? It?s not their error! In fact it is doing exactly what it?s supposed to do!
To explain (ahem):
This error happened to me on my small home network. Three nodes and all are running Vista SP1. Everything was working fine. I even had a little smile on my puss!
Then the horror show, my little droogs (http://en.wikiquote.org/wiki/A_Clockwork_Orange ). I moved and got myself a new little ADSL modem, a NetGear DM111p. Oh the pain....
This little thing caused a chain of events which took 2 days to resolve. I was able to connect one node to the intarweb but not the others.
Huh?
The other nodes said that they had local access but no internet. Ipconfig on the other nodes only gave me the IPv6 address and not a local address.
Clue #1.
After looking at all of the settings I found that this little piece of @%$# modem said it was doing DHCP but was, in fact, not doing NAT.
OMG
The PC with intarweb access had a public IP address passed straight through from the piece of $#@! Modem.
So....
Vista looks at the ip address. Has a heart tremor and decides that this is like doing a hooker without a rubber and panics. Vista decides to leave the initial address but won?t provide connectivity to the rest of the LAN.
Well done, Microsoft. That?s exactly what should happen except for one minor little item which would be an informative message to tell the poor users (that?s me) WTF is going on.
Vista has done the right thing! Take credit! Tell us!
Hope this helps all the other users with the same issue. This crops up if a corporate LAN is considered to be outside of a private LAN address space (i.e. routable external addresses instead of the old C and B classes) so if someone connects to a routable external address, goes home and plugs into their own LAN, wallah, local connection only unless they have set up an alternate LAN configuration) which very few people do).
Good luck and HTH
Issue:
You see ?Unidentified local access only? message under Vista.
Supposed fix:
Microsoft says to put a registry fix in to address the issue. This doesn?t work. You start tearing your hair out (if you have any left...)
Everyone is blaming Microsoft.
But guess what? It?s not their error! In fact it is doing exactly what it?s supposed to do!
To explain (ahem):
This error happened to me on my small home network. Three nodes and all are running Vista SP1. Everything was working fine. I even had a little smile on my puss!
Then the horror show, my little droogs (http://en.wikiquote.org/wiki/A_Clockwork_Orange ). I moved and got myself a new little ADSL modem, a NetGear DM111p. Oh the pain....
This little thing caused a chain of events which took 2 days to resolve. I was able to connect one node to the intarweb but not the others.
Huh?
The other nodes said that they had local access but no internet. Ipconfig on the other nodes only gave me the IPv6 address and not a local address.
Clue #1.
After looking at all of the settings I found that this little piece of @%$# modem said it was doing DHCP but was, in fact, not doing NAT.
OMG
The PC with intarweb access had a public IP address passed straight through from the piece of $#@! Modem.
So....
Vista looks at the ip address. Has a heart tremor and decides that this is like doing a hooker without a rubber and panics. Vista decides to leave the initial address but won?t provide connectivity to the rest of the LAN.
Well done, Microsoft. That?s exactly what should happen except for one minor little item which would be an informative message to tell the poor users (that?s me) WTF is going on.
Vista has done the right thing! Take credit! Tell us!
Hope this helps all the other users with the same issue. This crops up if a corporate LAN is considered to be outside of a private LAN address space (i.e. routable external addresses instead of the old C and B classes) so if someone connects to a routable external address, goes home and plugs into their own LAN, wallah, local connection only unless they have set up an alternate LAN configuration) which very few people do).
Good luck and HTH