Phantom domain problem

October 12, 2010 at 18:07:28
Specs: Win Server 2003 R2, Xenon X 2- 4 GB
I have inherited a domain problem that has me stumpted.
The domain originally had two domain controllers. I know...
There was an old W2K3 domain controller for let's say domain ABC.local. It is defunct and off-line.
There is another W2k3 domain controller for domain ABCdef.local.
When I join a new computer to the ABCdef.local domain, I get a normal "Welcome to the ABCdef.local domain"... and have to reboot.
When it comes back on-line it belongs to the old ABC.local domain even though, as I said, that DC isn't even on-line any longer.

Also, there is no group policy editor available on this DC. I get "Failed to open group policy object. You may not have appropriate rights" and "network path not found". I am the administrator and the path should be right there on the same drive and partition.

Is this a catalog problem or what? It's making me very confused.


See More: Phantom domain problem

Report •

October 13, 2010 at 03:14:45
Sounds like a mixup with netbios names. If you go into system properties > computer name, what is the full computer name there? It it's something like computer.abcdef.local then you're good, it might just be that the netbios name of the domain is ABC, hence the mixup. However if the full computername is you might have a problem, but check first.

Report •

October 13, 2010 at 08:29:03
ABC.local and ABCdef.local are NOT two domains. These are two different namespaces commonly referred to as forests in Active Directory.

Example of two different domains in a forest would be abc.test.local and with being the root domain.

How many users/pcs are we talking here? Exchange in the mix?

Your issue points to a problem with DNS and active directory. I would bet the dns and other event viewer logs have errors.

Since these are two different forests perhaps a trust was made between them that was not properly removed.

Report •

October 14, 2010 at 02:00:44
wanderer: What if there initially was a server with abc.local as domain, then it was replaced with a new server and a new domain instead of building on the existing one? I see that all the time, when people make changes incorrectly. Wouldn't that in fact create two separate environments?

Report •

Related Solutions

October 14, 2010 at 07:11:34
domain is a subset of forest. What you describe is a new forest not a new domain in the old forest. Being a new forest there would be no impact on the old forest.

Even if you name the new forest the same as the old one this fact remains.

given your example of replacing a forest just means there is a new forest. This would not effect the old one or the new one. They are different names.

Report •

Ask Question