cancel
Showing results for 
Search instead for 
Did you mean: 

What to check when Prognosis Client GUI gets 'Connection to server failed' message?

Support_Sydney
Moderator

What to check when Prognosis Client GUI gets 'Connection to server failed' message?

When connecting the GUI to a server, the error ‘Connection to <server name> failed’ occurs.

1 ACCEPTED SOLUTION

Accepted Solutions
Support_Sydney
Moderator

Re: What to check when Prognosis Client GUI gets 'Connection to server failed' message?

When connecting the GUI to a server, the error ‘Connection to <server name> failed’ occurs.
There are a number of things that can be checked when this behaviour is seen.

• Confirm the server IP address using ‘nslookup’ with the supplied host name.
• Ping both the hostname and IP address of the server. The IP address can be used in the Server field if there is a DNS issue.
• The default ports are 1960-1964. Check if any firewalls or routers exist between the GUI and Server and ensure they have these ports opened.
• Run # netstat –an|grep 1960 {or port being used if not the default port(s) }
• Is Prognosis service actually running - this opens up port 1960.
• Check the port PROGNOSIS is using by running the Service Control Panel (on Windows) or using 'ircnfutl' to list the Network configuration on UNIX or HpNonStop.
• Ensure this is the same port set in the Port field of the dialog for login.

View solution in original post

1 REPLY 1
Support_Sydney
Moderator

Re: What to check when Prognosis Client GUI gets 'Connection to server failed' message?

When connecting the GUI to a server, the error ‘Connection to <server name> failed’ occurs.
There are a number of things that can be checked when this behaviour is seen.

• Confirm the server IP address using ‘nslookup’ with the supplied host name.
• Ping both the hostname and IP address of the server. The IP address can be used in the Server field if there is a DNS issue.
• The default ports are 1960-1964. Check if any firewalls or routers exist between the GUI and Server and ensure they have these ports opened.
• Run # netstat –an|grep 1960 {or port being used if not the default port(s) }
• Is Prognosis service actually running - this opens up port 1960.
• Check the port PROGNOSIS is using by running the Service Control Panel (on Windows) or using 'ircnfutl' to list the Network configuration on UNIX or HpNonStop.
• Ensure this is the same port set in the Port field of the dialog for login.

View solution in original post