marieconverse
asked on
NETLOGON Event ID 5721
We are replacing our NT 4 Domain controller with a Windows 2003 Domain controlller.
The new Domain controller has the same name and IP as the old NT 4 box had.
Under our NT 4 domain controller we had an application running on a seperate Windows 2003 server (that is not a DC).
Now that we are running the new Windows 2003 Domain controler, the application running on the
other 2003 server is giving us authentication errors.
The event log in the non domain controller server has the following item.
NETLOGIN 5721 The session setup to the Windows NT or 2000 Domain Controller xxxxx for the domain failed
because the Domain controller did not have an account needed to set up the session by this computer.
We have never had an account set up for this application on the old NT 4 domain controller. We are wondering if this is a trust issue.
Can anyone help?
The new Domain controller has the same name and IP as the old NT 4 box had.
Under our NT 4 domain controller we had an application running on a seperate Windows 2003 server (that is not a DC).
Now that we are running the new Windows 2003 Domain controler, the application running on the
other 2003 server is giving us authentication errors.
The event log in the non domain controller server has the following item.
NETLOGIN 5721 The session setup to the Windows NT or 2000 Domain Controller xxxxx for the domain failed
because the Domain controller did not have an account needed to set up the session by this computer.
We have never had an account set up for this application on the old NT 4 domain controller. We are wondering if this is a trust issue.
Can anyone help?
ASKER
Let me try to better explain.
We have turned off the old NT 4 box. We purchased a new Windows 2003 server. We used DC Promo to
now make that our Domain Controller.
At your suggested, we have thru my computer, properties, changed the domain name for login to ourdomain.com restarted the computer, changed the changed the domain name for login to ourdomain and
restarted the computer. This seems to have helped to get the system on the "new" domain. However,
SQL server services will now NOT start due to authentication.
We have turned off the old NT 4 box. We purchased a new Windows 2003 server. We used DC Promo to
now make that our Domain Controller.
At your suggested, we have thru my computer, properties, changed the domain name for login to ourdomain.com restarted the computer, changed the changed the domain name for login to ourdomain and
restarted the computer. This seems to have helped to get the system on the "new" domain. However,
SQL server services will now NOT start due to authentication.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
In doing so, you have eradicated the old domain, same name or not.
You'll have to rejoin any former domain machine to the new domain.