Question

Locked

Facing DNS & File Replications issues in DC but not sure what is the issue?

By inderdev ·
Hi,
I have an issue which I am not sure on how to solve? My users pick up their batch files from the \\server-name\netlogon from my domain controller which maps their network drives. Currently my users have difficulty in getting their network drives mapped whenever they are connected to this particular Domain controller. In my environment we have 4 domain controllers. The domain controller which I am currently having an issue is my PDC. I guess it may lie in the DNS but I cannot confirm. I have tried deleting this servers A record and reinserting it but does not resolve the issue. None of my domain controllers have this issue. I have even restarted the server 5 times but to no effect. I only have a single domain, single forest with no child domains and trusts as such. I have also checked in the DNS that there is no 2 servers with the same IP address or hostname. Please advise on how I can solve this issue. Thanks.

1) Whenever I try to insert this into any of my clients(\\server-name\netlogon), it does not work.
I get the following error:
Logon Failure: The target account name is incorrect

Whenever I insert \\IP-address\netlogon, it works.

2) If I were to do the following from my client:
\\server-name\netlogon
System error 5 has occurred.
Access is denied.

3) If I were to do the following from my client:

\\IP-address\netlogon
Domain Controller (PDC only)

Share name Type Used as Comment

--------------------------------------------------------------
app Disk
NETLOGON Disk Logon server share
SYSVOL Disk Logon server share
The command completed successfully.

I have found some errors with the DNS and File Replication of one of my Domain Controllers. This DC also contains the 5 FSMO rules.

This conversation is currently closed to new comments.

6 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Collapse -

This is just some added info to what I have collected. Hope it helps.

by inderdev In reply to Facing DNS & File Replica ...

I did some ipconfig /all, dcdiag and ping -a commands. Please let me know if you would want me to insert any other commands in. Thanks.


DC Without issues (ipconfig /all):

C:\Documents and Settings\dev>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : BL2
Primary Dns Suffix . . . . . . . : mount-alvernia.org
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mount-alvernia.org

Ethernet adapter Local Area Connection 5:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP Network Team #1
Physical Address. . . . . . . . . : 18-A9-05-72-43-60
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 128.1.1.162
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 128.1.15.1
DNS Servers . . . . . . . . . . . : 128.1.1.162
128.1.1.161
128.1.1.20
Primary WINS Server . . . . . . . : 202.79.64.21
Secondary WINS Server . . . . . . : 202.79.64.26


DC with Issue: (ipconfig /all)

C:\Documents and Settings\admin>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : DC1
Primary Dns Suffix . . . . . . . : mount-alvernia.org
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mount-alvernia.org

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC7781 Gigabit Server Adapter #2
Physical Address. . . . . . . . . : 00-11-85-5C-BA-65
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 128.1.1.20
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 128.1.1.42
DNS Servers . . . . . . . . . . . : 128.1.1.20
128.1.1.161
128.1.1.13
128.1.1.162
Primary WINS Server . . . . . . . : 202.79.64.21
Secondary WINS Server . . . . . . : 202.79.64.26

Client: (ipconfig /all)

C:\Documents and Settings\dev>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : MIS_SS_08_39
Primary Dns Suffix . . . . . . . : mount-alvernia.org
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mount-alvernia.org

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82566DC-2 Gigabit Network C
onnection
Physical Address. . . . . . . . . : 00-1C-C0-23-30-1F
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.10.15.89
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.10.15.1
DNS Servers . . . . . . . . . . . : 128.1.1.161
128.1.1.20


Nslookup via client

C:\Documents and Settings\dev>nslookup dc1
*** Can't find server name for address 128.1.1.161: Non-existent domain
*** Can't find server name for address 128.1.1.20: Non-existent domain
*** Default servers are not available
Server: UnKnown
Address: 128.1.1.161

Name: dc1.mount-alvernia.org
Address: 128.1.1.20


Nslookup via Troubled DC

C:\Documents and Settings\admin>nslookup dc1
*** Can't find server name for address 128.1.1.20: Non-existent domain
Server: UnKnown
Address: 128.1.1.20

Name: dc1.mount-alvernia.org
Address: 128.1.1.20

Hi all just something extra that I tried and found this:

DC with no issues:(dcdiag /q /f:c:\dcdiag.txt)


Results:

