Windows 2003 Server Different Domain
I have a server which was migrated using the AD migration tool from Microsoft. We migrated the server back in 2006. I recently logged into the server and noticed that the domain it belongs to is the old domain name and not the new one. Example Old domain name was ABCCompany and new one is BCDCompany. We made no changes to the server and we are recieving Error 5719 in the System Event viewer. This server is in our External DMZ.
I also see it in Active Directory and can open computer management remotely without a problem.
Need to know why this would have happen, very urgent at this is a production server that external clients use.
I also see it in Active Directory and can open computer management remotely without a problem.
Need to know why this would have happen, very urgent at this is a production server that external clients use.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Check the Windows Event Viewer for anything interesting, then put a sniffer on the wire to confirm that network traffic is behaving as you think it is.
Is the old domain still in service? Could be something as simple as 'somebody turned the PDC back on that had been in a storage closet to see what it was'.
Beyond these, if it's a member server you can always drop it to a workgroup and re-add it to the correct domain.
Is the old domain still in service? Could be something as simple as 'somebody turned the PDC back on that had been in a storage closet to see what it was'.
Beyond these, if it's a member server you can always drop it to a workgroup and re-add it to the correct domain.
ASKER
The old domain is still in service because there are servers we still access their. I think that is going to be our only options but since its a production server we would have to schedule time off hours. I have never seen something like this happen before on a 2K3 domain. We left the NT domain seperate because we not want to run in mix mode.
ASKER
What effects restarting the Net Logon service will have on a Windows 2003 server. My boxx wanted me to ask this questions. I am not sure of what the answer will be but he thinks it might have something to do with our problem.
ASKER
Does anyone know the effects of restarting the Net Logon Service?
If it's a domain controller (you haven't specified), it will be unable to service auth requests until the service restarts; restarting Netlogon will also re-register any SRV records that the server has registered. On member servers and workstations it's pretty much a non-event as operations go.
ASKER
This is a member server, so basically you are saying it really would do nothing to restart the service?
Unless you have applications that depend on it, and only you can answer that. If it's a concern, schedule the restart for an outage window and/or notify the affected userbase of the maintenance.
ASKER
Well this server is actually scheduled to be reboot tonight. So I can check that tonight.
ASKER
My worry is why it would revert back to the other domain. How would happen.