exchangefreaks.com Forum Index
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

dcdiag fails connectivity test

 
Post new topic   Reply to topic    exchangefreaks.com Forum Index -> MS Exchange Setup
Author Message
Paul MacFarlane



Joined: 05 Aug 2007
Posts: 10

PostPosted: Wed Feb 27, 2008 1:28 pm    Post subject: dcdiag fails connectivity test Reply with quote

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

Archived from group: microsoft>public>exchange>setup
Back to top
View user's profile Send private message
John Oliver, Jr. [MVP]



Joined: 05 Aug 2007
Posts: 823

PostPosted: Wed Feb 27, 2008 9:52 pm    Post subject: Re: dcdiag fails connectivity test Reply with quote

Did you download and run ExBPA against your Exchange Server? What version
of Exchange and OS of system?

--
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2008
Microsoft Certified Partner


"Paul MacFarlane" wrote in message
news:%23g9oQ3VeIHA.3368@TK2MSFTNGP02.phx.gbl...
> 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
>
>
>
>
>
Back to top
View user's profile Send private message
Paul MacFarlane



Joined: 05 Aug 2007
Posts: 10

PostPosted: Wed Feb 27, 2008 9:07 pm    Post subject: Re: dcdiag fails connectivity test Reply with quote

Thank John...

No I haven't. I will because we are currently on Ex2003 and going to 2007
soon.

We did resolve the problem. It turns out it was a problem with a NIC
driver. A W2k3 update was incompatible with older drivers...
James in the connectivity group told me about it...

Paul


"John Oliver, Jr. [MVP]" wrote in message @TK2MSFTNGP03.phx.gbl...
> Did you download and run ExBPA against your Exchange Server? What version
> of Exchange and OS of system?
>
> --
> John Oliver, Jr
> MCSE, MCT, CCNA
> Exchange MVP 2008
> Microsoft Certified Partner
>
>
> "Paul MacFarlane" wrote in message
> news:%23g9oQ3VeIHA.3368@TK2MSFTNGP02.phx.gbl...
>> 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
>>
>>
>>
>>
>>
>
>

Back to top
View user's profile Send private message
Display posts from previous:   
Related Topics:
new test install I would like to familiarize myself with exchange 2007 with a test server. I don't currently have any version of exchange but I do have a functioning AD domain. Would I be foolish to try to install this test server connected to my live domain? It would

Need Public MX record for test home mail server Is there a way i can get emails working in and out of the internet without a valid registered domain name? I can send email to yahoo. but obviously cant reply back in to my ex 2007 environment. To make matters worse, i also have a dynamic IP address. wha

SP1 installation fails Hi When trying to install SP1 on our Exchange 2007 HUB/CAS server, the installation fails because it cannot stop the We have tried to stop it manually but it wont work. The service must be running when starting sp1 setup. Ha

CAS Install Fails I had a CAS server installed first, which was uninstalled clean and then build the machine again. Now when I try to install the CAS server on it... I get the Remote Registry error. Summary: 1 item(s). 0 succeeded, 1 failed. Elapsed time: 00:02:06 Client A

2007 installation fails I am trying to install Exchange 2007 from a windows/ Exchange 2000 domain. I have 4 DC's, 2 running Windows 2003, the other 2 Win 2000. I transfered all the roles to the one 2003 DC except infratructure master. It is also a GC . I am trying to install exc
Post new topic   Reply to topic    exchangefreaks.com Forum Index -> MS Exchange Setup All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group