We found, sometimes, the IPv6 of Vista VPN connection might cause the problem to share. Please also try to disable IPv6 in the LAN to see what happens.
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
"Richard_G" <RichardG@discussions.microsoft.com> wrote in message news:A8BF61D1-CAB7-4B1D-9BF3-7913C6160022@microsoft.com...
I have tried disabling IPV6 from the VPN connection to find no noticable
affect: i can still not browse shares. I have not tried disabling IPV6
altogether in Vista - is that what you mean?
"Robert L [MVP - Networking]" wrote:
> Doesn't seem the routing is issue here because you can ping it. Try to disable IPv6. Please post back with the result.
>
> 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
> "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