Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies. Only from Platform Scholar.
Solved
NLTEST.EXE / BDC_Query Error
Posted on 2012-12-29
Hi,
I'm running a health inspection for our Active Directory (2003 Native).
I run this command - nltest.exe /bdc_query:DOMAIN_NAME
All but one servers were succesfull with the following notification:
SyncState : IN_SYNC
ConnectionState : Status = 0 0x0 NERR_Success
The one server who had an error notification gave me this error:
ConnectionState : Status = 1311 0x51f ERROR_NO_LOGON_SERVERS
And i have no knowledge on this error or how to fix it?
I'm running a health inspection for our Active Directory (2003 Native).
I run this command - nltest.exe /bdc_query:DOMAIN_NAME
All but one servers were succesfull with the following notification:
SyncState : IN_SYNC
ConnectionState : Status = 0 0x0 NERR_Success
The one server who had an error notification gave me this error:
ConnectionState : Status = 1311 0x51f ERROR_NO_LOGON_SERVERS
And i have no knowledge on this error or how to fix it?
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
3
4 Comments
Active today
Since you are running Active Directory 2003 in native mode there is not true BDC anymore.
This existed in NT 4.0 Domain Controllers. So this switch does not apply to your enviroment and I am not 100% sure it would apply to anyone anymore since we are now on Server 2012 (5 verisons since NT 4.0)
From http://technet.microsoft.com/en-us/library/cc731935(v=ws.10).aspx
This existed in NT 4.0 Domain Controllers. So this switch does not apply to your enviroment and I am not 100% sure it would apply to anyone anymore since we are now on Server 2012 (5 verisons since NT 4.0)
From http://technet.microsoft.com/en-us/library/cc731935(v=ws.10).aspx
/bdc_query: <DomainName>
Queries for a list of BDCs in DomainName, and then displays their state of synchronization and replication status. You can use this parameter only for Windows NT 4.0 domain controllers.
Active today
You will have a server (if in a single domain w/o any child domains) hold all 5 FSMO roles.
You can consider that your primary DC, but in regards to an actual BDC role that does not exist anymore as of 2000 AD. If all your DC's are in the same site located in the Site and Services MSC it is a round robin which server the client uses to authenticate to.
So Client A and Client B both are on the same subnet and 3 DC's are on this subnet.
Client A and B can both be authenticated to Server A.
Or Client A can auth to Server A and Client B to Server B, but next logon the can be switched.
You can consider that your primary DC, but in regards to an actual BDC role that does not exist anymore as of 2000 AD. If all your DC's are in the same site located in the Site and Services MSC it is a round robin which server the client uses to authenticate to.
So Client A and Client B both are on the same subnet and 3 DC's are on this subnet.
Client A and B can both be authenticated to Server A.
Or Client A can auth to Server A and Client B to Server B, but next logon the can be switched.
Active today
Have you looked at the event logs on the server with the issue.
See if the KB articale from MS could shed some light on your situation.
http://support.microsoft.com/kb/321044
Also you might want to use REPADMIN to see if the topology is in a consistant state.
http://technet.microsoft.com/en-us/library/cc770963(v=ws.10).aspx
Also DCDIAG /ReplSource:<SourceDomainC
http://technet.microsoft.com/en-us/library/cc731968(v=ws.10).aspx
See if the KB articale from MS could shed some light on your situation.
http://support.microsoft.com/kb/321044
Also you might want to use REPADMIN to see if the topology is in a consistant state.
http://technet.microsoft.com/en-us/library/cc770963(v=ws.10).aspx
Also DCDIAG /ReplSource:<SourceDomainC
http://technet.microsoft.com/en-us/library/cc731968(v=ws.10).aspx
Tests the connection between the domain controller on which you run the command and the source domain controller. (This parameter is used for the CheckSecurityError test.) SourceDomainController is the DNS name, NetBIOS name, or distinguished name of a real or potential server that will be the source domain controller for replication, as represented by a real or potential connection object.
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Here's a look at newsworthy articles and community happenings during the last month.
Let's recap what we learned from yesterday's Skyport Systems webinar.
- Ransomware
- Experts Exchange
- Skyport Systems
- Active Directory
- Security
- *privileged credentials
Attackers love to prey on accounts that have privileges.
Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Suggested Courses
Course of the Month9 days, 5 hours left to enroll
721 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.