Windows 7 windows 7 vpn connects sometimes, but nothing works

[Dave Bahr]

Hi,

I am trying to set up a vpn from my home computer to my laptop so I can access my network drives when I'm on the go. I am able to access my remote desktop using a dynamic dns hostname, but cannot access the vpn using the same hostname. I have to use my external ip, and port 1723 is forwarded on my tplink router. I have all the firmware updated on the router, using win7 64 bit with all updates installed. I have created the vpn connections (in and out) with the wizzard. I have also disabled the windows logon option for the incoming connection. I have searched online but all steps have not resolved the issue and, as usual, the windows network troubleshooter is useless.

If I connect with my external ip, give the vpn the correct destination name, and the credentials for connecting, I can connect, but nothing works. I have 3 hard drives mapped when I am on my lan and they just say "file system ntfs" when I try to connect from outside the lan. Furthermore, the wireless connection that I use to connect to the internet outside of the lan is disabled when I connect with the windows 7 vpn. In order to get back online I have to disconnect from the vpn, which right now is fine as it doesn't really do anything despite the fact that it says it's connected. Is there a way to fix these two problems?

One last problem. When I type in my dynamic dns hostname (which the router recognizes in it's config page) into the vpn address box, type all credentials correctly and press Connect, I get the "error 868 the server name did not resolve" message. I can use this same dyndns host to connect with windows rdp, but I want to be able to access audio and files from outside the lan without RDP (audio is compressed).

So to recap, issues are:

1. can only use external ip to connect to win7 vpn; nothing happens after connection is established and internet is disconnected from original wireless accesspoint.

2. I cannot connect with dynamic dns hostname despite having a dyndns update client and a static internal non-dhcp ip. I cannot see drives accept for their designations on the network but cannot access them.

I hope that made sense? So, if anyone has any ideas as to these problems, I would love to hear from you. thank you, dave

 

[ChatGPT]

Dave, it appears that you are encountering multiple issues while trying to set up a VPN connection to access your network drives remotely. Let's address each of your concerns:

Issue 1: Unable to Access Network Drives via VPN Connection​

• Connection with External IP: It's common to use the external IP address for VPN connections when dynamic hostname resolving fails. Since you can establish the connection using the external IP but encounter issues with drive access, this could be related to network permissions or firewall settings.
• Drive Mapping: The issue where your drives only show as "file system ntfs" when connected remotely could be due to how the drives are mapped in your VPN configuration or potential network restrictions.
• Wireless Connection Disabling: When you connect to the VPN, your wireless connection getting disabled indicates a routing issue or configuration conflict. This can often be resolved by adjusting the VPN settings or checking for any conflicting network settings.

  Issue 2: Dynamic DNS Hostname Resolution Error​

• Error 868 - Server Name Did Not Resolve: This error typically occurs when the VPN server's hostname cannot be resolved. It's important to ensure that the dynamic DNS hostname is correctly configured and resolving to the correct external IP address. Double-check the settings in your router as well as the DDNS configuration.

  Recommendations to Resolve the Issues:​

  1. Check Firewall Settings: Ensure that your firewall is not blocking the necessary VPN traffic. Adjust the settings to allow VPN connections.
  2. Verify Network Permissions: Check the permissions on your network drives to ensure they are accessible over VPN connections.
  3. Router Configuration: Confirm that port forwarding for VPN (port 1723) is correctly set up on your TP-Link router.
  4. Update VPN Settings: Double-check your VPN configuration settings to ensure they are correctly set up for remote access.
  5. Troubleshoot Network Connection Issues: Troubleshoot the network connections between your devices to identify any potential conflicts or misconfigurations. By addressing these recommendations and troubleshooting steps, you should be able to resolve the issues you are facing with your VPN setup. If you need further assistance or detailed steps for any of these recommendations, feel free to ask!