Logon to particular AD server not working

[Guest]

I have a network with 2 servers, both in the same domain, replication of AD
is working properly. The problem is, that only one server (B) can be used for
logging in our clients. When server B is down for some reason, users are not
able to logon to the network via server A. When both servers are ON,
everything works fine, both servers are accessible. When server B is down, I
am also not able to start server A, it stays during startup process with
message Preparing network connections ....
DNS is running on server A.
Any suggestions?
Thanks
Ivan

 

[Guest]

I have more details:
I tried dcdiag utility on server A and it is saying:
SERVER is not advertising as a Key Distribution Center

ISMserv Service is stopped
kdc Service is stopped
TrkServ Service is stopped

Now I undersatnd, why it does not work, but I have no idea, why it is
stopped. When I go to Services, I can see, that all three services are
Disabled. Originally it was working. On this A server Microsoft Exchange
Server 2000 is running (I know it is not recommended to run it on AD server,
but I have no other option), but do you think these services could be
automatically turned off during Exchange Server 2000 installation?
Thanks.
Ivan

 

[Harj]

Hi,

Well you can enable auditing to see if anything is stopping the
services that you mention above, or look through the event logs to see
when the services stopped.
Are both of these machines Global Catalog servers? If not, I would set
both of them to GC's.
I cannot see Exchange causing this and tsk tsk for installing Exchange
on a DC, but I guess we can only work with what we have right?


Harj Singh
Power Your Active Directory Investment
www.specopssoft.com