Recent content by LonnieSmith

In the end, reboot fixed it. Might have been winsock or ipstack reset, but my bet is that RRAS has jacked up communication with DHCP or some other integral service on the server and wouldn't restore till a reboot took place. Thanks for your advice gbb0330

going to try ipstack and winsock repair on the vpn server and a reboot after everyone leaves, see where that takes us.

DHCP shows 50 available now I did increase this by 20 after the issue ensued. regarding third error: Only one NIC on the server (it is a virtual server hosted on Hyper V), and it is set to use a Static IP. I will look further into the second error.

Telnet was successful. I checked the logs from when I made the change: Warning: RoutingDomainID- {: No IP address is available to hand out to the dial-in client. Error: RoutingDomainID- {00000000-0000-0000-0000-000000000000}: CoId={E3E3FB2F-A2E5-4DF3-969E-5F403B9F6C4B}: The user...

Also point of interest, checked and RAS And VPN are set to be allowed through windows firewall on the server. I don't think the software or hardware firewalls can be at fault as no changes have been made to them and it was working before I changed the security protocols in RRAS settings.

I did that as well, and chose all of the defaults as I remember doing it originally. No luck, goes right back to where it was before.

I had a working PPTP VPN hosted on a Windows Server 2012 R2 Domain Controller, which is also running DHCP and DNS. Last night I enabled PAP Security protocol as well as IKEv2, in an attempt to make it more Win10 friendly. This immediately broke the VPN. Now when users connect they are able to...