Link to home
Start Free TrialLog in
Avatar of cascade99
cascade99

asked on

Domain controller not accessible from a second domain controller

We have a very simple network: about 10 W2K machines and a few NT4 machines. We have two domain controllers: Ajax and Zebra. Ajax can see the drives of Zebra. But Zebra cannot see the drives of Ajax. When I attempt to view Ajax drives from Zebra, I get this message:
\\Ajax is not accessible.
Logon failure: The target account name is incorrect.

We logon to both machines with the same admin logins (administrator), the same passwords, and the same domain. I can go to the Active Directory on both machines, and see the same settings for both machines under Domain Controllers. Both are members of Administrators, Domain Administrators, and Domain Controllers. Both are W2K with the latest updates, and are reliable servers. Not too long ago, this was not a problem. I sure wish I knew what I did to cause this problem. All i can think of is that I tightened security on some network drives. We have had Ajax for > 4 years. We have had Zebra about 1 year. Both were fine till yesterday.

There is another interesting tidbit that I hope is a clue. That is, I can see Ajax from all the other machines on the network except for one, Kary. Kary is a brand new W2K workstation. It gives me the same error message that I get from Zebra (Target account name is incorrect) when I try to access Ajax. I logon as Administrator on Kary using the same domain .

Am at wits end on this one, and really need to get it solved ASAP. Thanks!
ASKER CERTIFIED SOLUTION
Avatar of trywaredk
trywaredk
Flag of Denmark image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Avatar of Rich Rumble
Rich Rumble
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of cascade99
cascade99

ASKER

This was crazy. We finally had a LAN consultant come in. Apparently the configuration settings were ok. Doing a cold (power all the way off) reboot cleared caches that were the fundamental cause of the problem. So I will simply split the points three ways, out of gratitude for trying to help.
Didn't you know that reboots fix everything in M$ ? I always assume people have done them a few times before coming here !-)
-rich
:o) Glad we could help each other - thank you for the points
To richrumble: I agree. I reboot everything all the time, problems or not. But I don't usually worry about a cold reboot. I've always thought a warm reboot amounted to the same thing. Are you saying that it is your experience that that makes a difference?