COURSE of the MONTH

Issue with Child Domain user accessing resources in the parent domain

We have recently run into an issue with one of our child domains in our forest. Up until last week there was not an issue. Now when users from the child domain try to access any of our resources in the parent domain, it requests a login.

When they put in the following,

domain\username
password

it will not allow them in. However when they put

username@childdomainFQDN
password

It allows them to login.

This would not be as big of an issue except that we have now add window authentication to SQL for one of our applications.

When they try to login on machine that are connected to the Parent domain if they use pre-2000 login, it will not let them login. If they use their normal login, then they get a "password or user name incorrect" error.

We think this is an issue with something with NetBIOS. When we are in the child domain and try to connect to the ADUC of the parent, we can't type in "CORP", we have to search by Domain.net. We can however connect to any of the other child domains by NetBIOS name with no issue.

Replication looks like it is working properly from all domains, but I am not sure where else to look. This is only effecting one child domain. We have several others that are working correctly.

It looks like we have suffered from a USN rollback on one of our Parent level DC's.

I have pulled the bad DC out of the replication trees for all the child domains. This has corrected the issue of passing the pre-2000 name for fileshares on the child domain DC's but we are still having issues on computers that are joined to the child domain.

I cannot login on any computers outside the child domain with credentials from that child domain. We have several child domains, and all others are working. We are combing through the logs for this domain.

0

PLHGroupAuthor Commented: 2015-01-02

Yeah. We are going through that process now. To get our users from that domain working, we are changing the connections for the application they use from the server name to the server IP. That is allowing them to pass their credentials properly to SQL.

0

PLHGroupAuthor Commented: 2015-01-02

Amit thank you for your help. That KB was what we were looking at. One of my guys followed that down the rabbit hole and found some commands from Repadmin that would allow you restart the replication.

What we ended up doing was the following.

1) Removed the DC from the replication trees of every DC in our forest. We ensured no one was making any changes in the parent domain so that we wouldn't have to have any replications being missed.
2) We waited a couple of hours making sure all other DC's in the forest were replicating properly (child domains only obviously)
3) We ran Repadmin /options Disable_inbound_repl and Repadmin /options disable_inbound_repl
4) We waiting 15 minutes and the replication restarted with no issues.

Great, thanks for sharing the solution. I also suggest you to put some monitoring for your AD environment...bare minimum you can run repadmin /replsum everyday and email it. You can also implement monitoring script or use scom