Jorge's Quest For Knowledge!

All You Need To Know About Identity And Security On-Premises And In The Cloud. It's Just Like An Addiction, The More You Have, The More You Want To Have!

(2005-12-17) Follow-Up On "It Works On Physical Hardware And It Does Not In VMware Virtualization Software"

Posted by Jorge on 2005-12-17


Remember me writing about not being able to promote a new DC into the forest as an additional DC for an existing domain or as a DC for a new child domain? (read more about it at: https://jorgequestforknowledge.wordpress.com/2005/11/14/it-works-on-physical-hardware-and-it-does-not-in-vmware-virtualization-software-2/)

Well, I found another one!

This time the environment is (again in VMware Workstation 5.x):

W2K3 Forest 1: ADCORP.LAN

1 DC = GC = DNS (pointing to itself)

DC name: ROOTDC01

Default administrator password: adcorp

W2K3 Forest 2: OTHERCORP.LAN

1 DC = GC = DNS (pointing to itself)

DC name: ROOTDC02

Default administrator password: othercorp

 

This time I tried to create an external trust and after that a forest trust…

After I entered the target domain name for the trust it says:

<QUOTE>

Cannot continue

the trust relationship cannot be created because the following error occured:

The Local Security Authority is unable to obtain an RPC connection to the domain controller <FQDN DC>. Please check that the name can be resolved and that the server is available

</QUOTE>

And again DNS name resolution (no NetBIOS) between both forest was setup with forwarding and it worked!

This time I immediately went for the network trace. This is what I found again:

————————————-

SMB (Server Message Block Protocol)
     SMB Header
          Server Component: SMB
          SMB Command: Session Setup AndX (0x73)
          NT Status: STATUS_LOGON_FAILURE (0xc000006d)     <————————-!!!!!!!!!!!!

————————————-

I changed the password of one of the default administrator to match the other, and again it worked and I was able to create a trust.

 

I’m still wondering what is causing this…

Cheers,
Jorge
———————————————————————————————
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always evaluate/test yourself before using/implementing this!
* DISCLAIMER:
https://jorgequestforknowledge.wordpress.com/disclaimer/
———————————————————————————————
############### Jorge’s Quest For Knowledge #############
#########
http://JorgeQuestForKnowledge.wordpress.com/ ########
———————————————————————————————

6 Responses to “(2005-12-17) Follow-Up On "It Works On Physical Hardware And It Does Not In VMware Virtualization Software"”

  1. I see the same behaviour. After discussions with Jorge and further tests, I have posted some additional information here.

    http://www.activedir.org/article.aspx?aid=75

  2. This don’t work for me.
    You’ll find a good explanation and solution there:
    http://blog.baeke.info/blog/_archives/2006/1/24/1720712.html
    thanks

  3. If you read the OTHER article (including comments) you should have seen more information and also the same solution by removing the shared folders feature.
    Jorge

  4. […] Follow-Up On "It Works On Physical Hardware And It Does Not In VMware Virtualization Software&q… […]

  5. […] Follow-Up On "It Works On Physical Hardware And It Does Not In VMware Virtualization Software&q… […]

  6. […] (2005-12-17) Follow-Up On "It Works On Physical Hardware And It Does Not In VMware Virtualizati… […]

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: