onepiolin
asked on
Server is dropping authentication
I have one of seven servers that is part of a Windows AD network that started giving us problems.
For some reason, some users (about 5-7 out of 25) are getting access denied messages when trying to connect to this server. This is a Win 2003 Std file server with Exchange 2003 loaded on it. It is not a DC and there are 4 DCs out there to authenticate.
There are no error messages anywhere, not on the server nor on the client.
To resolve the issue, sometimes I have to restart the computer, log in as admin, log off and log the user in. Today I had to remove one win7 pc out of the domain and rejoin. I also had to do the same on an xp and recreate the profile on the workstation.
It's very erratic on the fixes. the problem is that I can't reproduce the problem. It will happen suddenly and with no warning.
any ideas?
For some reason, some users (about 5-7 out of 25) are getting access denied messages when trying to connect to this server. This is a Win 2003 Std file server with Exchange 2003 loaded on it. It is not a DC and there are 4 DCs out there to authenticate.
There are no error messages anywhere, not on the server nor on the client.
To resolve the issue, sometimes I have to restart the computer, log in as admin, log off and log the user in. Today I had to remove one win7 pc out of the domain and rejoin. I also had to do the same on an xp and recreate the profile on the workstation.
It's very erratic on the fixes. the problem is that I can't reproduce the problem. It will happen suddenly and with no warning.
any ideas?
Nenadic
Can you post the text of the message? Is this the "domain trust relationship failure"? If so, it's a known issue with no known solution, other than to keep re-adding the computer to the domain. MS is apparently working on a fix, since the previous one they offered didn't solve the problem.
ASKER
ok.. found out something interesting.
on an xp computer with this issue, if do a \\computername it will say "logon failure: the target account name is incorrect".
if I do \\(ip address) it works fine.
I checked the DNS server and everything looks fine. I even deleted the A record and recreated it with no positive result.
I ended finally removing the client from the AD, deleting the client, renaming the user profile, rejoining the domain, adding the user and copying docs and desktop back to the new profile. That's the only thing that made it work.
on an xp computer with this issue, if do a \\computername it will say "logon failure: the target account name is incorrect".
if I do \\(ip address) it works fine.
I checked the DNS server and everything looks fine. I even deleted the A record and recreated it with no positive result.
I ended finally removing the client from the AD, deleting the client, renaming the user profile, rejoining the domain, adding the user and copying docs and desktop back to the new profile. That's the only thing that made it work.
A few items to check (mostly for sanity, not necessarily a cause):
- DNS: AD-integrated? Reverse lookup zone?
- DHCP: Are the DNS servers issued to each scope correct for the network?
- Any restrictive firewall policies at client level?
- Any firewalls in the environment that would be dropping RPC traffic?
- Any AD replication issues?
- DNS: AD-integrated? Reverse lookup zone?
- DHCP: Are the DNS servers issued to each scope correct for the network?
- Any restrictive firewall policies at client level?
- Any firewalls in the environment that would be dropping RPC traffic?
- Any AD replication issues?
ASKER
- DNS: AD-integrated? Yes - dynamic updates
Reverse lookup zone? Yes - only secure updates
- DHCP: Are the DNS servers issued to each scope correct for the network? I'm assuming yes.
- Any restrictive firewall policies at client level? none besides windows firewall... the xp machine's fw was off.
- Any firewalls in the environment that would be dropping RPC traffic? none... windows integrated fw
- Any AD replication issues? No NTDS warnings or errors only issue I saw was NTFRS, but we're not doing FRS as far as I know. Event 13508, NTFRS:
"The File Replication Service is having trouble enabling replication from HOME to DC for c:\winnt\sysvol\domain using the DNS name home.domain.com. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name home.domain.com from this computer.
[2] FRS is not running on home.domain.com.
[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. ""
Reverse lookup zone? Yes - only secure updates
- DHCP: Are the DNS servers issued to each scope correct for the network? I'm assuming yes.
- Any restrictive firewall policies at client level? none besides windows firewall... the xp machine's fw was off.
- Any firewalls in the environment that would be dropping RPC traffic? none... windows integrated fw
- Any AD replication issues? No NTDS warnings or errors only issue I saw was NTFRS, but we're not doing FRS as far as I know. Event 13508, NTFRS:
"The File Replication Service is having trouble enabling replication from HOME to DC for c:\winnt\sysvol\domain using the DNS name home.domain.com. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name home.domain.com from this computer.
[2] FRS is not running on home.domain.com.
[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. ""
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
dcdiag errors:
>>>
C:\>dcdiag /q
[Replications Check,DC] A recent replication attempt failed:
From REYNOLDS to DC
Naming Context: CN=Schema,CN=Configuration
The replication generated an error (5):
Access is denied.
The failure occurred at 2011-08-10 20:47.07.
The last success occurred at 2011-07-06 19:47.33.
840 failures have occurred since the last success.
[REYNOLDS] DsBind() failed with error -2146893022,
The target principal name is incorrect..
[Replications Check,DC] A recent replication attempt failed:
From HOME to DC
Naming Context: CN=Schema,CN=Configuration
The replication generated an error (5):
Access is denied.
The failure occurred at 2011-08-10 20:47.07.
The last success occurred at 2011-05-12 07:48.36.
2175 failures have occurred since the last success.
[Replications Check,DC] A recent replication attempt failed:
From BACKUP to DC
Naming Context: CN=Schema,CN=Configuration
The replication generated an error (5):
Access is denied.
The failure occurred at 2011-08-10 20:47.07.
The last success occurred at 2011-05-12 12:01.30.
2169 failures have occurred since the last success.
[Replications Check,DC] A recent replication attempt failed:
From REYNOLDS to DC
Naming Context: CN=Configuration,DC=domain
The replication generated an error (5):
Access is denied.
The failure occurred at 2011-08-10 20:47.07.
The last success occurred at 2011-07-06 20:22.43.
840 failures have occurred since the last success.
[Replications Check,DC] A recent replication attempt failed:
From BACKUP to DC
Naming Context: CN=Configuration,DC=domain
The replication generated an error (5):
Access is denied.
The failure occurred at 2011-08-10 20:57.10.
The last success occurred at 2011-05-12 12:15.37.
10267 failures have occurred since the last success.
[Replications Check,DC] A recent replication attempt failed:
From HOME to DC
Naming Context: CN=Configuration,DC=domain
The replication generated an error (5):
Access is denied.
The failure occurred at 2011-08-10 20:57.30.
The last success occurred at 2011-05-12 07:48.36.
10283 failures have occurred since the last success.
[Replications Check,DC] A recent replication attempt failed:
From REYNOLDS to DC
Naming Context: DC=domain,DC=com
The replication generated an error (5):
Access is denied.
The failure occurred at 2011-08-10 20:47.06.
The last success occurred at 2011-07-06 20:23.43.
840 failures have occurred since the last success.
[Replications Check,DC] A recent replication attempt failed:
From HOME to DC
Naming Context: DC=domain,DC=com
The replication generated an error (5):
Access is denied.
The failure occurred at 2011-08-10 21:07.10.
The last success occurred at 2011-05-12 07:48.36.
92944 failures have occurred since the last success.
[Replications Check,DC] A recent replication attempt failed:
From BACKUP to DC
Naming Context: DC=domain,DC=com
The replication generated an error (5):
Access is denied.
The failure occurred at 2011-08-10 21:08.30.
The last success occurred at 2011-05-12 12:43.04.
44010 failures have occurred since the last success.
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
<<<
repadmin /replsum is not a correct command. This DC is an old Windows 2000 machine.
>>>
C:\>dcdiag /q
[Replications Check,DC] A recent replication attempt failed:
From REYNOLDS to DC
Naming Context: CN=Schema,CN=Configuration
The replication generated an error (5):
Access is denied.
The failure occurred at 2011-08-10 20:47.07.
The last success occurred at 2011-07-06 19:47.33.
840 failures have occurred since the last success.
[REYNOLDS] DsBind() failed with error -2146893022,
The target principal name is incorrect..
[Replications Check,DC] A recent replication attempt failed:
From HOME to DC
Naming Context: CN=Schema,CN=Configuration
The replication generated an error (5):
Access is denied.
The failure occurred at 2011-08-10 20:47.07.
The last success occurred at 2011-05-12 07:48.36.
2175 failures have occurred since the last success.
[Replications Check,DC] A recent replication attempt failed:
From BACKUP to DC
Naming Context: CN=Schema,CN=Configuration
The replication generated an error (5):
Access is denied.
The failure occurred at 2011-08-10 20:47.07.
The last success occurred at 2011-05-12 12:01.30.
2169 failures have occurred since the last success.
[Replications Check,DC] A recent replication attempt failed:
From REYNOLDS to DC
Naming Context: CN=Configuration,DC=domain
The replication generated an error (5):
Access is denied.
The failure occurred at 2011-08-10 20:47.07.
The last success occurred at 2011-07-06 20:22.43.
840 failures have occurred since the last success.
[Replications Check,DC] A recent replication attempt failed:
From BACKUP to DC
Naming Context: CN=Configuration,DC=domain
The replication generated an error (5):
Access is denied.
The failure occurred at 2011-08-10 20:57.10.
The last success occurred at 2011-05-12 12:15.37.
10267 failures have occurred since the last success.
[Replications Check,DC] A recent replication attempt failed:
From HOME to DC
Naming Context: CN=Configuration,DC=domain
The replication generated an error (5):
Access is denied.
The failure occurred at 2011-08-10 20:57.30.
The last success occurred at 2011-05-12 07:48.36.
10283 failures have occurred since the last success.
[Replications Check,DC] A recent replication attempt failed:
From REYNOLDS to DC
Naming Context: DC=domain,DC=com
The replication generated an error (5):
Access is denied.
The failure occurred at 2011-08-10 20:47.06.
The last success occurred at 2011-07-06 20:23.43.
840 failures have occurred since the last success.
[Replications Check,DC] A recent replication attempt failed:
From HOME to DC
Naming Context: DC=domain,DC=com
The replication generated an error (5):
Access is denied.
The failure occurred at 2011-08-10 21:07.10.
The last success occurred at 2011-05-12 07:48.36.
92944 failures have occurred since the last success.
[Replications Check,DC] A recent replication attempt failed:
From BACKUP to DC
Naming Context: DC=domain,DC=com
The replication generated an error (5):
Access is denied.
The failure occurred at 2011-08-10 21:08.30.
The last success occurred at 2011-05-12 12:43.04.
44010 failures have occurred since the last success.
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
<<<
repadmin /replsum is not a correct command. This DC is an old Windows 2000 machine.
Have you perhaps raised the domain or forest functional levels on Win 2003? Are you able to remove the W2000 DC from circulation? Where are your FSMO (Operations Masters) roles? Is DC a GC?
ASKER
We added a Server 2008 as a dc a while back... so the dcs we have are 2008, 2003 and two 2000s.
I'll get back to you with the roles in a bit.
I'll get back to you with the roles in a bit.
What are domain and forest functional levels?
ASKER
domain functional level: 2000 native
can't find the forest one using ldp... I'm assuming 2000?
all four dc's hold the gc. I checked the exchange server (the one we're having people authenticating to) system manager for the list of directory access and it finds all the dcs... but it only has "reynolds" - 2000 server, as a config dc...
fsmo roles:
rid: home (2003 server)
pdc: home
infrastructiure: home
dom naming: home
schema: home
can't find the forest one using ldp... I'm assuming 2000?
all four dc's hold the gc. I checked the exchange server (the one we're having people authenticating to) system manager for the list of directory access and it finds all the dcs... but it only has "reynolds" - 2000 server, as a config dc...
fsmo roles:
rid: home (2003 server)
pdc: home
infrastructiure: home
dom naming: home
schema: home
ASKER
I don't know if this will help, but I just checked "home" for log errors and I found the following:
on the 10th at 3:30am... I'm assuming this is because the servers were restarting from windows update:
>>>
Directory Services: Event 2088, Src: NTDS Replication
"Active Directory could not use DNS to resolve the IP address of the source domain controller listed below. To maintain the consistency of Security groups, group policy, users and computers and their passwords, Active Directory successfully replicated using the NetBIOS or fully qualified computer name of the source domain controller.
Invalid DNS configuration may be affecting other essential operations on member computers, domain controllers or application servers in this Active Directory forest, including logon authentication or access to network resources. "
<<<
Also on the 8th at 11:56pm (no restart time)
Event 1308, Src NTDS KCC:
"The Knowledge Consistency Checker (KCC) has detected that successive attempts to replicate with the following domain controller has consistently failed.
Attempts:
2
Domain controller:
CN=NTDS Settings,CN=DC,CN=Servers,
Period of time (minutes):
124
The Connection object for this domain controller will be ignored, and a new temporary connection will be established to ensure that replication continues. Once replication with this domain controller resumes, the temporary connection will be removed.
Additional Data
Error value:
1722 The RPC server is unavailable."
<<<
And on the 10th at 3:30am, under File Replication, Event 13568, Src NTFRS
"The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.
Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Replica root path is : "c:\windows\sysvol\domain"
Replica root volume is : "\\.\C:"
A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reasons.
[1] Volume "\\.\C:" has been formatted.
[2] The NTFS USN journal on volume "\\.\C:" has been deleted.
[3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal.
[4] File Replication Service was not running on this computer for a long time.
[5] File Replication Service could not keep up with the rate of Disk IO activity on "\\.\C:".
Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state.
[1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication Service.
[2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.
WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again.
To change this registry parameter, run regedit.
Click on Start, Run and type regedit.
Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\
Double click on the value name
"Enable Journal Wrap Automatic Restore"
and update the value.
If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above."
<<<
on the 10th at 3:30am... I'm assuming this is because the servers were restarting from windows update:
>>>
Directory Services: Event 2088, Src: NTDS Replication
"Active Directory could not use DNS to resolve the IP address of the source domain controller listed below. To maintain the consistency of Security groups, group policy, users and computers and their passwords, Active Directory successfully replicated using the NetBIOS or fully qualified computer name of the source domain controller.
Invalid DNS configuration may be affecting other essential operations on member computers, domain controllers or application servers in this Active Directory forest, including logon authentication or access to network resources. "
<<<
Also on the 8th at 11:56pm (no restart time)
Event 1308, Src NTDS KCC:
"The Knowledge Consistency Checker (KCC) has detected that successive attempts to replicate with the following domain controller has consistently failed.
Attempts:
2
Domain controller:
CN=NTDS Settings,CN=DC,CN=Servers,
Period of time (minutes):
124
The Connection object for this domain controller will be ignored, and a new temporary connection will be established to ensure that replication continues. Once replication with this domain controller resumes, the temporary connection will be removed.
Additional Data
Error value:
1722 The RPC server is unavailable."
<<<
And on the 10th at 3:30am, under File Replication, Event 13568, Src NTFRS
"The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.
Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Replica root path is : "c:\windows\sysvol\domain"
Replica root volume is : "\\.\C:"
A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reasons.
[1] Volume "\\.\C:" has been formatted.
[2] The NTFS USN journal on volume "\\.\C:" has been deleted.
[3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal.
[4] File Replication Service was not running on this computer for a long time.
[5] File Replication Service could not keep up with the rate of Disk IO activity on "\\.\C:".
Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state.
[1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication Service.
[2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.
WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again.
To change this registry parameter, run regedit.
Click on Start, Run and type regedit.
Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\
Double click on the value name
"Enable Journal Wrap Automatic Restore"
and update the value.
If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above."
<<<
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
this dc is a bit more involved since it's our primary dns and dhcp server. so I'll have to move things around to do it... I eventually want to take it out, but I can't do this until next week.
I'm hoping to get this working without having to demote it.
I'm hoping to get this working without having to demote it.
The log you of posted of Home DC(Win2003) has replication issue.
Checked the DNS setting on the server.If DNS role is installed on the server the primary dns should point to itself that is IP address of the Server and alternate DNS entry should be of other DC.
If multiple nic are present on the server check the NIc binding the NIc which is acting as DNS and is online should be first in the order.Disable the NIc which is not required.Refer this link:http://theregime.wordpress.com/2008/03/04/how-to-setview-the-nic-bind-order-in-windows/
The log also shows that the FRS is in JRNL_WRAP_ERROR.To fix the same in the event itself the process to recover the same is given.Refer this article for details:http://www.eventid.net/display.asp?eventid=13568&eventno=1743&source=NtFrs&phase=1
Once th JRNL_WRAP_ERROR is fixed ran repadmin /replsum /AdeP from command prompt to force the replication.
Ran dcdiag /q and repadmin /replsum to check for any errors.
Ran dcdiag /q and repadmin /replsum to check for any errors.
Checked the DNS setting on the server.If DNS role is installed on the server the primary dns should point to itself that is IP address of the Server and alternate DNS entry should be of other DC.
If multiple nic are present on the server check the NIc binding the NIc which is acting as DNS and is online should be first in the order.Disable the NIc which is not required.Refer this link:http://theregime.wordpress.com/2008/03/04/how-to-setview-the-nic-bind-order-in-windows/
The log also shows that the FRS is in JRNL_WRAP_ERROR.To fix the same in the event itself the process to recover the same is given.Refer this article for details:http://www.eventid.net/display.asp?eventid=13568&eventno=1743&source=NtFrs&phase=1
Once th JRNL_WRAP_ERROR is fixed ran repadmin /replsum /AdeP from command prompt to force the replication.
Ran dcdiag /q and repadmin /replsum to check for any errors.
Ran dcdiag /q and repadmin /replsum to check for any errors.
ASKER
ok. it seems the issue was with the DC. it was not replicating with home or backup.
I demoted it last night and changed the dns to point to another server.
The issue now is that since the change, we cannot send attachments with droid phones through our exchange box. lol.
DCDIAG and REPADMIN shows no errors except a missing printer driver.
What's with the functional level? The win2000 machines will be gone soon. Is this something I should do?
I demoted it last night and changed the dns to point to another server.
The issue now is that since the change, we cannot send attachments with droid phones through our exchange box. lol.
DCDIAG and REPADMIN shows no errors except a missing printer driver.
What's with the functional level? The win2000 machines will be gone soon. Is this something I should do?
Here are a couple of articles to get an idea about functional levels:
http://technet.microsoft.com/en-us/library/cc787290(WS.10).asp
http://www.petri.co.il/understanding_function_levels_in_windows_2003_ad.htm
It may not be required, but it is beneficial.
http://technet.microsoft.com/en-us/library/cc787290(WS.10).asp
http://www.petri.co.il/understanding_function_levels_in_windows_2003_ad.htm
It may not be required, but it is beneficial.
ASKER
Thank you for your help. AD is not an area that is dealt with much on a day to day basis and your comments helped narrow down the issues.