Well like i stated above i have removed the server from the domain rebooted and re-added it to the domain without any problems...
As for the logs - nothing
Time setting - all current
Main Topics
Browse All Topicsi have installed a new windows server 2008 standard on my windows 2003 network... everything has been running fine for the last few weeks since the install... However today we had to reboot the server (not a domain controller, just a stand alone box) and we are getting this error message when we try to log into the domain...
The security database on the server does not have a computer account for this workstation
trust relationship
I can log into the computer as the local admin without any problems... And i even removed the server from the domain, rebooted and readded (which did not have any errors) and when i tried to log into the domain i get the same message "The security database on the server does not have a computer account for this workstation trust relationship"
thanks,
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Well i un-installed the Symantec BackupExec client and rebooted and tried to log in... got the same error message.
I logged into the server locally using the local admin user i created and had a look at the user account for the account we are using to log into this server (which the local account does work remember)... did not see anything on the local account, so i went to the domain account and found that something changed the level of access from ADMINISTRATOR to OTHER (set to Debug user) so i change that back to Administrator and logged off.... well now both my local account AND my domain account can no longer log into this server.
Well after almost 4 days working with Microsoft Support we were able to narrow down the problem. This Windows 2008 Standard Server is a new server for us that is replacing an old dying Windows 2000 Advanced Server being used as our Development Server. On this server we use a program called CVSNT v2.02.58d, CVSNT is a version control system for software developers.
Turns out that once this software is installed, it also installs a service that makes changes to the Active Directory. We have not tested this in Windows 2003, but it causes the above login problems to Windows Server 2008 Standard. This specific field in active directory that gets modified in AD is called servicePrincipalName which is found when you access
1. Open ADSI Edit
2. Expand your domain
3. Expand the DC=<yourdomain>,DC=com
4. Expand CN=Computers
5. Find the computer name in question and right click and select Properties
6. Under the Attribute Editor find SERVICEPRINCIOLENAME
7. Click Edit
8. You should at a MINIMUM the following (you might have many others as well, but these
two entries HAVE to be present to log into the domain)
a. HOST/<servername>
b. HOST/<servername.domainmam
9. Click OK and then OK again
10. Close ADSI Edit and reboot the server having the problems logging into the domain.
***** Below is the information from our Development Department on how to fix CVSNV *****
Cvsnt 2.0.58d
Cvs \CvsService can cause users to fail to logon on windows 2008 server
Cvsservice.exe loads ntdsapi.dll to do Active directory configuration. (in service.cpp) This needs to be updated as the code can overwrite settings in AD : Computers \ Properties \ servicePrincipleName.
Updated to code from 2.5.03.2382 - cut\\paste the same block of code and recompile cvsservice using MSVC 2003.
Replace cvsservice to resolve issue.
Just to add to this, if you have any other machine/account on the domain with the SPN set to HOST/servername or HOST/server.domainname it will cause this to happen, so if you renamed a machine in the past that had the same name you'll want to check there too to make sure it's not still in the SPN of that machine/account.
I had this very situation.
But the problem had arisen because we had renamed a server called XXX to YYY, and then joined another server with the XXX name to replace it. (So users would not have to learn a new name)
When i then looked at the old server YYY, it still had the XXX name in the SERVICEPRINCIOLENAME prop.
As soon as i delete that name from the old server entry, i could log in on the new server.
Best regards.
Business Accounts
Answer for Membership
by: jburgaardPosted on 2008-03-20 at 12:45:23ID: 21175098
Sounds like a deleted/corrupted computeraccount in AD.
I would create/reset the account for your 2008-server in ADUC-snapin and log on to 2008 server and add to domain.
Any clues in logs? Time settings?