Aanand Ramachandran

Hi Richard,
Did you check if NetBIOS over TCP/IP is enabled on the source (Vista)
and destination machines? This is absolutely necessary for shares access to
work.

thanks
Aanand

"Richard_G" <RichardG@discussions.microsoft.com> wrote in message
news:644A920A-B367-4908-BBA4-158705D28485@microsoft.com...
>I have not made any progress in resolving this problem.
>
> This is a major limitation of the VPN functionality of Vista - come on
> Microsoft: what's going on?
>
> "Richard_G" wrote:
>
>> Having NOT disabled IPV6 on the LAN (but it is disabled for the VPN
>> connection):
>> C:\Users\Richard>net view \\10.116.116.1
>> System error 53 has occurred.
>> The network path was not found.
>>
>> AND:
>>
>> C:\Users\Richard>net view \\front.local
>> System error 53 has occurred.
>> The network path was not found.
>>
>> It appears not to be an authentication problem.
>>
>> Thank you for your response.
>>
>> "Janani Vasudevan[MSFT]" wrote:
>>
>> > What error do you get? Is it 'Logon failure: Unknown username or
>> > password'?
>> > If so, can you try accessing the shares with the full FQDN name of the
>> > machine?
>> >
>> > Do let me know what happens.
>> >
>> > --
>> > Janani Vasudevan
>> > Software Design Engineer/Test
>> > RRAS, Windows Enterprise Networking
>> >
>> > [This posting is provided "AS IS" with no warranties, and confers no
>> > rights.]
>> >
>> > "Richard_G" <RichardG@discussions.microsoft.com> wrote in message
>> > news:71354DF0-DBC4-48A4-ABA7-33B48F1779EE@microsoft.com...
>> > > Vista has been working great for me with one major problem:
>> > >
>> > > I have a remote machine running WS2003, and have R&RA configured to
>> > > allow
>> > > dial-in VPN connections. DHCP is configured for all dial-in
>> > > IP/DNS/WINS IP
>> > > allocation.
>> > >
>> > > Using the windows XP VPN client I can connect fine to the server. I
>> > > can
>> > > also
>> > > browse the servers shares and (granted permissions) browse the
>> > > contents of
>> > > shared folders.
>> > >
>> > > Using the vista VPN client I can also connect fine. I can ping each
>> > > machine
>> > > from the end of the tunnel. I cannot access shared folders though,
>> > > nor
>> > > browse
>> > > the shares of either machine.
>> > >
>> > > I found a promising update from Microsoft: KB930163. This explained
>> > > that a
>> > > possible cause of the problem is the incorrect metric of the route to
>> > > the
>> > > VPN
>> > > server. However this update did not resolve the problem.
>> > >
>> > > As far as I can see, the only difference of the basic configurable
>> > > properties of the VPN connection on the Vista machine vs XP is the
>> > > 'automatic
>> > > metric' option in advanced tcp/ip settings. Should this be set
>> > > manually?
>> > > My
>> > > concern is that the metric status may be causing the problem - and
>> > > I'm not
>> > > entirely confident changing that setting.
>> > >
>> > > Any help will be gratefully appreciated.
>> > >
>> > > I have included a grab of netstat -r for reference (please note
>> > > 63.63.63.63
>> > > is fictional!)
>> > >
>> > > Active Routes:
>> > > Network Destination Netmask Gateway Interface
>> > > Metric
>> > > 0.0.0.0 0.0.0.0 192.168.10.1 192.168.10.6
>> > > 30
>> > > 10.0.0.0 255.0.0.0 10.116.116.3 10.116.116.8
>> > > 26
>> > > 10.116.116.8 255.255.255.255 On-link 10.116.116.8
>> > > 281
>> > > 63.63.63.63 255.255.255.255 192.168.10.1 192.168.10.6
>> > > 31
>> > > 127.0.0.0 255.0.0.0 On-link 127.0.0.1
>> > > 306
>> > > 127.0.0.1 255.255.255.255 On-link 127.0.0.1
>> > > 306
>> > > 127.255.255.255 255.255.255.255 On-link 127.0.0.1
>> > > 306
>> > > 192.168.10.0 255.255.255.0 On-link 192.168.10.6
>> > > 286
>> > > 192.168.10.6 255.255.255.255 On-link 192.168.10.6
>> > > 286
>> > > 192.168.10.255 255.255.255.255 On-link 192.168.10.6
>> > > 286
>> > > 224.0.0.0 240.0.0.0 On-link 127.0.0.1
>> > > 306
>> > > 224.0.0.0 240.0.0.0 On-link 192.168.10.6
>> > > 286
>> > > 255.255.255.255 255.255.255.255 On-link 127.0.0.1
>> > > 306
>> > > 255.255.255.255 255.255.255.255 On-link 192.168.10.6
>> > > 286
>> > > 255.255.255.255 255.255.255.255 On-link 10.116.116.8
>> > > 281
>> >
>> >