DCDiag connectivity error - exchange server loses connection

Paul MacFarlane · Joined: 05 Aug 2007 Posts: 10

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
could 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>admin

Jamestechman · Joined: 05 Aug 2007 Posts: 200

See if this applies.

Windows 2003 Scalable Networking pack and its possible effects on
Exchange
http://msexchangeteam.com/archive/2007/07/18/446400.aspx

James Chong (MVP)
MCITP | EMA; MCSE | M+, S+, Security+
msexchangetips.blogspot.com

On Feb 27, 11:30 am, "Paul MacFarlane"
wrote:
> 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
> could 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

Paul MacFarlane · Joined: 05 Aug 2007 Posts: 10

Thanks James -

That may be it. The drivers I have are outdated and we recently went to
SP2.....

"Jamestechman" wrote in message @n75g2000hsh.googlegroups.com...
See if this applies.

Windows 2003 Scalable Networking pack and its possible effects on
Exchange
http://msexchangeteam.com/archive/2007/07/18/446400.aspx

James Chong (MVP)
MCITP | EMA; MCSE | M+, S+, Security+
msexchangetips.blogspot.com

On Feb 27, 11:30 am, "Paul MacFarlane"
wrote:
> 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
> could 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

Paul MacFarlane · Joined: 05 Aug 2007 Posts: 10

James - thank you....

Updated the drivers and the errors have gone....

"Jamestechman" wrote in message @n75g2000hsh.googlegroups.com...
See if this applies.

Windows 2003 Scalable Networking pack and its possible effects on
Exchange
http://msexchangeteam.com/archive/2007/07/18/446400.aspx

James Chong (MVP)
MCITP | EMA; MCSE | M+, S+, Security+
msexchangetips.blogspot.com

On Feb 27, 11:30 am, "Paul MacFarlane"
wrote:
> 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
> could 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

user loses permission to access his mailbox in exchange 2007 After upgrading to exchange 2007 I have had some strange user permissions problems. It started with two people getting this error: "Cannot start Microsoft Office Outlook. Unable to open the Outlook window. The set of folders could not be opened." From

The connection to the MS Exchange Server is Unavailable...pl I am looking for the help of an Exchange guru who can help me with the dreaded "The connection to the Microsoft Exchange Server is error. Here is our setup: We use a remote, managed, Exchange 2003 Server for email and group calendar. We c

Service Connection Points / Exchange Server 2007 Good afternoon! I am trying to wrap my head around this but am coming up a bit short. We have put in four Exchange 2007 Servers in the last week or so. I am doing most of it (God only help our clients). I am getting the vast majority of things but am ru

Inconsistent connection (attempting to restore connection to I'm running Exchange 2003 SP2 and my users are experiencing inconsistent connection to the database server. Sometimes it will just say "Exchange has lost contact with the database" and then "attempting to restore connection". It eventually comes back but

Exchange 2007 OWA error - Server Error in '/' Application Server Error in '/' Application. The resource cannot be found. Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following U