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?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Rob WilliamsCommented:
Firstly I trust you are aware PPTP is now considered extremely risky  to use?

Newer server versions require you configure NPS (Network  Protection Services) to grant the user permissions.

You may want to look at an article I did several years ago for configuring PPTP.  Different server version, but the method is the same:

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Rob WilliamsCommented:
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.
nociSoftware EngineerCommented:
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.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2016

From novice to tech pro — start learning today.