Error messages in client programs

Can't open/find server, can't connect to server, server not responding

The client and ClickMail are not talking to each other. Can be caused by improper settings in the client, improper TCP/IP settings on the client or ClickMail Mac, or network failures.

To observe whether the client is reaching ClickMail, watch the ClickMail log window for activity when the client is used.

Make sure the IP address or host name entered for ClickMail in the client program's settings is correct.

Make sure that TCP/IP settings on the client computer and the ClickMail Mac are both correct, and that they are both connected to the network.

Verify that the client computer can "see" the ClickMail Mac—that the TCP/IP connection works. This is best done with a TCP/IP "Ping" utility run on the client. If there is a web or email server running on the ClickMail Mac, try accessing that service from the client.

Denied access, insufficient access

The client has been blocked by ClickMail's database permissions. Or, the client is attempting to log in with a password, and logged-in access is not enabled or the password is wrong.

In ClickMail's Database Permissions, check that the proper read access is enabled. If an IP range is in use, verify that the range includes the IP address of the client computer.

Check if client settings are configured to log in (authenticate). If so, make sure logged in access is enabled in Database Permissions. If an IP range is enabled for logged in users, make sure the IP range includes the IP address of the client computer. Make sure the password entered in the client's settings match the password attribute value in that user's entry. Make sure the user name or distinguished name entered in the client program is correct.

Base object outside naming context (included in LDAP error 32)

The client specified a base object (a distinguished name, usually in its preferences) that did not match the directory's naming context, or the base object did not have the same ending as the naming context. Change the client program setting. For basic lookups, leave the base object blank.

DN not found (included in LDAP error 32)

The client specified a base object (requested a specific entry) that is in the directory's naming context, but no entry exists with that distinguished name. The dn logged (and possibly displayed by the client) is the closest ancestor that does exist. So a smart client could try again with that dn.