I have setup a VPN server with Server 2k12 and i have set it up behind an NAT and external/remote clients can connect via PPTP just fine. I was having issues with L2TP but i further read that L2TP has issues when the server is behind a NAT (if this is not entirely true, i would like to know how to get L2TP working as well). So now i am trying to setup SSTP for windows clients.
I already attained a legit certificate with COMODO and got it imported onto my server through IIS. I created the request and then completed it with the response i got from COMODO and i configured my VPN server to use that certificate. All ports are forwarded for L2TP, PPTP, IPSec, HTTPS (443 for SSTP). But i am unable to connect even from a client in the same network as the server. Because of that i marked off a firewall issue as being a possibility.
The error i get on windows 10 is "the remote server is not responding in a timeley fashion"
I have tried to change authentication settings on the client side but that has had no effect. I also have reviewed multiple tutorials on how to setup SSTP and even with the exact settings i still cant connect from either a local client or remote client.
I followed these tutorials:
Setup an SSTP SSL VPN in Windows Server 2012 R2
How to setup an SSTP VPN server with Windows Server
Im fairly new to VPN's so i have just gone with my gut on changing client settings hoping it would connect. From what i can say, the protocols are allowed through the server's firewall and also from the client and home router. Im not sure where its failing. im thinking it could be my certificate? perhaps i bought the wrong one?
Much help appreciated!
Best Answer
So after doing more troubleshooting with IIS and my VPN server. I removed a Self-Signed Certificate i made before and after i did that i got an error message when going to Routing and Remote Access saying that the certificate i was using does not exist meaning my server, for some reason after changing, it selected the SS Certificate instead of the one i bought. Set the certificate to the correct one and restarted the service. Tried to connect with my client and it worked just fine.
Hope this helps anyone else int he future