Connection Problems

PreviousNext

Home

 

Connection Problems

1. Enable the AADS RDP Firewall

See the AADS Manual  for details.

DO NOT disable the AADS RDP Firewall

Don't be tempted to disable the AADS built-in Firewall. Too often we receive ZIP Support Files with loglines indicating many hack-attempts because of a disabled AADS RDP Firewall or no Firewall at all. This also applies to local networks. If one (or more) of the Client PCs is hacked, infected, the virus on the Client PCs may attempt to login on the AADServer and is doing many RDP-logins. Regularly we receive ZIP Support Files with these type of problem...

 

2. Attempt to connect for a Client.

 

3. Look at the RDP or SSL logging

Look at the RDP or SSL Logging, and see if the Client PC and its IP Address does appear in the logging when it is attempted to connect.

 

The Client and its IP Address do not appear in the RDP or SSL Logging

If the Client and its IP Address do not appear in the RDP or SSL Logging, then something "before" the AADServer is blocking the connection, or is not allowing the connection.

 

The Client and its IP Address do appear in the RDP or SSL Logging

If the Client and its IP Address do appear in the RDP or SSL Logging, the RDP and the SSL logging do also tell you why the connection is blocked. For example, because

Occasionally it happens there is a "less important" reason why a connection is blocked:

 


Copyright 2012-2018 AADS WorldWide LTD. AADS Terminal Server | Application Server | Remote Desktop solutions | Firewall

PreviousNext

Home