[Replications Check,BL2] A recent replication attempt failed:
From DC1 to BL2
Naming Context: DC=ForestDnsZones,DC=mount-alvernia,DC=org
The replication generated an error (1256):
The remote system is not available. For information about network troubleshooting, see Windows Help.
The failure occurred at 2011-03-11 11:49:22.
The last success occurred at 2011-03-02 16:54:11.
219 failures have occurred since the last success.
[DC1] DsBindWithSpnEx() failed with error -2146893022,
The target principal name is incorrect..
[Replications Check,BL2] A recent replication attempt failed:
From DC1 to BL2
Naming Context: DC=DomainDnsZones,DC=mount-alvernia,DC=org
The replication generated an error (-2146893022):
The target principal name is incorrect.
The failure occurred at 2011-03-11 12:11:18.
The last success occurred at 2011-03-02 20:12:51.
275 failures have occurred since the last success.
[Replications Check,BL2] A recent replication attempt failed:
From DC1 to BL2
Naming Context: CN=Schema,CN=Configuration,DC=mount-alvernia,DC=org
The replication generated an error (-2146893022):
The target principal name is incorrect.
The failure occurred at 2011-03-11 11:49:22.
The last success occurred at 2011-03-02 16:54:11.
215 failures have occurred since the last success.
[Replications Check,BL2] A recent replication attempt failed:
From DC1 to BL2
Naming Context: CN=Configuration,DC=mount-alvernia,DC=org
The replication generated an error (-2146893022):
The target principal name is incorrect.
The failure occurred at 2011-03-11 11:49:22.
The last success occurred at 2011-03-02 16:54:11.
215 failures have occurred since the last success.
[Replications Check,BL2] A recent replication attempt failed:
From DC1 to BL2
Naming Context: DC=mount-alvernia,DC=org
The replication generated an error (-2146893022):
The target principal name is incorrect.
The failure occurred at 2011-03-11 12:07:43.
The last success occurred at 2011-03-02 17:47:33.
288 failures have occurred since the last success.
REPLICATION-RECEIVED LATENCY WARNING
BL2: Current time is 2011-03-11 12:28:06.
DC=ForestDnsZones,DC=mount-alvernia,DC=org
Last replication recieved from DC1 at 2011-03-02 16:57:37.
DC=DomainDnsZones,DC=mount-alvernia,DC=org
Last replication recieved from DC1 at 2011-03-02 20:12:19.
CN=Schema,CN=Configuration,DC=mount-alvernia,DC=org
Last replication recieved from DC1 at 2011-03-02 16:57:37.
CN=Configuration,DC=mount-alvernia,DC=org
Last replication recieved from DC1 at 2011-03-02 16:57:37.
DC=mount-alvernia,DC=org
Last replication recieved from DC1 at 2011-03-02 17:47:01.
Warning: DC1 is the Schema Owner, but is not responding to DS RPC Bind.
[DC1] LDAP bind failed with error 8341,
A directory service error has occurred..
Warning: DC1 is the Schema Owner, but is not responding to LDAP Bind.
Warning: DC1 is the Domain Owner, but is not responding to DS RPC Bind.
Warning: DC1 is the Domain Owner, but is not responding to LDAP Bind.
Warning: DC1 is the PDC Owner, but is not responding to DS RPC Bind.
Warning: DC1 is the PDC Owner, but is not responding to LDAP Bind.
Warning: DC1 is the Rid Owner, but is not responding to DS RPC Bind.
Warning: DC1 is the Rid Owner, but is not responding to LDAP Bind.
Warning: DC1 is the Infrastructure Update Owner, but is not responding to DS RPC Bind.
Warning: DC1 is the Infrastructure Update Owner, but is not responding to LDAP Bind.
......................... BL2 failed test KnowsOfRoleHolders
......................... BL2 failed test RidManager
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.
......................... BL2 failed test frsevent
An Error Event occured. EventI 0x40000004
Time Generated: 03/11/2011 12:05:11
Event String: The kerberos client received a
An Error Event occured. EventI 0x40000004
Time Generated: 03/11/2011 12:05:47
Event String: The kerberos client received a
An Error Event occured. EventI 0x40000004
Time Generated: 03/11/2011 12:28:06
Event String: The kerberos client received a
An Error Event occured. EventI 0x40000004
Time Generated: 03/11/2011 12:28:06
Event String: The kerberos client received a
......................... BL2 failed test systemlog


DC with issues:(dcdiag /q /f:c:\dcdiag.txt)


Results:

REPLICATION LATENCY WARNING
ERROR: Expected notification link is missing.
Source BL1
Replication of new changes along this path will be delayed.
This problem should self-correct on the next periodic sync.
REPLICATION LATENCY WARNING
ERROR: Expected notification link is missing.
Source BL2
Replication of new changes along this path will be delayed.
This problem should self-correct on the next periodic sync.
REPLICATION LATENCY WARNING
ERROR: Expected notification link is missing.
Source BL1
Replication of new changes along this path will be delayed.
This problem should self-correct on the next periodic sync.
REPLICATION LATENCY WARNING
ERROR: Expected notification link is missing.
Source BL2
Replication of new changes along this path will be delayed.
This problem should self-correct on the next periodic sync.
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.
......................... DC1 failed test frsevent
An Error Event occured. EventI 0xC0001B72
Time Generated: 03/11/2011 12:11:53
(Event String could not be retrieved)
An Error Event occured. EventI 0x40000004
Time Generated: 03/11/2011 12:26:48
Event String: The kerberos client received a

