Windows server Trust Relationship Failed

Microsoft Outlook 2003 (full product)
July 7, 2010 at 11:31:10
Specs: Windows XP
At my work we have a server, which only acts as a files server, when I set up computer accounts, everyone joins that domain as the same user, but they log onto their computers locally, and not through the domain. The issue we are having is that some computers are sharing their files/drives fine, while other computers are completely unavailable. Everyone shows up on the network, but half of the computers are not even accessible from the server. any ideas?

See More: Windows server Trust Relationship Failed

Report •

July 7, 2010 at 12:23:28
makes no sense your server is a DC unless its a SBS which requires it.

How many pcs total?

Report •

July 7, 2010 at 12:31:04
sorry i dont know what you mean, we have about 30 computers and i am new to setting up the server, but i remember setting up a domain controller, we are running windows server 2008. also i tried to exit the domain and then reenter it, but now i have 2 entries for the same computer, one for the correct domain and one for the old workgroup we had before the server

Report •

July 7, 2010 at 12:53:33
SBS = small business server.

You are doing peer to peer networking. A xp pro box can only have up to 10 network connections to it max. this means what is shared on it can only go to 10 others at a time. This also means 20 people won't be able to access the xp pro share.

xp home only supports 5 connections.

Proper configuration should have been a DC with all users files/shares on it and not on the local workstations at all. This allows you to backup everything important when you backup the server.

A pc can not be joined to the domain and a workgroup at the same time. This I suspect is the source of your problem along with the above concerning peer to peer limits.

You have quite a mess with the mixture you have. I would suggest reading a book on 2008 and networking then discuss with management what your best approach to correcting these issues would be. Might even be a good time to bring an experienced network person in to help straighten this out.

Report •

Related Solutions

July 7, 2010 at 13:02:48
thanks so much for your input! I wanted to set everything up through the server originally, but my boss thought that it would be too complicated to try and copy the local profiles to the domain profiles, and save all the individual user data and settings. is it possible? also, if i do set everything up through the server, will it eliminate the restriction on connections from computer to computer and everything will be shared from computer to computer and to the server?

Report •

July 7, 2010 at 13:53:38
You would no longer do sharing on the pcs. They add a lot of network overhead [slowing down the network] with their share advertising.

When you add the pc to the domain and then have a domain user logon [can't just use a single account anymore] you will get username.domainname under Documents and Settings. Just copy the local profile contents to this domain profile and the user will have everything they did before.

You need 30 cals for the server [1 per user]. FYI

I would suggest its a good time to get a 2008 book [nothing too complex - a dummies book [no offence meant] would be perfect given your situation. You don't want to setup anything too complex like roaming profiles for example.

Report •

July 8, 2010 at 12:31:29
thank you so much for all your help and clarification! We have a copy of McGraw Hill Windows Server 2008 A Beginners Guide, and it helped a bit. Maybe I should read it a bit more carefully! Now I do have a question about the roaming profiles you mentioned... our company does onsite work and our employees would need to be able to either connect to the server onsite, (however we have no internet connected to the server, so setting up a vpn and what not would be alot, also because I am not good with security), but what would it take to sync the local and domain profiles on a laptop?

Report •

July 8, 2010 at 15:02:31
The domain profile is on the local machine like I explained above

A roaming profile is used when you have people using different machines in a facility which is not what you are describing.

In the presented scenerio above there is no syncing of domain profiles nor is a roaming profile needed or recommended.

"our company does onsite work and our employees would need to be able to either connect to the server onsite"

What do you mean by this statement? Your firm is outsourcing tech support? Your techs go to another company's site?

If so I am amazed they let your tech connect to their network. You sure wouldn't on mine. I would provide you with a workstation and a controlled logon account. Anything less is a security issue and possible infection/hacker vector.

Report •

Ask Question