|
|
Welcome to Vista Banter. You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to ask questions and reply to others posts, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact support. |
|
|||||||
| Networking with Windows Vista Networking issues and questions with Windows Vista. (microsoft.public.windows.vista.networking_sharing) |
|
|
LinkBack | Thread Tools | Display Modes |
April 3rd 08, 04:51 PM
posted to microsoft.public.windows.vista.networking_sharing
|
|||
|
|||
Vista VPN: Can't see network resources over VPN
I have successfully established a VPN connection between two Vista Ultimate
SP1 computers, my client MAINE and the host APC. However, I cannot see or access any of the host network resources over the VPN from the client. From the client, I can successfully ping the host by IP address or name but from the host I cannot successfully ping the client by either IP or name. I've tested with firewalls disabled with no success. There is a router on each end, both configured to forward ports TCP 1723, 47, and 445 to their respective client or host computers. The results of ipconfig /all on the client a Windows IP Configuration Host Name . . . . . . . . . . . . : MAINE Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : maine.rr.com PPP adapter APC - VPN Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : APC - VPN Connection Physical Address. . . . . . . . . : DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2005:123:456:789:c849:21de:9187:8883(Preferred) Link-local IPv6 Address . . . . . : fe80::c849:21de:9187:8883%17(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.1.103(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.255 Default Gateway . . . . . . . . . : fe80::2835:f23b:939b:a7b4%17 0.0.0.0 DHCPv6 IAID . . . . . . . . . . . : 295577888 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-0D-9F-0E-60-00-07-E9-BF-76-2C DNS Servers . . . . . . . . . . . : 68.87.71.226 68.87.73.242 NetBIOS over Tcpip. . . . . . . . : Enabled Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : maine.rr.com Description . . . . . . . . . . . : Intel(R) PRO/100 M Desktop Adapter Physical Address. . . . . . . . . : 00-07-E9-BF-76-2C DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::b047:388b:3277:2131%8(Preferred) IPv4 Address. . . . . . . . . . . : 10.168.1.101(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Friday, March 21, 2008 5:14:56 PM Lease Expires . . . . . . . . . . : Sunday, May 10, 2144 7:05:45 PM Default Gateway . . . . . . . . . : 10.168.1.1 DHCP Server . . . . . . . . . . . : 10.168.1.1 DNS Servers . . . . . . . . . . . : 24.92.226.40 24.92.226.41 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter Local Area Connection* 6: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : maine.rr.com Description . . . . . . . . . . . : isatap.maine.rr.com Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 7: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 02-00-54-55-4E-01 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 11: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2 Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes I have NetBIOS enabled and I am loading an LMHOSTS file with this data: 192.168.1.103 APC #PRE 10.168.1.101 MAINE #PRE CAN ANYONE HELP! I have been trying to get this VPN to work for weeks. Any ideas? Thank you in advance. 
|
|
April 3rd 08, 07:27 PM
posted to microsoft.public.windows.vista.networking_sharing
|
|||
|
|||
|
Vista VPN: Can't see network resources over VPN
Both sites' DNS are public IP addresses. Can I assume the VPN host is
workstation (no server)? -- 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 "Kevin" wrote in message ... I have successfully established a VPN connection between two Vista Ultimate SP1 computers, my client MAINE and the host APC. However, I cannot see or access any of the host network resources over the VPN from the client. From the client, I can successfully ping the host by IP address or name but from the host I cannot successfully ping the client by either IP or name. I've tested with firewalls disabled with no success. There is a router on each end, both configured to forward ports TCP 1723, 47, and 445 to their respective client or host computers. The results of ipconfig /all on the client a Windows IP Configuration Host Name . . . . . . . . . . . . : MAINE Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : maine.rr.com PPP adapter APC - VPN Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : APC - VPN Connection Physical Address. . . . . . . . . : DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2005:123:456:789:c849:21de:9187:8883(Preferred) Link-local IPv6 Address . . . . . : fe80::c849:21de:9187:8883%17(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.1.103(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.255 Default Gateway . . . . . . . . . : fe80::2835:f23b:939b:a7b4%17 0.0.0.0 DHCPv6 IAID . . . . . . . . . . . : 295577888 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-0D-9F-0E-60-00-07-E9-BF-76-2C DNS Servers . . . . . . . . . . . : 68.87.71.226 68.87.73.242 NetBIOS over Tcpip. . . . . . . . : Enabled Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : maine.rr.com Description . . . . . . . . . . . : Intel(R) PRO/100 M Desktop Adapter Physical Address. . . . . . . . . : 00-07-E9-BF-76-2C DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::b047:388b:3277:2131%8(Preferred) IPv4 Address. . . . . . . . . . . : 10.168.1.101(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Friday, March 21, 2008 5:14:56 PM Lease Expires . . . . . . . . . . : Sunday, May 10, 2144 7:05:45 PM Default Gateway . . . . . . . . . : 10.168.1.1 DHCP Server . . . . . . . . . . . : 10.168.1.1 DNS Servers . . . . . . . . . . . : 24.92.226.40 24.92.226.41 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter Local Area Connection* 6: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : maine.rr.com Description . . . . . . . . . . . : isatap.maine.rr.com Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 7: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 02-00-54-55-4E-01 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 11: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2 Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes I have NetBIOS enabled and I am loading an LMHOSTS file with this data: 192.168.1.103 APC #PRE 10.168.1.101 MAINE #PRE CAN ANYONE HELP! I have been trying to get this VPN to work for weeks. Any ideas? Thank you in advance.
|
|
April 10th 08, 04:19 PM
posted to microsoft.public.windows.vista.networking_sharing
|
|||
|
|||
|
Vista VPN: Can't see network resources over VPN
Sorry for the slow response. I appreciate any help you can offer.
Yes, the VPN host is a workstation, not a server. "Robert L. (MS-MVP)" wrote: Both sites' DNS are public IP addresses. Can I assume the VPN host is workstation (no server)? -- 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 "Kevin" wrote in message ... I have successfully established a VPN connection between two Vista Ultimate SP1 computers, my client MAINE and the host APC. However, I cannot see or access any of the host network resources over the VPN from the client. From the client, I can successfully ping the host by IP address or name but from the host I cannot successfully ping the client by either IP or name. I've tested with firewalls disabled with no success. There is a router on each end, both configured to forward ports TCP 1723, 47, and 445 to their respective client or host computers. The results of ipconfig /all on the client a Windows IP Configuration Host Name . . . . . . . . . . . . : MAINE Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : maine.rr.com PPP adapter APC - VPN Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : APC - VPN Connection Physical Address. . . . . . . . . : DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2005:123:456:789:c849:21de:9187:8883(Preferred) Link-local IPv6 Address . . . . . : fe80::c849:21de:9187:8883%17(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.1.103(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.255 Default Gateway . . . . . . . . . : fe80::2835:f23b:939b:a7b4%17 0.0.0.0 DHCPv6 IAID . . . . . . . . . . . : 295577888 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-0D-9F-0E-60-00-07-E9-BF-76-2C DNS Servers . . . . . . . . . . . : 68.87.71.226 68.87.73.242 NetBIOS over Tcpip. . . . . . . . : Enabled Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : maine.rr.com Description . . . . . . . . . . . : Intel(R) PRO/100 M Desktop Adapter Physical Address. . . . . . . . . : 00-07-E9-BF-76-2C DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::b047:388b:3277:2131%8(Preferred) IPv4 Address. . . . . . . . . . . : 10.168.1.101(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Friday, March 21, 2008 5:14:56 PM Lease Expires . . . . . . . . . . : Sunday, May 10, 2144 7:05:45 PM Default Gateway . . . . . . . . . : 10.168.1.1 DHCP Server . . . . . . . . . . . : 10.168.1.1 DNS Servers . . . . . . . . . . . : 24.92.226.40 24.92.226.41 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter Local Area Connection* 6: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : maine.rr.com Description . . . . . . . . . . . : isatap.maine.rr.com Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 7: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 02-00-54-55-4E-01 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 11: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2 Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes I have NetBIOS enabled and I am loading an LMHOSTS file with this data: 192.168.1.103 APC #PRE 10.168.1.101 MAINE #PRE CAN ANYONE HELP! I have been trying to get this VPN to work for weeks. Any ideas? Thank you in advance.
|
|
October 16th 08, 11:06 PM
posted to microsoft.public.windows.vista.networking_sharing
|
|||
|
|||
|
Vista VPN Host TCP Port 445 error
I am experiencing very similar issues and am wondering if a solution has been found.
My situation is: Computer A - Vista Business/VPN Host Computer B - Vista Home Premium/VPN Client B connects via vpn, authenticates, registers on the network and can ping A, but cannot map drive, or command/run \\computer A; both give error 445. Ports 50, 51, 137, 138, 139, 445, 500, 1701, 1723 are open on WRV210 Linksys VPN router; have tested with both windows firewalls disabled and no other software firewalls running. I have confirmed that the Linksys works by creating an XP Pro VPN host--that scenario works 100%. Linksys tech support confirms my results; Vista VPN will NOT work and XP Pro VPN will work. They will not troubleshoot further because they say it is a Vista problem.
|
|
October 17th 08, 04:43 AM
posted to microsoft.public.windows.vista.networking_sharing
|
|||
|
|||
|
Vista VPN Host TCP Port 445 error
Can you ping VPN host by IP?
-- 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 "Paul Kramer" wrote in message ... I am experiencing very similar issues and am wondering if a solution has been found. My situation is: Computer A - Vista Business/VPN Host Computer B - Vista Home Premium/VPN Client B connects via vpn, authenticates, registers on the network and can ping A, but cannot map drive, or command/run \\computer A; both give error 445. Ports 50, 51, 137, 138, 139, 445, 500, 1701, 1723 are open on WRV210 Linksys VPN router; have tested with both windows firewalls disabled and no other software firewalls running. I have confirmed that the Linksys works by creating an XP Pro VPN host--that scenario works 100%. Linksys tech support confirms my results; Vista VPN will NOT work and XP Pro VPN will work. They will not troubleshoot further because they say it is a Vista problem.
|
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
