DCDiag error

DCDiag error

I'm trying to resolve a problem with our exchange server not authenticating 
accounts in the AD...

One minute users can open Outlook and connect to exchange, the next they 
can't....
Resetting the network connection and simply pinging the DC seems to resolve 
the problem temporarily.

dcdiag results:
   Testing server: Default-First-Site-Name\MHDC
      Starting test: Connectivity
         The host 45b9f6e2-5f64-4aac-b689-8e9f5af0f55e._msdcs.mullenlaw.com 
coul
d not be resolved to an
         IP address.  Check the DNS server, DHCP, server name, etc
         ......................... MHDC failed test Connectivity

Sometimes the message is a little different:

   Testing server: Default-First-Site-Name\MHDC
      Starting test: Connectivity
         The host 45b9f6e2-5f64-4aac-b689-8e9f5af0f55e._msdcs.X could not be 
resolved to an
         IP address.  Check the DNS server, DHCP, server name, etc
Although the GUID DNS Name (45b9f6e2-5f64-4aac-b689-8e9f5af0f55e._msdcs.X) 
could not be resolved, the server name (mhdc.X) resolved to IP address 
(192.168.10.6) and was pingable.  Check that the IP address is registered 
correctly with the DNS server.
         ......................... MHDC failed test Connectivity

Checking the DNS server, there is a CNAME entry there.

We are also getting LDAP events (article 272552) and the Recipient Update 
Services if pointed to the same server....

Any help would be appreciated..

Paul

date: Wed, 27 Feb 2008 08:29:14 -0800 author: Paul MacFarlane

Re: DCDiag error

You haven't installed http://support.microsoft.com/kb/943484 have you?

Oliver

date: Wed, 27 Feb 2008 17:24:44 -0000 author: Oliver Moazzezi [MVP]

Re: DCDiag error

I probably did because we recently updated the server with all the latest 
patches.....

But, I don't see it on the updates list.

Do you know how I can confirm it otherwise?




"Oliver Moazzezi [MVP]"  wrote in message 
news:OeYrmWWeIHA.4312@TK2MSFTNGP03.phx.gbl...
> You haven't installed http://support.microsoft.com/kb/943484 have you?
>
> Oliver
>
>

date: Wed, 27 Feb 2008 09:33:43 -0800 author: Paul MacFarlane

Re: DCDiag error

It isn't on there then. You say you recently patched. Have you gone to SP2?

Oliver

date: Wed, 27 Feb 2008 18:37:32 -0000 author: Oliver Moazzezi [MVP]

Re: DCDiag error

"Oliver Moazzezi [MVP]"  wrote in message 
news:u9SCS$WeIHA.3400@TK2MSFTNGP03.phx.gbl...
> It isn't on there then. You say you recently patched. Have you gone to 
> SP2?
>
> Oliver

Yep - we did install SP2..

date: Wed, 27 Feb 2008 11:10:04 -0800 author: Paul MacFarlane

Re: DCDiag error

"Oliver Moazzezi [MVP]"  wrote in message 
news:u9SCS$WeIHA.3400@TK2MSFTNGP03.phx.gbl...
> It isn't on there then. You say you recently patched. Have you gone to 
> SP2?
>
> Oliver

I'm a little confuse on your original question?  Is KB943484 a problem or a 
solution? <g>

Paul

date: Wed, 27 Feb 2008 11:16:23 -0800 author: Paul MacFarlane

Re: DCDiag error

KB943484 is a problem, it limits LDAP returns and causes issues with 
Exchange.

You may want to check the SP2 Scalable Networking features, and ensure your 
NIC drivers are fully supported.

Check: http://msexchangeteam.com/archive/2007/07/18/446400.aspx

Oliver

date: Thu, 28 Feb 2008 11:28:27 -0000 author: Oliver Moazzezi [MVP]

Re: DCDiag error

Thanks Oliver,

Our problem went away since installing new NIC drivers on the 27th....

But....  it came back this morning....

So, I'm still a little confused.... "KB943484 is a problem" - I thought it 
was the solution

I'm running W2k3 SP2 and I should download the patch suggested by this 
article...

"Oliver Moazzezi [MVP]"  wrote in message 
news:Ox$FL0feIHA.1212@TK2MSFTNGP05.phx.gbl...
> KB943484 is a problem, it limits LDAP returns and causes issues with 
> Exchange.
>
> You may want to check the SP2 Scalable Networking features, and ensure 
> your NIC drivers are fully supported.
>
> Check: http://msexchangeteam.com/archive/2007/07/18/446400.aspx
>
> Oliver
>
>

date: Mon, 3 Mar 2008 12:26:26 -0800 author: Paul MacFarlane