Shared folders on XP/Windows Server 2003 via VPN from Vista

G

Guest

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
 
R

Robert L [MVP - Networking]

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
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
 
G

Guest

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?
 
R

Robert L [MVP - Networking]

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
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?
 
J

Janani Vasudevan[MSFT]

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.]
 
G

Guest

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 said:
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 said:
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
Click to expand...
Click to expand...
 
G

Guest

I have disabled IPV6 from all network connections. There has not resolved the
problem. Is there a method to completely disable the IPV6 layer of the TCP/IP
stack in Vista?

FWIW I have also tried disabling the firewall on the VPN server, which has
not helped. Also, I CAN access an FTP server on the VPN server over the VPN,
so the problem is definitely not a routing one.

So far no clues...

All help has been gratefully received. Thank you.
 
G

Guest

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 said:
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 said:
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 said:
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
Click to expand...
Click to expand...
Click to expand...
 
A

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 said:
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 said:
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 said:
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.]

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
Click to expand...
Click to expand...
Click to expand...
 
G

Guest

Thanks for your response Aanand. I have checked and netbios is enabled on the
vista client, and on the w2k3 server. Browsing shared folders works fine on
my many other XP machines.

Is NetBIOS not only for name resolution though? I have tried accessing the
shares on the server using an IP address and that does not work either.

Aanand Ramachandran said:
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 said:
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 said:
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.

:

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.]

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
Click to expand...
Click to expand...
Click to expand...
 
A

Aanand Ramachandran

Yes, it is not only for name resolution and is also used for data transfer
(session service)

thanks
Aanand

Richard_G said:
Thanks for your response Aanand. I have checked and netbios is enabled on
the
vista client, and on the w2k3 server. Browsing shared folders works fine
on
my many other XP machines.

Is NetBIOS not only for name resolution though? I have tried accessing the
shares on the server using an IP address and that does not work either.

Aanand Ramachandran said:
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 said:
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?

:

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.

:

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.]

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
Click to expand...
Click to expand...
Click to expand...
 
R

Rama Amaravadi [MSFT]

Richard,
Are the shares that you are trying to access are on the VPN server?
Can you make sure that checkboxes for "File and Printer Sharing for
Microsoft Networks" and "Client for Microsoft Networks" are selected. You
can find them by clicking on the properties of the connection and going to
"Networking" tab.
Also make sure that "Enable NetBIOS over TCP/IP" is enabled. You can check
that by following steps.
Go to properties of the connection.
Click on "Networking" tab.
Select "Internet Protocol Version 4 (TCPIPv4)" and click on "Properties"
Click on "Advanced" button in the new page.
Go to "WINS" tab and select "Enable NetBIOS over TCP/IP" if it is not
already selected.

Can you also please send us output for "cmdkey /list"

If port 139 on blocked by corpnet firewall or on theVPN server then you may
want to refer the KB article 933468.

--
Thanks,
Rama Amaravadi [MSFT]
RRAS blog: http://blogs.technet.com/rrasblog
[This posting is provided "AS IS" with no warranties, and confers no
rights.]

Richard_G said:
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 said:
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 said:
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.]

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
Click to expand...
Click to expand...
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Help - don't understand Vista route commend 1
Vista Premium - can't ping or see local machines 5
Vista/XP networking dilemma 5
Vista / W2K8 -- Outgoing VPN blocks RDP/LAN connection ? 0
Persistent routes 1
Problems connecting a new Vista PC to my Home neetwork 3
2 networks for diferent uses (wired and wirless) 3
Site-to-Site VPN 0

Top