Connecting to servers¶
Problem | Symptoms and solution |
---|---|
Cannot connect to server | Symptoms:
|
Solution:
|
|
Symptoms: events log entry: Unable to establish connection to server zbigniew (10.0.35.53:3399). | |
Cause: incorrect server configuration. | |
Solution:
|
|
|
|
Problem | Symptoms and solution |
---|---|
When logging in not all of the users see the Wheel Fudo PAM logon screen. | Cause:
|
Symptoms:
|
|
Cause: incorrect login credentials. | |
Solution: provide correct login credentials in server configuration. | |
Symptoms:
|
|
Cause: server has been blocked. | |
Solution: log in to Wheel Fudo PAM administration panel and unblock the server. | |
Problem | Symptoms and solution |
---|---|
Connection is terminated | Symptoms:
|
Solution: | |
Download new target host certificate in the Target host section. | |
Symptoms:
|
|
Solution: check if in the General tab in TCP-Rdp properties, the Encryption level option is not set to FIPS Compliant. | |
Cannot connect to server | Symptoms:
|
Cause: user is not assigned to proper connection. | |
Solution: add user to appropriate connection object. |
Problem | Symptoms and solution |
---|---|
Symptoms:
|
|
Cause: user is blocked. | |
Solution: log in to Wheel Fudo PAM administration panel and unblock the user in question. | |
User has to provide login credentials twice | Symptoms: user connecting over RDP protocol enters login credentials and immediately afterwards is asked again for the same login information. |
Cause: server is a part of an infrastructure managed by connections broker which has detected an active user’s session on another server. | |
Symptoms: user connecting over SSH protocol enters login credentials and immediately afterwards is asked again for login information. | |
Cause: in connection object options for login and password substitution are enabled but the input fields are left blank which results in two fold authentication - first time against Wheel Fudo PAM and second time against the target host. | |
Cannot connect to server over RDP protocol | Symptoms:
|
Cause: connection is redirected to a host which does not listen on port number 3389. | |
Solution: configure server in question so it accepts user connections on port number 3389. | |
Symptoms:
|
|
Cause: connections broker determines an existing user session on another server and redirects user to that host but it is not configured on Wheel Fudo PAM or the user does not have sufficient access rights to connect to given server. | |
Solution:
|