Karl Middleton
2005-07-04 08:53:28 UTC
Hello NG,
Over the weekend we upgraded to SBS2003 Premium a new customer site with a
Win2k box configured with a domain name belonging to someone else.
As part of the process we introduced new hardware, loaded Win2k3 from the
SBS disks, DCPromoed, moved the DC from the Win2k box to the new system with
Win2k3. All items like forestprep, etc, etc were performed along the way.
As stated, the catch was the the previous support organisation had set up
the Win2k domain using someone elses domain name! So we decided to do a
domain rename as per the white paper from Microsoft. We followed it to the
letter and successfully renamed the domain to correctdomainname.local as per
SBS best practice. The last step was to change the domain controller name
and FQDN. We followed the process detailed in the Active Directory help on
the Win2k3 system.
This all went fine and we then ran the SBS install to load Exchange, RWW,
Sharepoint etc etc etc.
All loaded OK. The server is running beautifully.
However, to cut a long story short, we now find that every few hours the
event log is showing a Netlogon event ID 5774. For some reason the server is
still trying to contact the old incorrect domain name. The error indicates
that the server is attempting to contact a DNS server external to our
customer which is obviously rejecting us thus generating the error. The
error doesn't seem to be harming the reliability or performance of the
system but bottom line is it shouldn't be doing this and I hate red entries
in my event log.
So we went on a trawl to find references to the old domain name in AD and
the registry. We found reference to it in the
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet\Services\NTDS\Parameters
in the Configuration NC key, the Machine DN Name key, and the Src Root
Domain Srv key.
Does anyone know how to fix this or where I can go to get the information?
TIA
Karl from Oz
Over the weekend we upgraded to SBS2003 Premium a new customer site with a
Win2k box configured with a domain name belonging to someone else.
As part of the process we introduced new hardware, loaded Win2k3 from the
SBS disks, DCPromoed, moved the DC from the Win2k box to the new system with
Win2k3. All items like forestprep, etc, etc were performed along the way.
As stated, the catch was the the previous support organisation had set up
the Win2k domain using someone elses domain name! So we decided to do a
domain rename as per the white paper from Microsoft. We followed it to the
letter and successfully renamed the domain to correctdomainname.local as per
SBS best practice. The last step was to change the domain controller name
and FQDN. We followed the process detailed in the Active Directory help on
the Win2k3 system.
This all went fine and we then ran the SBS install to load Exchange, RWW,
Sharepoint etc etc etc.
All loaded OK. The server is running beautifully.
However, to cut a long story short, we now find that every few hours the
event log is showing a Netlogon event ID 5774. For some reason the server is
still trying to contact the old incorrect domain name. The error indicates
that the server is attempting to contact a DNS server external to our
customer which is obviously rejecting us thus generating the error. The
error doesn't seem to be harming the reliability or performance of the
system but bottom line is it shouldn't be doing this and I hate red entries
in my event log.
So we went on a trawl to find references to the old domain name in AD and
the registry. We found reference to it in the
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet\Services\NTDS\Parameters
in the Configuration NC key, the Machine DN Name key, and the Src Root
Domain Srv key.
Does anyone know how to fix this or where I can go to get the information?
TIA
Karl from Oz