If the macOS client does not establish a connection to Password Depot Enterprise Server or hangs right after logging in, the cause is usually an incorrectly selected server main version in the login dialog, a server setting that blocks macOS clients, an outdated client, or a corrupted local cache. Work through the following checklist in order.
Check the server main version in the login dialog. Unlike the Windows client, which must have the same main version as the Enterprise Server, the macOS client may also be newer than the server: As of version 15, it can connect to servers with older main versions. To do so, select the main version of your Enterprise Server in the login dialog – the port is adjusted automatically. An incorrect version selection is one of the most common causes of failed logins.
Server settings: allow the macOS Edition. The Enterprise Server only accepts client types that are enabled in its settings. In the Server Manager, open Manage → Server settings, go to the Connections tab, section Supported clients, and enable macOS Edition. The option is enabled by default but may have been disabled by the administrator. If it is disabled, the server rejects macOS logins with the message "This client application is not supported. Please use another one or contact the administrator of Password Depot Enterprise Server."
Check the network. The same basic rules apply as for all clients: The server address and port must be correct (default port of version 19: 25019, TCP and UDP), and firewalls between the Mac and the server must allow the port. Each server main version uses its own default port; with the version selection from step 1, the client sets the port automatically.
Update the macOS client. Install the latest version of the macOS client from the Password Depot website (Download Password Depot for Windows, macOS & More Free).
Reset the "Network" cache folder. If the connection still fails, quit Password Depot and rename the Network cache folder (for example, to "Network-old"). It is located in the Password Depot app container under Library/Containers in your home folder; the "Library" folder is hidden in the Finder by default. On the next launch, the client recreates the cache – then try logging in again.
Note: To narrow down the cause, check whether a different client (Windows client, Web Client) can connect to the same server. If that fails as well, the cause is more likely the server or the network – see the socket error checklist and the firewall settings under "Related topics".
Related topics: