UNC path logon failure: The target account name is incorrect
Hi
The setup at the customer:
There are 7 sites. 6 of them have at least one DC/GC server. A mix of W2K, W2K3, W2K8
Site 1:
Milano: W2K --> DC/GC
Berlin: W2K3 --> DC/GC, Exchange and Holds all the FSMO roles
Verona: W2K --> DC/GC
Site 2:
Bari: W2K3 --> DC/GC, Exchange
NewYork: W2K --> DC/GC
Site 3:
Madrid: W2K8 R2 --> DC/GC
Site 4:
Faro: W2K3 --> DC/GC
Site 5:
Napoli: W2K8 R2 --> DC/GC
Site 6:
no servers
Site 7:
Boston: W2K --> DC/GC
Chicago: W2K --> DC/GC
All the sites are directly connected with each other however I think that there are also site link bridges setup. I must admit that i'm not that familiar with sites and replications.
The problem we have now is:
From all the sites we can connect to \\bari but from Site 2, where Bari sits, we cannot and receive the error logon failure: The target account name is incorrect.
Connecting to IP address does work. Ping -a and nslookup resolves correctly.
Plz help.
Thx
Filip
The setup at the customer:
There are 7 sites. 6 of them have at least one DC/GC server. A mix of W2K, W2K3, W2K8
Site 1:
Milano: W2K --> DC/GC
Berlin: W2K3 --> DC/GC, Exchange and Holds all the FSMO roles
Verona: W2K --> DC/GC
Site 2:
Bari: W2K3 --> DC/GC, Exchange
NewYork: W2K --> DC/GC
Site 3:
Madrid: W2K8 R2 --> DC/GC
Site 4:
Faro: W2K3 --> DC/GC
Site 5:
Napoli: W2K8 R2 --> DC/GC
Site 6:
no servers
Site 7:
Boston: W2K --> DC/GC
Chicago: W2K --> DC/GC
All the sites are directly connected with each other however I think that there are also site link bridges setup. I must admit that i'm not that familiar with sites and replications.
The problem we have now is:
From all the sites we can connect to \\bari but from Site 2, where Bari sits, we cannot and receive the error logon failure: The target account name is incorrect.
Connecting to IP address does work. Ping -a and nslookup resolves correctly.
Plz help.
Thx
Filip
David Atkin
Have you done a DCdiag and checked the replication?
ASKER
Here you go. And thanks for the quick response.
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Technical\BARI
Starting test: Connectivity
......................... BARI passed test Connectivity
Doing primary tests
Testing server: Technical\BARI
Starting test: Replications
[Replications Check,BARI] A recent replication attempt failed:
From NEWYORK to BARI
Naming Context: CN=Schema,CN=Configuration
The replication generated an error (8456):
The source server is currently rejecting replication requests.
The failure occurred at 2013-04-30 09:57:01.
The last success occurred at 2013-02-10 12:55:45.
7563 failures have occurred since the last success.
Replication has been explicitly disabled through the server options.
[NEWYORK] DsBindWithSpnEx() failed with error 1722,
The RPC server is unavailable..
[Replications Check,BARI] A recent replication attempt failed:
From NEWYORK to BARI
Naming Context: CN=Configuration,DC=domain
The replication generated an error (8456):
The source server is currently rejecting replication requests.
The failure occurred at 2013-04-30 09:57:01.
The last success occurred at 2013-02-10 12:55:45.
14958 failures have occurred since the last success.
Replication has been explicitly disabled through the server options.
[Replications Check,BARI] A recent replication attempt failed:
From NEWYORK to BARI
Naming Context: DC=domain,DC=be
The replication generated an error (8456):
The source server is currently rejecting replication requests.
The failure occurred at 2013-04-30 09:57:01.
The last success occurred at 2013-02-10 12:55:45.
22879 failures have occurred since the last success.
Replication has been explicitly disabled through the server options.
REPLICATION-RECEIVED LATENCY WARNING
BARI: Current time is 2013-04-30 10:06:19.
CN=Schema,CN=Configuration
Last replication recieved from MILANO at 2013-01-24 12:18:44.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from PORTO at 2012-10-11 08:54:38.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from NEWYORK at 2013-02-10 12:55:45.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
CN=Configuration,DC=domain
Last replication recieved from PORTO at 2012-10-11 08:59:56.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from NEWYORK at 2013-02-10 12:55:45.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
DC=domain,DC=be
Last replication recieved from PORTO at 2012-10-11 09:00:26.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from NEWYORK at 2013-02-10 12:55:45.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
......................... BARI passed test Replications
Starting test: NCSecDesc
......................... BARI passed test NCSecDesc
Starting test: NetLogons
......................... BARI passed test NetLogons
Starting test: Advertising
Warning: BARI is not advertising as a time server.
......................... BARI failed test Advertising
Starting test: KnowsOfRoleHolders
......................... BARI passed test KnowsOfRoleHolders
Starting test: RidManager
......................... BARI passed test RidManager
Starting test: MachineAccount
......................... BARI passed test MachineAccount
Starting test: Services
......................... BARI passed test Services
Starting test: ObjectsReplicated
......................... BARI passed test ObjectsReplicated
Starting test: frssysvol
......................... BARI passed test frssysvol
Starting test: frsevent
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may cause
Group Policy problems.
......................... BARI failed test frsevent
Starting test: kccevent
......................... BARI passed test kccevent
Starting test: systemlog
......................... BARI passed test systemlog
Starting test: VerifyReferences
......................... BARI passed test VerifyReferences
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Running partition tests on : domain
Starting test: CrossRefValidation
......................... domain passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... domain passed test CheckSDRefDom
Running enterprise tests on : domain.be
Starting test: Intersite
......................... domain.be passed test Intersite
Starting test: FsmoCheck
......................... domain.be passed test FsmoCheck
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Technical\BARI
Starting test: Connectivity
......................... BARI passed test Connectivity
Doing primary tests
Testing server: Technical\BARI
Starting test: Replications
[Replications Check,BARI] A recent replication attempt failed:
From NEWYORK to BARI
Naming Context: CN=Schema,CN=Configuration
The replication generated an error (8456):
The source server is currently rejecting replication requests.
The failure occurred at 2013-04-30 09:57:01.
The last success occurred at 2013-02-10 12:55:45.
7563 failures have occurred since the last success.
Replication has been explicitly disabled through the server options.
[NEWYORK] DsBindWithSpnEx() failed with error 1722,
The RPC server is unavailable..
[Replications Check,BARI] A recent replication attempt failed:
From NEWYORK to BARI
Naming Context: CN=Configuration,DC=domain
The replication generated an error (8456):
The source server is currently rejecting replication requests.
The failure occurred at 2013-04-30 09:57:01.
The last success occurred at 2013-02-10 12:55:45.
14958 failures have occurred since the last success.
Replication has been explicitly disabled through the server options.
[Replications Check,BARI] A recent replication attempt failed:
From NEWYORK to BARI
Naming Context: DC=domain,DC=be
The replication generated an error (8456):
The source server is currently rejecting replication requests.
The failure occurred at 2013-04-30 09:57:01.
The last success occurred at 2013-02-10 12:55:45.
22879 failures have occurred since the last success.
Replication has been explicitly disabled through the server options.
REPLICATION-RECEIVED LATENCY WARNING
BARI: Current time is 2013-04-30 10:06:19.
CN=Schema,CN=Configuration
Last replication recieved from MILANO at 2013-01-24 12:18:44.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from PORTO at 2012-10-11 08:54:38.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from NEWYORK at 2013-02-10 12:55:45.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
CN=Configuration,DC=domain
Last replication recieved from PORTO at 2012-10-11 08:59:56.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from NEWYORK at 2013-02-10 12:55:45.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
DC=domain,DC=be
Last replication recieved from PORTO at 2012-10-11 09:00:26.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from NEWYORK at 2013-02-10 12:55:45.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
......................... BARI passed test Replications
Starting test: NCSecDesc
......................... BARI passed test NCSecDesc
Starting test: NetLogons
......................... BARI passed test NetLogons
Starting test: Advertising
Warning: BARI is not advertising as a time server.
......................... BARI failed test Advertising
Starting test: KnowsOfRoleHolders
......................... BARI passed test KnowsOfRoleHolders
Starting test: RidManager
......................... BARI passed test RidManager
Starting test: MachineAccount
......................... BARI passed test MachineAccount
Starting test: Services
......................... BARI passed test Services
Starting test: ObjectsReplicated
......................... BARI passed test ObjectsReplicated
Starting test: frssysvol
......................... BARI passed test frssysvol
Starting test: frsevent
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may cause
Group Policy problems.
......................... BARI failed test frsevent
Starting test: kccevent
......................... BARI passed test kccevent
Starting test: systemlog
......................... BARI passed test systemlog
Starting test: VerifyReferences
......................... BARI passed test VerifyReferences
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Running partition tests on : domain
Starting test: CrossRefValidation
......................... domain passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... domain passed test CheckSDRefDom
Running enterprise tests on : domain.be
Starting test: Intersite
......................... domain.be passed test Intersite
Starting test: FsmoCheck
......................... domain.be passed test FsmoCheck
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok. Thx!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
For more information you can check System event logs for Netlogon warnings and errors. Something like "Netlogon Event ID 5719"
ASKER
Seems ok.
C:\>nltest /server:bari /sc_query:domain.be
Flags: 30 HAS_IP HAS_TIMESERV
Trusted DC Name \\BERLIN
Trusted DC Connection Status Status = 0 0x0 NERR_Success
The command completed successfully
C:\>nltest /server:bari /sc_query:domain.be
Flags: 30 HAS_IP HAS_TIMESERV
Trusted DC Name \\BERLIN
Trusted DC Connection Status Status = 0 0x0 NERR_Success
The command completed successfully
ASKER
dcdiag of NewYork attached.
dcdiagNewYork.txt
dcdiagNewYork.txt
ASKER
Some more output of NLTEST:
on Bari:
C:\>nltest /whowill:domain test
[11:07:45] Mail message 0 sent successfully (\MAILSLOT\NET\GETDC539)
[11:07:50] Mail message 0 sent successfully (\MAILSLOT\NET\GETDC539)
[11:07:55] Mail message 0 sent successfully (\MAILSLOT\NET\GETDC539)
Didn't receive a response for mail message 0 (\MAILSLOT\NET\GETDC539)
The command completed successfully
on NewYork:
C:\>nltest /whowill:domain test
Cannot write netlogon mailslot: 53
Didn't receive a response for mail message 0 (\MAILSLOT\NET\GETDC347)
The command completed successfully
also on NewYork:
C:\>nltest /server:bari /sc_query:domain
I_NetLogonControl failed: Status = 5 0x5 ERROR_ACCESS_DENIED
C:\>nltest /server:berlin /sc_query:domain
I_NetLogonControl failed: Status = 5 0x5 ERROR_ACCESS_DENIED
C:\>nltest /server:newyork /sc_query:domain
I_NetLogonControl failed: Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN
C:\>nltest /server:newyork /sc_query:domain.be
Flags: 30 HAS_IP HAS_TIMESERV
Trusted DC Name \\berlin.domain.be
Trusted DC Connection Status Status = 0 0x0 NERR_Success
The command completed successfully
C:\>nltest /server:berlin /sc_query:domain.be
I_NetLogonControl failed: Status = 5 0x5 ERROR_ACCESS_DENIED
on Bari:
C:\>nltest /whowill:domain test
[11:07:45] Mail message 0 sent successfully (\MAILSLOT\NET\GETDC539)
[11:07:50] Mail message 0 sent successfully (\MAILSLOT\NET\GETDC539)
[11:07:55] Mail message 0 sent successfully (\MAILSLOT\NET\GETDC539)
Didn't receive a response for mail message 0 (\MAILSLOT\NET\GETDC539)
The command completed successfully
on NewYork:
C:\>nltest /whowill:domain test
Cannot write netlogon mailslot: 53
Didn't receive a response for mail message 0 (\MAILSLOT\NET\GETDC347)
The command completed successfully
also on NewYork:
C:\>nltest /server:bari /sc_query:domain
I_NetLogonControl failed: Status = 5 0x5 ERROR_ACCESS_DENIED
C:\>nltest /server:berlin /sc_query:domain
I_NetLogonControl failed: Status = 5 0x5 ERROR_ACCESS_DENIED
C:\>nltest /server:newyork /sc_query:domain
I_NetLogonControl failed: Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN
C:\>nltest /server:newyork /sc_query:domain.be
Flags: 30 HAS_IP HAS_TIMESERV
Trusted DC Name \\berlin.domain.be
Trusted DC Connection Status Status = 0 0x0 NERR_Success
The command completed successfully
C:\>nltest /server:berlin /sc_query:domain.be
I_NetLogonControl failed: Status = 5 0x5 ERROR_ACCESS_DENIED
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Wow. Great info guys. I love this website. It's such a big help.
UNC path access and the mail flow is working again. However I'm not sure that my replication errors are gone.
Dcdiag output for Bari and Newyork attached.
dcdiagBari.txt
dcdiagNewYork.txt
UNC path access and the mail flow is working again. However I'm not sure that my replication errors are gone.
Dcdiag output for Bari and Newyork attached.
dcdiagBari.txt
dcdiagNewYork.txt