Windows 10: Windows 10 VPN external port other than 1723?

My windows 10 vpn works just fine if I specify 1723 as both the external and internal port on my router. However, I cannot connect remotely if I change the external port to something else and keep the internal port at 1723, which I want to do to add a very small layer of additional security. Can this be made to work? Is there a setting on the client that needs specific protocol, etc.?

:)

 

Private VPN and port forwarding 1723 to Random Port - any ideas


Hi there

I'm creating a private VPN - the actual VPN creation process isn't too bad but there's a bit of security I don't like.

Incoming VPN connections on Windows I think use Port 1723 - so malicious people if they want to check for any VPN's out there can just see who has got port 1723 open.

Is there a way of "masking" this -- say accept a Random port number (obviously fixed for the time the VPN is open) but unlikely to be targeted and then forward that port "internally" to 1723.

I'm getting into Network stuff which is "a bit beyond my paygrade here" though.

As far as the external IP address is for the Internet (i.e Me) it's easy enough

I have a silly stupid little micky mouse email program that just runs every 30 mins with an IPQUERY (on windows) or IFCONFIG (on LINUX), pipes the output into a file and then emails me so if the IP address has changed (ISP's tend not to give out static IP stuff any more) I can still access the VPN by simply reading the email and typing in the new I.P address.

My program runs on a Linux crontab with a sendmail command so that's easy enough to get the IP address every so often. Having trouble getting the windows one to work -- outlook seems to blow up when trying an auto sendmail but that's a minor issue currently -- the Linux one is fine.

I don't need to pay silly people like dyndns or whatever for doing essentially the same thing as I'm doing - although you get a domain name rather than use a specic IP address. As I'm the only user the IP address is fine. I do have a domain but that's for other uses - this VPN I want to be able to access the whole thing like I would do at home - and need slightly more sophistication than RDP gives. Eventually it will be some type of Server config so multiple users can logon concurrently to their own Windows VM's.

Cheers
jimbo

 

VPN to localip works, VPN to localip:1723 does not. Why?

Hi

I've just set up VPN for the first time, and I'm having some issues related to port specification.

The server is set up using the built-in Windows VPN server.

The client connects fine to the server if I specify the local ip (or computer name) of the server. However, if I specify port 1723, the connection hangs trying to connect. Port 443 gives the same result.

Given that 1723 and 443 are the default ports for VPN in Windows, I'm puzzled how this can be. Am I missing something?

Server is Win 8.1, client is Win 10, both are Pro editions.

Best regards,

Steinar

Edit: Moved to Network & internet, changed to Win 10 as I suspect the problem might lay there.

 

VPN Server on Windows 10 not Working

Windows 10 uses the same method as the previous versions of Windows. However, Windows 10 appears to have a bug. It becomes clear when you do this:

• Delete any existing incoming VPN connections.
• Reboot the machine.
• Create an incoming VPN connection.
• Type this command in a Command Console:
  
  netstat -a | find "1723"The command should report that the machine is listening on port 1723. Your VPN server is now working.
  
• Shut down Windows, then restart it.
  
• Try this command again:
  
  netstat -a | find "1723"
  
  The command will probably report nothing about port 1723. Your VPN server is no longer working.
  

The problem appears to be caused by the Windows 7 "Fast Startup Option". You can disable it by following this path:

Control Panel / Power Options / Change what the power buttons do / Change settings that are currently unavailable / remove the mark from the Fast Startup tick box.

Your VPN server should now survive a reboot.

BTW - Multiposting is frowned upon in these forums because it leads to duplication of effort. I suggest you either remove
your duplicate post or include a link to this thread in it.