T
TTBAdmin
I am running into some weird things that I cannot figure out and could use a little help.
I have a Windows 2016 server setup as a SSTP VPN with routing and remote access configured. I do not have a ton of users, the most I have seen connected to it at one time is 12.
In the morning it seems to work fine, but if you connect to the VPN in the afternoon it will not allow to access anything on the remote network. The connection is very fast and it say connected but that is where it stops. One of two things happen. 1. You cannot connect to any network drives, you cannot ping anything by name or IP address. I check the VPN server and can see the user is connected. I check the event logs and see nothing that would point me in the right direction.
The 2nd thing that might happen is that you still cannot connect to any resources on the remote network but when you try to ping a computer by name, it returns a public ip address. If you try to ping by ip address it will work sometimes, sometimes it will not.
This has happened with 3 or 4 users connected or with 10 users connected so it does not seem to be some limitation to the number of the users.
If I reboot the server, everything works without any issues for a while.
The users computers are all Windows 10 and are configured with "Use Default gateway on the remote network" un-checked.
Any help would be greatly appreciated
Continue reading...
I have a Windows 2016 server setup as a SSTP VPN with routing and remote access configured. I do not have a ton of users, the most I have seen connected to it at one time is 12.
In the morning it seems to work fine, but if you connect to the VPN in the afternoon it will not allow to access anything on the remote network. The connection is very fast and it say connected but that is where it stops. One of two things happen. 1. You cannot connect to any network drives, you cannot ping anything by name or IP address. I check the VPN server and can see the user is connected. I check the event logs and see nothing that would point me in the right direction.
The 2nd thing that might happen is that you still cannot connect to any resources on the remote network but when you try to ping a computer by name, it returns a public ip address. If you try to ping by ip address it will work sometimes, sometimes it will not.
This has happened with 3 or 4 users connected or with 10 users connected so it does not seem to be some limitation to the number of the users.
If I reboot the server, everything works without any issues for a while.
The users computers are all Windows 10 and are configured with "Use Default gateway on the remote network" un-checked.
Any help would be greatly appreciated
Continue reading...