|
 |  |  |  |  |  |  |
| Welcome to Windows Vista Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows Vista. The Vista forum also covers news and updates and has an extensive Windows Vista tutorial section that covers a wide range of tips and tricks. |
| |||||||
 |
| |
03-07-2007
| #1 (permalink) |
| | Shared folders on XP/Windows Server 2003 via VPN from Vista 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 |
My System Specs |
|
03-07-2007
| #2 (permalink) |
| | Re: Shared folders on XP/Windows Server 2003 via VPN from Vista 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.8 281 |
| My System Specs |
|
03-07-2007
| #3 (permalink) |
| | Re: Shared folders on XP/Windows Server 2003 via VPN from Vista 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 |
| My System Specs |
|
03-07-2007
| #4 (permalink) |
| | Re: Shared folders on XP/Windows Server 2003 via VPN from Vista 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 |
| My System Specs |
|
03-08-2007
| #5 (permalink) |
| | Re: Shared folders on XP/Windows Server 2003 via VPN from Vista 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 |
| My System Specs |
|
03-08-2007
| #6 (permalink) |
| | Re: Shared folders on XP/Windows Server 2003 via VPN from Vista 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 > > |
| My System Specs |
|
03-08-2007
| #7 (permalink) |
| | Re: Shared folders on XP/Windows Server 2003 via VPN from Vista 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. "Robert L [MVP - Networking]" wrote: > 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 |
| My System Specs |
|
03-08-2007
| #8 (permalink) |
| | Re: Shared folders on XP/Windows Server 2003 via VPN from Vista 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 > > > > |
| My System Specs |
|
03-12-2007
| #9 (permalink) |
| | Re: Shared folders on XP/Windows Server 2003 via VPN from Vista 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 >> > >> > |
| My System Specs |
|
03-12-2007
| #10 (permalink) |
| | Re: Shared folders on XP/Windows Server 2003 via VPN from Vista 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" wrote: > 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 > >> > > >> > > > |
| My System Specs |
|
| Thread Tools | |
| |
Similar Threads | ||||
| Thread | Forum | |||
| Server driver locks shared folders | Vista networking & sharing | |||
| Cannot see certain files and folders on Windows 2003 server from V | Vista file management | |||
| Shared Fax/Scan Folders on server?? | Vista print fax & scan | |||
| Vista to Server 2003 shared folders | Vista networking & sharing | |||
| Windows 2003 Server domain cannot see shared Vista computer | Vista networking & sharing | |||
