DC Issue

I have a DC at a remote site that can communicate and performs normally with it clients and the rest of the DCs in the env. The issue I have is I cannot communicate with it from any other site. If I try to map to it I get this error...

The kerberos client received a KRB_AP_ERR_MODIFIED error from the server host/ypw01-svr-001.hydro.local.  The target name used was cifs/ypw01-svr-001.hydro.local. This indicates that the password used to encrypt the kerberos service ticket is different than that on the target server. Commonly, this is due to identically named  machine accounts in the target realm (HYDRO.LOCAL), and the client realm.   Please contact your system administrator.

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

chadfranAuthor Commented:
However via IP I can....
Darius GhassemCommented:
Make sure you are only pointing to internal DNS servers. Plus if you have two NICs in the system disable one of the NICs.
chadfranAuthor Commented:
I'm using its own and one of our other remote DNS servers that it has connection to. I've disabled all 4 nics except the one being used.
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Darius GhassemCommented:
Run ipconfig /registerflushdns, ipconfig /regsiterdns, and dcdiag /fix. Make sure that both servers only have one NIC enabled.
Might be that you have a SPN registered on two different hosts (cifs/ypw01-svr-001).

Here are some methods to find them:


Or a script: http://technet.microsoft.com/en-us/library/ee176972.aspx
chadfranAuthor Commented:
I created the script. Named it Test.vbs. Copied it to my DC. Ran it with Test.vbs cifs/ypw01-svr-001 and got No SPNs found
Try with: */ypw01-svr-001*
chadfranAuthor Commented:
ok a lot comes up now, what am I looking for?
Identical SPN's. A SPN should not be registered twice.

host/server1 --> (identical)

host/server1 --> (identical)

A host will register its SPN with both NetBIOS name and FQDN.
chadfranAuthor Commented:
I don't see an issue...Am I missing something...

CN=YPW01-SVR-001,OU=Domain Controllers,DC=hydro,DC=local
Class: computer
Computer DNS: ypw01-svr-001.hydro.local
-- NtFrs-88f5d2bd-b646-11d2-a6d3-00c04fc9b232/ypw01-svr-001.hydro.local
-- exchangeAB/YPW01-SVR-001
-- exchangeAB/YPW01-SVR-001.hydro.local
-- ldap/YPW01-SVR-001.hydro.local/DomainDnsZones.hydro.local
-- ldap/YPW01-SVR-001.hydro.local/ForestDnsZones.hydro.local
-- DNS/YPW01-SVR-001.hydro.local
-- GC/YPW01-SVR-001.hydro.local/hydro.local
-- HOST/YPW01-SVR-001.hydro.local/hydro.local
-- HOST/YPW01-SVR-001.hydro.local/HYDRO
-- ldap/YPW01-SVR-001.hydro.local/HYDRO
-- ldap/YPW01-SVR-001
-- ldap/YPW01-SVR-001.hydro.local
-- ldap/YPW01-SVR-001.hydro.local/hydro.local
-- HOST/YPW01-SVR-001
-- HOST/YPW01-SVR-001.hydro.local
-- ldap/480e1d9a-2bcb-44b9-9e2b-efee6de8e97c._msdcs.hydro.local
-- E3514235-4B06-11D1-AB04-00C04FC2DCD2/480e1d9a-2bcb-44b9-9e2b-efee6de8e97c/hyd

C:\Documents and Settings\admchadfran\Desktop>


CN=YND01-SVR-001,OU=Domain Controllers,DC=hydro,DC=local
Class: computer
Computer DNS: ynd01-svr-001.hydro.local
-- ldap/ynd01-svr-001.hydro.local/DomainDnsZones.hydro.local
-- ldap/ynd01-svr-001.hydro.local/ForestDnsZones.hydro.local
-- NtFrs-88f5d2bd-b646-11d2-a6d3-00c04fc9b232/ynd01-svr-001.hydro.local
-- HOST/ynd01-svr-001.hydro.local/HYDRO
-- HOST/ynd01-svr-001.hydro.local/hydro.local
-- GC/ynd01-svr-001.hydro.local/hydro.local
-- ldap/YND01-SVR-001
-- ldap/ynd01-svr-001.hydro.local/HYDRO
-- ldap/5e21e39c-3f2e-4a15-8006-55b574f17f44._msdcs.hydro.local
-- DNS/ynd01-svr-001.hydro.local
-- ldap/ynd01-svr-001.hydro.local/hydro.local
-- ldap/ynd01-svr-001.hydro.local
-- E3514235-4B06-11D1-AB04-00C04FC2DCD2/5e21e39c-3f2e-4a15-8006-55b574f17f44/hyd
-- HOST/YND01-SVR-001
-- HOST/ynd01-svr-001.hydro.local
When you say you can't communicate with the host from any other site, do you mean connecting to a network share on the host?

The service type CIFS will map to the default service type HOST (an alias for many service types), so you will not find the CIFS/YPW01-SVR-001 SPN on a GC.

Do you have one domain with many site in a forest, or multiple domains in the forest?
chadfranAuthor Commented:
One domain with many sites in a forest.
chadfranAuthor Commented:
Yes through the share.
Do you get any errors using the DNS name connecting to the share?

ie. \\YPW01-SVR-001.hydro.local\sharename
chadfranAuthor Commented:
Yess same error. Logon Failure: The target account name is incorrect then the event log above gets logged.

I think the secure channel is broken in this scenario.

1. Can you access shares on any other DCs from YPW01-SVR-001 ? If yes then you have to reset the secure channel of YPW01-SVR-001.

2. If you can not access the shares from YPW01-SVR-001 as well, then we need to know how many DCs we are not able to access. (in this case, I would need to know how many DCs you have, which onw is the PDC and which all DCs are not accessible from YPW01-SVR-001 - a diagram would be best to understand).

In first case, please run this command on the YPW01-SVR-001 DC:

repadmin /resetpwd /server:PDC.domain.local /Userd:domain\Administrator /passwordd:Password

This will update the machine account password of YPW01-SVR-001.

I think this should help. In case this is the 2nd case, please provide me with the details I asked for.


chadfranAuthor Commented:
It is the first case...So I'll attempt running the command this weekend. If it doesn't resolve the issue then I'll demote the server. Remove any DNS entries. And then repromote the server to see if that resolve the issue.
chadfranAuthor Commented:
Ok so running the repadmin corrected the issue. I'm able to map to the server via share now. However now I'm getting...

EventID:1097 Windows cannot find the machine account, The logon attempt failed .
EventID:1030 Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this.

Every few minutes.
chadfranAuthor Commented:
I demoted and promoted the server. All is fine again.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.