I did what you suggested, enabled the DNS service in the server that is the Domain Controller and configured to be the resolver it in the server i want to add to the domain in question. But, when i try it to the domain via the Sustem Properties utility i get the exact same error as before.
The Domain server has two ethernet interfaces and both are in use, i figured that incorrect resolvings to the secondary interface which has an out of range IP address to this would be a problem cause, so temporarily disabled it; and the problem stil persists. I have checked the DNS zone settings, everything looks allright, and the windows firewall is disabled,so it shouldnt be an issue. I dont know what else to check, ill keep poking to see if i get somewhere but any further help will be appreciated.
You may be running into trouble because of entries in the DNS resolver cache on the new machine. Also, on the dual-homed machine, make sure that there aren't any remaining entries for the disabled NIC in the routing table.
If not, maybe you could post the exact error you're now getting, or is it the same? Hope this helps! So I think it depends on the timeout value. In the repadmin output it seems that the server belongs to the UK-London site. Is this correct? Office Office Exchange Server.
Not an IT pro? Windows Server TechCenter. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Asked by:. Archived Forums. Directory Services. Sign in to vote. Thursday, January 12, AM. Hi, please check the active directory replication with repadmin. To configure the DNS information, follow these steps:. There should be a host record for the computer name.
This host record is an "A" record in Advanced view. On Windows Server and Windows Server member servers, Microsoft recommends that you configure the DNS client settings according to these specifications:.
Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. When you try to use network resources from the console of an affected domain controller, including Universal Naming Convention UNC resources or mapped network drives, you may receive the following error message:.
If you start any Active Directory administrative tools from the console of an affected domain controller, including Active Directory Sites and Services and Active Directory Users and Computers, you may receive one of the following error messages:.
Naming information cannot be located because: No authority could be contacted for authentication. Contact your system administrator to verify that your domain is properly configured and is currently online.
Naming information cannot be located because: Target account name is incorrect. Microsoft Outlook clients that are connected to Microsoft Exchange Server computers that are using affected domain controllers for authentication may be prompted for logon credentials, even though there is successful logon authentication from other domain controllers. DC list test. LDAP test. There are several resolutions for these symptoms. The following is a list of methods to try. The list is followed by steps to perform each method.
Try each method until the problem is resolved. Microsoft Knowledge Base articles that describe less common fixes for these symptoms are listed later.
0コメント