On Mon, 7 Nov 2005 18:37:14 -0800, "jetro57070"
<jetro57070@discussions.microsoft.com> wrote:

>"Chuck" wrote:
>
>> On Mon, 7 Nov 2005 14:26:24 -0800, "jetro57070"
>> <jetro57070@discussions.microsoft.com> wrote:
>>
>> >"Chuck" wrote:
>> >
>> >> On Sun, 6 Nov 2005 17:18:38 -0800, "jetro57070"
>> >> <jetro57070@discussions.microsoft.com> wrote:
>> >>
>> >> >"Chuck" wrote:
>> >> >
>> >> >> On Sat, 5 Nov 2005 09:47:02 -0800, "jetro57070"
>> >> >> <jetro57070@discussions.microsoft.com> wrote:
>> >> >>
>> >> >> >I have a home network with 3 computers connected to a NAT router and none of
>> >> >> >them can share files. They can all see and use the internet, The output from
>> >> >> >the suggested test CDIAG was run and is included below.
>> >> >> >
>> >> >> >PC 1 name ASTRO desktop with XP Prof SP2
>> >> >> >PC 2 name SCOOBYDOO notebook with XP Prof SP2
>> >> >> >PC 3 name SNOOPY desktop with XP Home Ed
>> >> >> >
>> >> >> >even if I take PC3 out of the picure PC1 and 2 can not share files and I get
>> >> >> >this error:
>> >> >> >
>> >> >> >Workgroup is not accessible, you might not have permission ...
>> >> >> >
>> >> >> >HELP I've been working on this for 2 months and am about ready to
>> >> >> >implement bodily harm to the nearest programmer from microsoft .. but I will
>> >> >> >settle for just getting it to work.
>> >> >>
>> >> >> Well, you've got at least 2 problems in there.
>> >> >> # Astro has trouble resolving addresses, and the other computers can't resolve
>> >> >> its address.
>> >> >> # Scooby has trouble resolving addresses, and the other computers can't resolve
>> >> >> its address. Plus it cant even resolve its own address properly.
>> >> >> # Astro is getting server datagrams from itself and from Scooby. No others are
>> >> >> visible in any Net Views.
>> >> >> # Only Astro can be pinged, by IP, by the others. Scooby and Snoopy can only be
>> >> >> pinged by themselves.
>> >> >>
>> >> >> Did you ever show "ipconfig /all" from all 3? Maybe there's a clue in there.
>> >> >> Other than that, and presuming that you have NetBIOS Over TCP/IP explicitly
>> >> >> Enabled on all 3 computers, you have multiple computers with firewall problems,
>> >> >> or corrupted LSP / Winsock stacks.
>>
>> <SNIP>
>>
>> >> Bingo. Scooby is running IPV6 aka Teredo Tunneling. Remove that.
>> >> <http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>
>> >> http://nitecruzr.blogspot.com/2005/0...-clean-up.html
>> >>
>> >> If any more problems, rerun "browstat status" and "ipconfig /all" from each
>> >> computer, and post all new results.
>>
>> >is there any other way around it? This is the VPN dial in connection I use
>> >for work so if I remove it, I cant remote access work from home?
>> >
>> >thanks for the help so far
>>
>> So you actually use IPV6 for the VPN?

>yes for highspeed secure VPN connection to work, it is a client with no
>configuration tabs, maybe there is a better one? Or is the netbios and dhcp
>disabled always for this type of vpn access? I was hoping maybe there is a
>way to disable it when I'm not using is so my home network would work

Well, this is a first. I have personally experienced the IPV6 / Windows
Networking problem twice - once before the problem was widely reported, and once
after (to verify that it really is a problem). Microsoft claims that IPV6 and
Windows Networking is compatible. All I know is that, every time someone writes
a problem report here, and IPV6 is found in their "ipconfig /all" log, removing
IPV6 makes the symptoms go away.

Up to now, the fact that removing IPV6 removes the symptom is final - IPV6 is
usually installed by accident, or when someone wanted to play with it. You're
the first person who has actually had a business need to keep IPV6.

I suspect that this problem will not be resolved under Windows XP - Microsoft is
simply too busy working on Vista. And TCP/IP under Vista is totally different,
so there's nothing gained either way.

Do you actually need to do file sharing, on your local LAN, with a computer also
involved in a VPN relationship? That would sound to me one like one of the
fears that I have had, for a while, with regard to corporate networks connected
by VPN to LANs that they can't secure.

The one guy in Microsoft that I talked to at any length claims that the IPV6
uninstall, resolving the symptom, is incidental. A re install of IPV6, after
the symptom is resolved, will allow both IPV6 and Windows Networking to work
together.
# Un install IPV6 temporarily.
# Verify that Windows Networking works.
# Re install IPV6.

--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.