Hey everyone,
I am having a issue in my test environment where i have 2 2000 domains setup. One is called allied.allied-companies.co
m which is the primary DC. The other is fileserver.allied-companie
s.com. I can ping between each DC just fine and i get a reply. I am receiving errors about replication because it cant connect to the DC by its name so it gets an error. The funny thing is when i connect by the ip address it will connect to the shares but then when i try by the name i get:
Logon Failure: The target account name is incorrect.
This happens between both domains if i try and connect to either by the name. Here is the microsoft document i found and ran it and it said it reset the password but still the same error.
On domain controllers that are experiencing this issue, disable the Kerberos Key Distribution Center service (KDC). To do so: 1. Click Start, point to Programs, click Administrative Tools, and then click Services.
2. Double-click KDC, set the startup type to Disabled, and then restart the computer.
After the computer restarts, use the Netdom utility to reset the secure channels between these domain controllers and the PDC Emulator operations master role holder. To do so, run the following command from the domain controllers other than the PDC Emulator operations master role holder:
netdom resetpwd /server:server_name /userd:domain_name\adminis
trator /passwordd:administrator_p
assword
Where server_name is the name of the server that is the PDC Emulator operations master role holder.
For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
260575 (
http://support.microsoft.com/kb/260575/EN-US/) How to Use Netdom.exe to Reset Machine Account Passwords
After you reset the secure channel, restart the domain controllers. Even if you attempt to reset the secure channel using the Netdom utility, and the command does not complete successfully, proceed with the restart process.
If only the PDC Emulator operations master role holder is running, the KDC forces the other domain controllers to resynchronize with this computer, instead of issuing themselves a new Kerberos ticket.
After the computers have finished restarting, start the Services program, restart the KDC service, and then attempt replication again.
Please help me,
Josh
Start Free Trial