Accessing Issues

July 4, 2007

I have a setup a domain on our test bench to test some disaster recovery

scenarios. It has 2 windows 2003 Sp1 servers. One server is a domain

controller and the second server is an exchange server 2003. Everything

was working fine. I tested a disaster recover scenario where I trashed the

exchange server 2003 and then rebuilt it again to see if I could recover it.

I made backups of the system state and exchange server database.

I have put this exchange 2003 server back on the test domain again as part

of the recovery process.

The problem I have know is that I can ping the domain controller from the

exchange server but I cannot do vice versa, meaning I cannot ping the

exchange server from the domain controller. I have checked all the network

settings and they are all fine. But if i create an AD account I can use

that account to log into the exchange server, so the domain part is ok., but

I dont know why i cannot ping the exchange server from the domain

controller. This causes me issues as I cannot install some remote backup

agents from the domain controller to the exchange server which I need to a

restore.

I have checked the event logs of the domain controller server and since I

have started to get this issue I have started to get the following warnings

in the system log:

Event ID: 40960

Source: LSASRV

The Security settings detected an anuthentication erro for the server

LDAP\<Domain Controller Server Name>. The failure code from Authentication

protocol kerberos was 'There are currently no logon servers available to

service logon requests'

I also got some ipsec events saying that the ipsec driver is started in

bymass mode. I have no idea why the ipsec message is appearing but I

disabled the ipsec service, but still get that event logs.

I also got some NTPClient messages about the W32time.

But I am more concerned about the LSASRV error log.

From this can anyone advise why the the domain controller cannot ping the

exchange server.

Recommended Posts