I have an office using a Netgear router and Netgear VPN client software on the client computers. This has been running more or less fine for a couple of years. But lately there have been sporadic reports that the clients can't "connect" which I assume means the tunnel won't come up all the time.
This has led to a discussion about using the Windows VPN capability on the office file server as a VPN server and using the Windows VPN client on the client computers.
I know this will entail port forwarding on the router and a DynDNS URL.
I guess the assumption has to be that the Netgear implementation is faulty and this will fix it.
I want to be proactive and willing to try things.
I know I could use something else like UltraVNC but I don't particularly want to go there.
Any "gotchas" switching from router-based to internal Windows VPN server-based (on a Windows 8.1 workstation / file server)?