Domain Controller SBS 2K8

Hi All,

This weekend we have installed a new domain controller server with SBS 2K8 Std. And Installed Windows 7 Pro PC's

Today we are getting the following

The security database on the server does not have a computer account for this workstation trust relationship.

Now I am getting the same error on my DC and cannot log on to it.

The Security database on the server does not have a computer account for this workstation trust relationship.
LVL 3
WaynepreAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

NJComputerNetworksCommented:
"This weekend we have installed a new domain controller server with SBS 2K8 Std"  So, are you saying that previosly, you had an SBS 2008 domain... It was working and users could log in.   Then later, you add a new domain controller into the SBS 2008 domain?  Since you have done this, users can no longer login to the domain...

is this true...


Normal things to check are:

1) make sure that your SBS is only using 1 nic... (nic teaming is not supported in 2008 SBS)
2) make sure that the SBS TCP/IP properties is pointing DNS to 127.0.0.1 or to the IP address of the SBS server.  Also, make sure that dns is not pointing any where else, like ISP dns servers.  
3) Make sure that all client machines are pointing to the SBS server for DNS resolution and nowhere else (like ISP dns servers)

4) if you have added a DC to the existing SBS domain, make sure that it points to the SBS server for DNS resolution and not to itself (at least not until DNS replication has occured and only after the DNs service has been added to this DC... )
0
WaynepreAuthor Commented:

Hi thanks for the reply.
Please ignore this question as it has now been resolved.
What had happened was we had this error one WS so one of m engineers had modified the WS using ADSI and connecting to AD and changed the serverprincipal name to the same name as the server. Removed this and the server is now working
Thanks anyways
Wayne
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.