Server Name Conflict

Tyring to set up a trust between some domains and find I have a duplicated server name.

Basically, DOM1 and DOM2 have trusts already set up without any problem. I want DOM2 to allow file access to users on DOM3 so DOM2 needs to be trusting DOM3; there is no need to have any trusting between DOM1 and DOM3 - in fact, users on these two should not have access to the other's resources - it's just DOM2 that is shared by both. Unfortunately, the DOM3 PDC has the same name as a server already part of DOM1. Changing the server's name wouldn't normally be a big problem, except for the fact that the DOM3 PDC also hosts Exchange for DOM3 users.

Is there any simple way to resolve the name duplication without renaming?

 

Do you have a BDC in DOM3? If so, upgrade it to the PDC and establish the trust.

 

No, DOM3 has just the one server. The problem has had to be resolved by changing its name - that bit was easy - reinstalling Exchange was the fun bit.

I just find it amazing that this sort of problem can arise in Windows.

Thanks for responding, though.

 

Is this an NT network? If it were a Windows 2000 network theoretically you could have machines with the same name in different domains because the FQDN would be different for each server.

 

It's definitely an NT4 network. The network manager goes into a blue funk if any W2k PC is connected! But that's the subject of another thread.

Thanks, though.

 

Gotcha. Microsoft's networking concepts in NT were not much more than a peer-to-peer on steroids. They made huge advances with Windows 2000 and Active Directory but they are still things I'd like to see improved. I anticipate future versions of AD to surpass Novell's NDS.