VPN (PPTP) setup on server 2016 Std
I migrated from a 2003 server to a 2016 server. After the fact, the client informed me that they were using PPTP to connect remote users. I have gone through the RRAS setup and have installed the necessary role. The server manager says all is running correctly. I am using the same IP address in the 2nd NIC of the new server so I do not have to modify the firewall. This is the same NIC I selected when I setup RRAS, so the binding appears to be correct. When I attempt to connect from a client, I am getting a 807 error code.
How can I confirm the settings on the server to verify the CHAP settings and so on?
How can I confirm the settings on the server to verify the CHAP settings and so on?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Rob Williams
PS: An 807 error can be due to a firewall, hardware, or more likely software, blocking GRE traffic, such as Windows firewall or 3rd party security software. I have seen anti-virus software cause an 807 error.
PPTP has been conceptualy beenbroken for about 20 years,about 10 years ago there was a real time service on AWS that would guarantee breakage within 24 hours (worst case). for paying the fee for CPU etc. upfront.
PPTP not only is broken, the RC4 is not implemented correctly exposing the key used, besides that PPTP daemon assists in gaining access to user accounts on the server, (ie. revealing passwords).
Tyr investing some time in L2TP it'w worth the effort.
PPTP not only is broken, the RC4 is not implemented correctly exposing the key used, besides that PPTP daemon assists in gaining access to user accounts on the server, (ie. revealing passwords).
Tyr investing some time in L2TP it'w worth the effort.