Check name Issues in Outlook

Possible Steps that can be checked:

1) Check all users are facing the same issue or it’s limited to some users.

2) Check the issue is with all versions on outlook or specific to some version.

3) Check the affected clients is in same subnet or on different sub-net

4) Try to ping the Exchange server name

5) Try to do the check name using the DC/GC name

6) Create new windows profile and then try to create new outlook profile

7) If we have load balancer then try to bypass the load balancer.

8) Check the all Exchange related services are started.

9) Check the LM compatibility value, both on CAS and Client machine. It should be same .navigate to (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa \LmCompatibilityLevel) to check the value

10) Also check the SPN and if we have any ExchangeAB value then Unregister the exchangeAB SPNs from the Exchange server.

Use below command to check the SPN

setspn -L ExchangeServerName

1) Unregister the exchangeAB SPNs from the Exchange server. To do this, follow these steps:

a: At the command prompt, type the following command, and then press ENTER:

setspn -D exchangeAB/ExchangeServerName ExchangeServerName

 b: At the command prompt, type the following command, and then press ENTER:

setspn -D exchangeAB/ExchangeServerName.example.com ExchangeServerName

 2) Register the exchangeAB SPNs with the global catalog server. To do this, follow these steps:

a: At the command prompt, type the following command, and then press ENTER:

setspn -A exchangeAB/GlobalCatalogServerName GlobalCatalogServerName

 b: At the command prompt, type the following command, and then press ENTER:

setspn -A exchangeAB/GlobalCatalogServerName.example.com GlobalCatalogServerName

11) Check the black hole router issue by running the command (ping computer_name or IP_address -f -l 1472). If we are getting result as “Packet need to be fragmented” then follow the method 1 from article # Troubleshoot Black Hole Router Issues

12) Check the RPC client access server is pointing to correct server by running the command (get-mailboxdatabase | fl name,rpc* )

13) We can try to disable the IPv6 if we are facing the check name issue.

For more info:

Outlook Unable to Connect to Exchange

Unable to perform check name

Praveen Kumar

MCTS, MCITP | Exchange Server

Publisher @ Techrid.com