Nltest 1355 Error

(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語)  HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related nltest /dsgetdc error_no_such_domain threads Remove From My Forums Asked by: I_NetLogonControlfailed: Status =

I_netlogoncontrol Failed: Status = 5 0x5 Error_access_denied

1355 0x54b ERROR_NO_SUCH_DOMAIN on 2008 r2 PDC Windows Server > Directory Services Question 0 Sign

Nltest Sc_verify Error_no_such_domain

in to vote Hi I get the following error (I_NetLogonControlfailed: Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN) on our PDC when running the NLTEST Command. As mentioned

I_netlogoncontrol Failed Status 1722 0x6ba Rpc_s_server_unavailable

before all the forums I've read relating to this error, is that we have numerous domain controllers and this fault/error only pops up on the PDC. I have disabled all firewall settings within the OS and the AV End Point. However highly doubt that this is the problem, as these nltest /dclist error_no_such_domain are set by policies that apply to all DC. We have a trust with one of our Subsidiaries in South Africa, where our Exchange is hosted; they report that this is causing issues on their side. I would like to confirm this, is this error related to the DC hosting the PDC Role or is this somewhere else I need to start investigating. Other individuals stated in the forums that when the move the PDC role, the error moves with it. Wednesday, July 11, 2012 10:22 AM Reply | Quote All replies 1 Sign in to vote Hello, Make sure DC Is not multihomed. Please disable unused NIC's from DC. Also make sure DNS is setup properly and there is no name resolution problem. Verify SRV Records are registred in DNS properly - http://support.microsoft.com/kb/241515 If nothing helps post DCDiag /q results from your PDC. Regards, _Prashant_MCSA|MCITP SA|Micros

bad! 7 August 2012 by Adam Rush Scenario It's a pleasant day and all is well with the world. Colleagues are skipping around the office with smiles on faces…until…duh duh daaa! One by one, services start failing: Printers go offline: First, 0x54b group policy for Win7 users Then for all clients Can still print from server though File repadmin /replsum shares go offline Active Directory replication fails DNS console will not open Basically, your main Domain Controller (DC) has just taken a nltest /sc_query dump…and so have you! These are the steps I took to troubleshoot the issues and get everything back online. Solution Gather Information Run the following commands to gather useful information: ipconfig /all > c:\ipconfig.txt (from each https://social.technet.microsoft.com/Forums/windowsserver/en-US/9f72712e-5119-4610-9faf-b6520cbdf732/inetlogoncontrolfailed-status-1355-0x54b-errornosuchdomain-on-2008-r2-pdc?forum=winserverDS DC/DNS Server) dcdiag /v /c /d /e /s: > c:\dcdiag.txt dcdiag /test:dns /s: /DnsBasic > c:\dcdiag-dnsbasic.txt repadmin /showrepl dc* /verbose /all /intersite > c:\showrepl.txt (dc* is a placeholder for the starting name of the DCs if they all begin the same - if more then one DC exists) repadmin /replsum > c:\replsum.txt Pour through the txt files and note down the errors. Some of mine included: repadmin /showrepl Last error: 1256 (0x4e8): The remote http://www.virtuallyimpossible.co.uk/when-good-domain-controllers-go-bad/ system is not available. Last error: 5 (0x5): Access is denied. WARNING: KCC could not add this REPLICA LINK due to error. result 1722 (0x6ba): The RPC server is unavailable. repadmin /replsum (1722) The RPC server is unavailable. (5) Access is denied. dcdiag /test:dns /s: /DnsBasic The host could not be resolved to an IP address. Check the DNS server, DHCP,server name, etc. Got error while checking LDAP and RPC connectivity. Please check your firewall settings. Error: No LDAP connectivity. invalid DNS server: No host records (A or AAAA) were found for this DC. Warning: no DNS RPC connectivity (error or non Microsoft DNS server is running). Name resolution is not functional. dcdiag /v /c /d /e /s: EventID: 0x40000004 - The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server. EventID: 0xC00004B2 - The DFS Replication service failed to contact domain controller  to access configuration information. EventID: 0xC000138A - The DFS Replication service encountered an error communicating with partnerfor replication group Domain System Volume. The replication generated an error (-2146893022): The target principal name is incorrect. Error: Detected circular loop trying to locate the ISTG. repadmin /syncall -2146893022 (0x80090322): The target principal name is incorrect. SyncAll exited with fatal Win32 error: 8440 (0x20f8): The naming context specified for this replication operation is invalid. Some information seem

for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to https://www.experts-exchange.com/questions/28579078/nslookup-dsgetdc-Getting-DC-name-failed-Status-1355-0x54b-ERROR-NO-SUCH-DOMAIN.html Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > nslookup /dsgetdc Getting DC name failed: Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN Want to Advertise Here? Solved nslookup /dsgetdc Getting DC name failed: Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN Posted on 2014-12-11 MS Legacy OS Windows Networking 1 Verified Solution 6 Comments 1,712 Views Last Modified: i_netlogoncontrol failed 2014-12-16 I have a 2012 Exchange server S is in domain A trying to get to domain B for linked mailboxes. S is not a domain controller. The trust appears to be working fine as I can add users from domain B to groups in domain A on server S However, the nslookup is failing and so is the authentication when trying to link mailboxes, this is from S nslookup nltest 1355 error /dsgetdc:B results with Getting DC name failed: Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN From S I can ping B as well as get to any machine as long as I provide the credentials. I appreciate any help on this! Rob 0 Question by:bobbybhere Facebook Twitter LinkedIn Google Best Solution bybobbybhere We did use the fqdn as well as the domain name both returned the same thing. However, in testing other items, we ended up unchecking the register this connections address in DNS, saving it and then rechecked Go to Solution 6 Comments LVL 37 Overall: Level 37 MS Legacy OS 8 Windows Networking 5 Message Active 2 days ago Expert Comment by:Neilsr2014-12-11 Did you mean to type nltest /dsgetdc:B not nslookup /dsgetdc:B 0 Message Author Comment by:bobbybhere2014-12-11 Correct, nltest not nslookup 0 LVL 37 Overall: Level 37 MS Legacy OS 8 Windows Networking 5 Message Active 2 days ago Expert Comment by:Neilsr2014-12-11 And you are using the DNS name for B not the NetBios name ? Try with nltest /dsgetdc:B.Local or whatever the DNS name of B is 0 Message Accepted Solution by:bobbybhere2014-12-11 We did use the fqdn as well as the domain name both returned the same thing. However, in testing other items, we ended up