Skip to main content
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    GUI client gets "Failed to connect to host" logging in

    • Article Type: General
    • Product: Aleph
    • Product Version: 20

    GUI client gets "Failed to connect to host", in the center of the screen, logging in.

    If the "Failed to connect to host" occurs after successful log-in, see Article 000019667.

    If the pc_server log shows no response to your attempted login, some possible reasons are:

    (1) the server address or port (in the library.ini file) is wrong,
    (2) the server is down,
    (3) the server's firewall (or, for a hosted site, the site's firewall) is preventing access to this port by this pc's ip-address.

    If the pc_server log *does* show a response, see Article 000002818.

    To diagnose if #2 might be the cause, go to the server and do util w/1/4 (to see if the pc_server is up). Verify that the port number you are checking for is the same as that in the pc's library.ini file.

    For #1 or #3, examine the $LOGDIR/pc_server_6nnn.log. Does the log show a response to your attempt to connect (such as the presence of your ip address in the log)? If not, then it may be that you are going to the wrong address/port or a firewall problem. See Articles 000025788 ("Diagnosing firewall problems") and 000033737 for an example of a firewall problem. ( )

    Compare your library.ini entry to that of someone who *is* connecting successfully. [See also Article 000033739. ( ).]

    If you’re connecting with a hostname which is more than 30 characters and the numeric IP works,
    consult Article 000033738 ("GUI 'Failed to connect to host' connecting with hostname; OK, with numeric IP") ( )

    • Article last edited: 3/3/2015