Solved

Domain Trust failing

Posted on 2010-09-17
10
2,039 Views
Last Modified: 2012-05-10
I am having an issue with a trust relationship that I have created.

Overview of my network

Domain A/B

2003 forest level
root domain (A)and child domain (B) fsmo roles within datacentre (firewalled)
Domain controller for domain B (Lets call it DC3) has been created at remote site (for Domain C) in DMZ
RPC ports have been tied down to allow traffic through the firewall





Domain C
2003 domain
Firewalled from domain B with exception of the domain controller (noted as placed at remote site)
Firewall is open between PDC of Domain C and domain controller (DC3) on all ports as RPC port settings have not been applied in domain C.

DNS zone transfers successfully created between both domains
WINS replication taking place between domains.

DC3 is able to communicate on standard AD ports (with RPC restricted) to Domain C subnets.

An incoming Trust has been established for domain C to trust domain B  but appears to have since broken.

From a DC in Domain C, the trust appears OK. I am told that the trust is valid and in place.

From Domain B, I am told that the trust cannot be validated as 'There are no logon servers available to service the logon request'. The strange things is that it attempts to validate the secure channel with a domain controller in domain C that it is firewalled from rather than the PDC with which it is able to communicate with.

Even stranger is that it seems to be OK one day and broken the next. Without anything changing everything may work tomorrow!


When I open AD users and computers from the DC in Domain B at the remote site and try connect to Domain C, I get an error;

The domain ** could not be found because: Access is denied


I have done some more investigations as it is back down again today. It was working OK yesterday and nothing has changed...

C:\Windows\system32>nltest /SC_query:ceg.company.org
I_NetLogonControl failed: Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN


C:\Windows\system32>nltest /dsgetdc:ceg.company.org
           DC: \\s-49-4901-002.ceg.company.org
      Address: \\10.49.31.12
     Dom Guid: 37a357fe-e492-43a2-8a1e-c0abcfcbf94e
     Dom Name: ceg.company.org
  Forest Name: ceg.company.org
 Dc Site Name: Koeln-HQ
        Flags: GC DS LDAP KDC TIMESERV WRITABLE DNS_DC DNS_DOMAIN DNS_FOREST
The command completed successfully

Any ideas?

It would appear to be something wrong with name resolution but everything looks OK
0
Comment
Question by:aideb
  • 5
  • 2
  • 2
  • +1
10 Comments
 
LVL 11

Accepted Solution

by:
Plantwiz earned 167 total points
Comment Utility
It does sound as though it is a name resolution problem.
Repopulate AD DNS with netdiag /fix on the directory server.  See if that improves things.


Review these:
http://technet.microsoft.com/en-us/library/aa998261(EXCHG.80).aspx
http://support.microsoft.com/kb/300684
http://support.microsoft.com/kb/824449
0
 
LVL 11

Expert Comment

by:Plantwiz
Comment Utility
Also, this may be of some help if you fall into a similar situation.

See here:
http://social.technet.microsoft.com/Forums/en-US/configmgrsetup/thread/75e6cfd9-dc72-4225-b88b-0390a15ad77b
0
 
LVL 3

Assisted Solution

by:saL1Las
saL1Las earned 166 total points
Comment Utility
I think I may have to pull out a pen and paper to draw this up properly.

Basically it looks like this. The domain you're logging into has more than one DC in it. Given that the DNS entry for "MYDOMAIN.LOCAL" will sort of round robin between different DCs, you will be unable to login if the DC point to is blocked by the firewall.

Solution is to either setup a host entry or edit DNS to point to only one server for said domain.
0
 
LVL 2

Author Comment

by:aideb
Comment Utility
Sorry, I omitted to add that domains A & B are running 2008 DCs so therefore NetDiag is no longer available.

I thought about the round robin issue and tried to force the issue with setting a host file on DC3 with an entry for the domain name pointing to the DC on domain C that it is able to speak to.

Whilst when I ping ceg.company.org it resolves to the right DC, the
nltest /dsgetdc:ceg.company.org

returns a DC without connectivity...
0
 
LVL 26

Expert Comment

by:Leon Fester
Comment Utility
I've seen instances where the trust behaves erratically. Some functionality is working one day then the next it isn't.

Even verifying the trust in AD Domains and Trusts Snap-in shows everything OK.

The easist way to fix a corrupt trust, even if verification works, is to break the trust and then set it up again. I spent a whole weekend chasing Event Log errors, and finally broke and re-established the trust and worked immediately.
0
Free Gift Card with Acronis Backup Purchase!

Backup any data in any location: local and remote systems, physical and virtual servers, private and public clouds, Macs and PCs, tablets and mobile devices, & more! For limited time only, buy any Acronis backup products and get a FREE Amazon/Best Buy gift card worth up to $200!

 
LVL 2

Author Comment

by:aideb
Comment Utility
I have previously removed and then re-established the trust. It went back in place and worked not problem for a few days then started playing up again! ARRRGH!!!!
0
 
LVL 26

Assisted Solution

by:Leon Fester
Leon Fester earned 167 total points
Comment Utility
Did you remove the trust from both sides of the domain, and did you confirm that replication had taken place after deleting the domain?

C:\Windows\system32>nltest /SC_query:ceg.company.org
I_NetLogonControl failed: Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN
I've seen the above happening when I run it on a bridgehead server, even when everything is working.

Did you try reseting the secure Channels to each server.
on DC1:
nltest /sc_reset:domain2
nltest /sc_reset:domain3

and then do the same for the other DC respectively.

Check if you've got any interesting errors/warnings recorded in your event viewer.
0
 
LVL 2

Author Comment

by:aideb
Comment Utility
On oneside of the trust reseting the channel gave

I_NetLogonControl failed: Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN

On the other side I got a succesful

0
 
LVL 2

Author Comment

by:aideb
Comment Utility
I have uploaded a problem steps recorder.

In AD domains and trusts today it says that the trust is valid and in place (yesterday it said it was failed!)
At the command line it says no such domain.

Any help would be invaluable.

I may have to try break and re-establish the trust again if I cannot get this working reliably soon :(
trust.zip
0
 
LVL 2

Author Closing Comment

by:aideb
Comment Utility
Issue was with firewall. Dc needs to have 389 opened to all DCs on the other domain
0

Featured Post

What Is Threat Intelligence?

Threat intelligence is often discussed, but rarely understood. Starting with a precise definition, along with clear business goals, is essential.

Join & Write a Comment

In this article, we will see the basic design consideration while designing a Multi-tenant web application in a simple manner. Though, many frameworks are available in the market to develop a multi - tenant application, but do they provide data, cod…
ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …

728 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now