An Error Event occured. EventI 0x0000168F
Time Generated: 03/11/2011 12:26:48
Event String: The dynamic deletion of the DNS record

An Error Event occured. EventI 0x0000168F
Time Generated: 03/11/2011 12:26:48
Event String: The dynamic deletion of the DNS record

An Error Event occured. EventI 0x0000168F
Time Generated: 03/11/2011 12:26:48
Event String: The dynamic deletion of the DNS record

An Error Event occured. EventI 0x0000168F
Time Generated: 03/11/2011 12:26:48
Event String: The dynamic deletion of the DNS record

An Error Event occured. EventI 0x0000168F
Time Generated: 03/11/2011 12:26:48
Event String: The dynamic deletion of the DNS record

An Error Event occured. EventI 0x0000168F
Time Generated: 03/11/2011 12:26:48
Event String: The dynamic deletion of the DNS record

An Error Event occured. EventI 0x0000168F
Time Generated: 03/11/2011 12:26:48
Event String: The dynamic deletion of the DNS record

......................... DC1 failed test systemlog


Client (ping -a dc1)


C:\Documents and Settings\dev>ping -a dc1

Pinging dc1.mount-alvernia.org [128.1.1.20] with 32 bytes of data:

Reply from 128.1.1.20: bytes=32 time<1ms TTL=127
Reply from 128.1.1.20: bytes=32 time<1ms TTL=127
Reply from 128.1.1.20: bytes=32 time<1ms TTL=127
Reply from 128.1.1.20: bytes=32 time<1ms TTL=127

Ping statistics for 128.1.1.20:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Collapse -

Still try on DNS as you can mount using IP address

by ossyemeh In reply to Facing DNS & File Replica ...

Make sure the server is pointing to a DNS server that is authoritative to your domain. On the DNS server, open DNS management console from administrative tools, check through the forward lookup zone and your zone to see if the name of the server is listed. If it is not confirm that automatic update is enabled on the DNS server and try refreshing the forward lookup zone.
You can confirm if it is a DNS problem by editing the host file in drivers folder found in system32 folder of one of your client. add the IP address of the server and the name and try mounting again

Collapse -

Reponse To Answer

by inderdev In reply to Still try on DNS as you c ...

Hi the current DNS server is the one holding the 5 FSMO roles.I have already refreshed the DNS and found that the server is also listed. I have found out that whenever my logonserver (under command set) is DC1(the dc with the issue), I am able to \\DC1\netlogon but whenever I am not under that logonserver I get Logon Failure: Target Account name is incorrect.


By the way I checked my FRS events and found the following issue:
vent id:13508
Source: NtFrs
Type: Warning
Computer:DC1
The File Replication Service is having trouble enabling replication from DC2 to DC1 for c:\windows\sysvol\domain using the DNS name DC2.mount-alvernia.org. FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name DC2.mount-alvernia.org from this computer.
[2] FRS is not running on DC2.mount-alvernia.org.
[3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.

This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.

For more information, see Help and Support Center at


I tried also going to Active Directory Sites & Services to force replication to the server but I am not able to replicate. I get the following error whenever I

the following error occurred during the attempt to synchronize naming context mount-alvernia.org from Domain Controller DC1 to target controller BL2:

Target Principal name is incorrect.

The operation will not continue

Collapse -

How long is your log?

by seanferd In reply to Facing DNS & File Replica ...

If long enough, you can look back 275 failures to the last success and see what was different.

Note also that <code>[2] FRS is not running on DC2.mount-alvernia.org.</code> If the service isn't running, replication will not occur.

Collapse -

Issue Resolved after backup was done

by inderdev In reply to Facing DNS & File Replica ...

Issue Solved. I brought down one of my DC's(BL1) for backup before wanting to do a netdom resetpw command. As I taught this would be one of the last solutions. To my surprise, after half an hour of backing up and booting up, the Domain Controller with the FSMO and the DC(BL1 server) started replicating back to normal. The DC with the FSMO had an event 13509 which points to it being able to replicate to other Domain Controllers. Quite confusing. Well I hope you can help me to understand what exactly does netdom resetpw do exactly? And If I had done it would it have caused any issues to my domain controller?

Back to Networks Forum
6 total posts (Page 1 of 1)  

Related Discussions

Related Forums