Trust Issue with Win7 on Server2003 SBS w/SP2 Domain
on win server 2003 small business server domain, have user who's using win7 pro. approximately month ago put laptop on domain, yesterday afternoon, couldn't login pc. error @ login screen was:
“the trust relationship between workstation , primary domain failed.” (or similar statement)
at company, ran same problem. in case , above case, removing laptop domain , re-joining solved problem. but, what's causing trust issue? laptops have these facts in common:
- both laptops, manufactured different makers
- they have used both wireless , network cables @ various points in time connect companys' domains
- the users take laptops home , use them on home wireless networks
- both on sbs 2003 server networks/domains
- both organizations use symantec sep protection
- they both have same win7 os version
- i haven't had problem winxp pc's
after "solving" (or working around situation), i went user's add/remove programs , saw .net framework client 4 had been installed yesterday afternoon, through windowsupdate (since update has caused problems me on other pc's in other situations, and since laptop didn't need it, uninstalled , hid future updates).
in doing research, noticed mention of "serviceprincipalname" attribute. in looking @ properties of laptop in adsi, noted attribute multi-valued , had 4 values. 2 of values set host/[pcname] , other 2 started "restrictedkrbhost". other pc's on network winxp pc's. viewed properties of few of pc's. sampling had 2 values, neither of began "restricted".
a couple questions:
- in future, matter of going pc's adsi properties , removing "restricted..." values, rebooting pc-in-question , logging in?
- if can so, fix? (as opposed taking pc off domain)
- if can't above, there "easy" solution?
- what's causing problem? server upgrade solve problem?
- anything else should looking at?
thanks in advance . . .
rich
1. not far can tell - expected...
2. can try resetting secure channel (http://social.technet.microsoft.com/forums/en-ie/winserverds/thread/23760978-0d91-4496-a2da-ef95ae9d5989) - if doesn't work, need resort removing/readding computer domain
3. ditto
4. failing secure channel - more @ http://blogs.technet.com/b/askds/archive/2009/02/15/test2.aspx
5. reach out sbs forum - since there might sbs specific caveats take account
hth
marcin
Windows Server > Directory Services
Comments
Post a Comment