Re: Random "computer account was not found" broken profiles Server
- From: "Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx>
- Date: Mon, 19 Jun 2006 23:58:14 +0100
sounds like network connectivity or configuration problem
- Do you have FW on your Windows Client Machines?
Deploying Windows Firewall Settings for Microsoft Windows XP with Service
Pack 2
http://www.microsoft.com/downloads/details.aspx?familyid=4454e0e1-61fa-447a-bdcd-499f73a637d1&displaylang=en
- Also follow the steps provided in this link:
http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows%20Operating%20System&ProdVer=5.2&EvtID=1053&EvtSrc=Userenv&LCID=1033
- Make sure that your clients use only their local (LAN) DNS Server.
--
I hope that the information above helps you
Good Luck
Jorge Silva
MCSA
Systems Administrator
"GobLox" <GobLox@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:832F9138-8141-4057-B226-0408E1060FE2@xxxxxxxxxxxxxxxx
Some important errors might be:
Userenv None 1053 SYSTEM CLIENT-110 (Windows cannot determine the user or
computer name)
Netlogon None 3210 N/A CLIENT-110
The second one appears to show up for the first time when the machine
cannot
connect to the domain again.
"Jorge Silva" wrote:
Hi
What errors do you see in event viewer on client and server computers
--
I hope that the information above helps you
Good Luck
Jorge Silva
MCSA
Systems Administrator
"GobLox" <GobLox@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:16151353-B94F-4CB2-AEC5-CBAAB93DC596@xxxxxxxxxxxxxxxx
"cannot connect to the domain, either because the domain controller is
down
or otherwise unavailable, or because your computer account was not
found"
We are running a 20-seat Server2003 license and a mixed
XPPRO/XPMediaCenter(Home) environment. I believe we do not have more
than
20
clients in the domain at anyone time but surely even if we did this
would
not
corrupt a profile/hive, right? Seemingly randomly we are having clients
shutdown at night and then unable to login to the domain the next
morning
with the account that worked the night before. The error above is
given.
Other Accounts still work fine. Obviously this is not acceptable - it's
making me look like an idiot. It's happening often enough that it
really
is
becoming an issue.
I've seen quite a few posts on this but never any specific answers on
what
the issue is? Yes, rejoining the domain "fixes" the issue in that we
can
once
again login to the domain with the problem account. I'm gathering that
there
may be no good fix once the hive is disconnected from the domain
although
someone had posted this:
"Run regedit.exe and navigate here:
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList:
Now locate the value ProfileImagePath that points to your current
profile folder, then change it back to the old profile folder and
reboot the machine."
I can't imagine that this will work - I have yet to try it. More
importantly
- what is the problem here? Is this the price of doing business on a
server2003 domain? This has to stop.
.
- Follow-Ups:
- References:
- Prev by Date: Re: Lost admin access to ADAM
- Next by Date: Re: Rejoining domains to new active directory .
- Previous by thread: Re: Random "computer account was not found" broken profiles Server
- Next by thread: Re: Random "computer account was not found" broken profiles Server
- Index(es):
Relevant Pages
|
