I upgraded my workplace server from Windows 7 Pro to Windows 10 Pro, and cannot connect anymore to server's incoming VPN connection: I receive Error 807. Previously till upgrade, connection to Win 7 Pro worked perfectly - router is configured correctly (ports tcp1723, udp500, gre protocol). I also tried to put computer in DMZ, disabled firewall, but nothing helped.

I did little research:

1. Tried same setup on Windows 7 Professional on other computer: and I could connect from every machine I tried.

2. I tried netstat -a, and on Windows 10 I didnt find port 1723 in list! On Windows 7 there was port 1723 listed and listened.

3. I checked also Services.msc - all remote and RAS services are running and seems to be similar in Win 7 and Win 10.

Maybe PPTP port number is changed in Windows 10? Or there are some other protocol used for VPN?

Confirm your computer's firewall settings are still configured to permit traffic to and from your VPN. As you are using PPTP protocol, TCP Port 1723 and GRE Protocol 47 must be opened/enabled.

• Edited by joeyndlovu(MCSE, MCT,ITIL) 10 hours 53 minutes ago

Confirm your computer's firewall settings are still configured to permit traffic to and from your VPN. As you are using PPTP protocol, TCP Port 1723 and GRE Protocol 47 must be opened/enabled.

• Edited by joeyndlovu(MCSE, MCT,ITIL) Saturday, September 05, 2015 8:26 PM

SOLUTION FOUND!

I uninstalled AVG Internet security 2015 and VPN started to work!

AVG has it's own firewall, and it automatically manages also Windows firewall. When I did testing, I completely disabled AVG firewall, but it somehow blocked port 1723 or GRE protocol even disabled.

I checked in AVG's firewall there were PPTP, udp 500 and GRE protocols allowed, anyway it blocked VPN connection.

I reinstalled AVG Internet security, and problem returned, so I switched my antivirus to AVG Antivirus, which doesn't disturb Windows firewall and VPN worked again.

• Marked as answer by YohnnyLuksh 24 minutes ago

AVG has it's own firewall, and it automatically manages also Windows firewall. When I did testing, I completely disabled AVG firewall, but it somehow blocked port 1723 or GRE protocol even disabled.

I checked in AVG's firewall there were PPTP, udp 500 and GRE protocols allowed, anyway it blocked VPN connection.

I reinstalled AVG Internet security, and problem returned, so I switched my antivirus to AVG Antivirus, which doesn't disturb Windows firewall and VPN worked again.

UPDATE:

Hmm.. Now I got one more problem: incoming VPN doesn't work after shutdown, but starts to work after one restart. Then works till next shutdown.

When VPN doesn't work, then port 1723 isn't listed in nestat -a, when works, port is listed in nestat -a.

My Internet security software had it's own firewall, and it automatically managed also Windows firewall. When I did testing, even if I completely disabled Internet security's firewall, it somehow blocked port 1723 or GRE protocol even disabled.

My workaround was to uninstall Internet security and install only Antivirus instead, and VPN worked again.

UPDATE:

Hmm.. Now I got one more problem: incoming VPN doesn't work after shutdown, but starts to work after one restart. Then works till next shutdown.

When VPN doesn't work, then port 1723 isn't listed in nestat -a, when works, port is listed in nestat -a.

• Edited by YohnnyLuksh 20 hours 43 minutes ago

My Internet security software had it's own firewall, and it automatically managed also Windows firewall. When I did testing, even if I completely disabled Internet security's firewall, it somehow blocked port 1723 or GRE protocol even disabled.

My workaround was to uninstall Internet security and install only Antivirus instead, and VPN worked again.

UPDATE:

Hmm.. Now I got one more problem: incoming VPN doesn't work after shutdown, but starts to work after one restart. Then works till next shutdown.

When VPN doesn't work, then port 1723 isn't listed in nestat -a, when works, port is listed in nestat -a.

• Edited by YohnnyLuksh Monday, September 07, 2015 10:36 AM

COLD STARTUP VPN BUG/SOLUTION FOUND:

I found that if I start Windows 10 from shutdown, then Port 1723 isn't listed in "netstat -a" and incoming VPN isn't working, but after restart, Port 1723 is listed and VPN is working.

To fix VPN so it's working also when computer fresh starts, I disabled Fast startup checkbox in Power options. It seems that this option doesn't fully start VPN services RRAS etc.

To disable fast startup:

Goto Control panel - System - Power options - Change what power buttons do - Change settings that are currently anavailable - uncheck box [ ] Turn on fast startup.

I guess it is Windows 10 bug - where I can properly report it?