I've been experiencing issues connecting to a remote system with RDP. The server has been operational for several years and is one of 4 servers identical servers located at the same site. Recently, one of the other servers crashed that I had
been remoting into for a long time so I had to start using this server to RDP into. Once our on-site IT personnel redirected port forwarding to this NAT'd server I was able to log in remotely to make some changes, including adding a role as a Remote
Access VPN server using the Routing and Remote Access Server Setup Wizard and removing the Network Threat Protection component of Symantec Endpoint Protection so that I can use and configure the Windows Firewall.
While working through the Routing and Remote Access Server Setup Wizard, my RDP session locked up and disconnected. I was able to reconnect after on-site personnel completed the wizard and restarted the computer, but once I reconnected, after a minute
or 2, I was again disconnected and could not reconnect until the server was restarted. I presumed adding the VPN role affected my RDP access, and decided to remove the VPN server role.
Now, I cannot RDP into the server unless it is freshly rebooted, and even then it only allows me to stay connected for a couple of minutes before the connection is lost and I'm unable to reconnect again until the server is restarted. One vicious cycle;
able to login after reboot only to have the connection dropped and require a restart to reconnect again.
This server also hosts a database that client systems are only able to access for a short period of time after reboot before their connection drops.
I've quadruple checked the Windows Firewall inbound rules, uninstalled the anti-virus application completely, even going so far as having to obtain their removal application to ensure every piece of it was removed, and I'm still having the same issue.
The entire issue started when I tried to add the VPN role. I'm sure uninstalling and reinstalling the anti-virus several times hasn't helped either, but as it stands right now, I have a server that shortly after restarting is unable to communicate;
not with the internet, not on the local area network, not remotely. On-site personnel are trying their best to follow my troubleshooting telephonically but it's getting to the point where I'll have to find out what's wrong and provide an easy fix
remotely, or, make a trip half-way around the world to try to figure it out myself (which would be EXTREMELY difficult/close to impossible right now).
Quesitons:
1) Why would I be able to connect remotely after reboot and then get disconnected shortly thereafter? (Service/application causing the issue hasn't started until shortly after a reboot??)
2) Why does it not only kill remote access, but LAN and internet access on the server?
3) What else can be checked to help diagnose and troubleshoot the issue?
I have done a lot of searching on the web but haven't found issues identical to my own. I've seen information on uninstalling a patch and a seen a hotfix for RDP issues, but that still wouldn't help LAN and internet access on the server.
This server ran local RDP access, local client access to the database, and could access the internet for years prior to the recent changes and issues.
Edit: The system I'm remoting into the server with is a Win 7 Pro system, and the database clients are also Win 7 Pro.
Edit 2: I've found information on the VPN "binding" to the port that may have been improperly configured which could be causing the issue.