VPN Error 800: The Remote connection was not made. VPN tunnels failed.

When computers both internally and remotely try to VPN into my server that is running Windows Server 2003 R2 Enterprise Edition, they receive VPN Error 800: The remote connection was not made because the attempted VPN tunnels failed.

I pinged my server and it replied all 4 times.

I went to CanYouSeeMe.org (on my server) and received the message: Success: I can see your service on  on port (1723) Your ISP is not blocking port 1723

I verfied that remote access permission was still enabled for my users in Active Directory Users and Computers.

I have changed nothing on the server in the last 2 months and VPN was working fine as of yesterday.

The image I uploaded is from my laptop which I verified that PPTP VPN and ESP Protocol were not being blocked by my AVG firewall.
Who is Participating?
AGDavisAuthor Commented:
I had to end up calling Microsoft to fix the problem. Evidently when I uninstalled Symantec Endpoint Protection 11.0.4 to install 11.0.6, it removed VPN registries. So I had to have them rebuilt.

Thank you,
Can you bounce the server and see if you still have issues? While I realize rebooting a server is an inconvenience sometimes it's the cure to reset the protocols.
Great glad to hear you got it resolved!

Where is the solution? Can someone please tell me is this problem occur after the Microsoft update that screw most of the time the stability of our environment.

The VPN on ISA 2006 server was working fine until yesterday. After I did the update for this server which spouse do good and fix problem The VPN stopped. Does not make any since, you can not trust even the update coming from huge company like Microsoft.
Please is any one knows which security patch causing this problem. Thank s
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.