Overview

Some users may encounter an issue where they are unable to access the Global Address Book, receiving an error message 'Directory server not responding'. This issue can be inconsistent, with some users on the same network able to access the Global Address Book without any problems. Despite troubleshooting steps such as ensuring a stable internet connection, restarting devices, and trying to access from a different network or device, the issue may persist. The root cause of the problem is related to certain parameters on the server that need to be added or adjusted.

Solution

To resolve this issue, the following parameters need to be added on the server:

• sec.TLS.profileSelection.SOPI='PlatformProfile1'
• sec.TLS.SOPI.cipherList='NoCipher'
• sec.TLS.SOPI.strictCertCommonNameValidation='0'

After adding these parameters, the devices should be rebooted. If the problem persists, the parameter `dir.local.serverFeatureControl.reg` should be changed to 1, and the devices should be restarted again.

Summary

This article provides a solution to the 'Directory server not responding' error that some users may encounter when trying to access the Global Address Book. The solution involves adding or adjusting certain parameters on the server and rebooting the devices.

FAQ

1. What causes the 'Directory server not responding' error?
   The error is caused by certain parameters on the server that need to be added or adjusted.
2. What should I do if the problem persists after adding the recommended parameters and rebooting the devices?
   If the problem persists, the parameter `dir.local.serverFeatureControl.reg` should be changed to 1, and the devices should be restarted again.
3. Can this issue affect all users on the same network?
   No, this issue can be inconsistent, with some users on the same network able to access the Global Address Book without any problems.