none
Outlook Name Resolve RRS feed

  • Question

  • Running Exchange 2010 with various versions of Outlook connecting to the server. Recently several users have not been able to connect to Exchange server with Outlook, either the users name does not resolve or when checking the profile an error indicating the Exchange server is offline is shown. This happens with an existing profile or when setting up a new profile for the user. The only way to setup the user in Outlook is when creating the profile to point user at a domain controller that is also a GC, the user name is resolved and able to connect to Outlook.

    Even after setting up the user with the DC server they do not resolve when using the Autodiscover settings or when pointing to any Exchange server. Any idea why point the user at the DC/GC works and using the Exchange server does not? This only happens with a handful of the users, about 500 users work correctly.

    Bill Jones

    Tuesday, January 17, 2012 3:45 PM

Answers

  • Hi Bill,

    Are these handful of users located at a separate site? Or even a subnet that isn't associated with a site that in turn has global catalog servers in it?

    From one of their machines, does running the following command return a valid list of global catalog servers? If so, they're not separated by firewalls or anything else that might prevent communication?

    nslookup -type=SRV _gc._tcp.yourDomain.com

    On the surface of it all, it sounds more like an AD/name resolution issue than something on the Outlook/Exchange side of things.

    Cheers,
    Lain

    Tuesday, January 17, 2012 11:59 PM