ROAMING PROFILE MESS!

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Random users on our network are recieving the following
error:

Windows cannot locate your roaming profile and is
attempting to log you on with your local profile. Changes
will not be propagated to the server.

Detail, logon failure the target

Windows cannot find the local profile and is logging you
on with a temporary profile. Changes you make to this
profile will be lost.

We have tried re-creating user accounts in Active
Directory and pointing them to new shared folders on our
network but this just keeps happening.
 
Connectivity good. Able to ping Domain Controller,
firewall and mail server successfully.
 
Could be a network issue - how's the connectivity?
Click to expand...
There are two problems. Firstly the computer cannot find a roaming
profile. That may be a connectivity issue. Maybe there is a DNS
problem. Secondly the users have not got a cached copy of the local
profile on the machine, so they get the second error.

Try nslookup on the Domain Controller, rather than ping.

Cheers,

Cliff
 
Thanks Cliff. I'll try nslookup.We have been having some
issues lately that I suspect are DNS related. Came in on
Jan 1 to find that MANY users on different subnets
couldn't log on and were getting a message that read:
"The system cannot log you on to this domain because the
system's computer account in it's primary domain is
missing or the password is incorrect". Now, the computer
accounts were listed in Active Directory so this threw me
off. I deleted the account from AD, took the offending
computer off of the domain and rejoined it. This seemed
to fix the problem, as users could now log on but the
computer accounts were not automatically created in AD.
(?) We started having this roaming profile error the next
day but not with all of the boxes and users that were
having a hard time logging on previously. We are all
completely stumped. Reckon they could be related?
I have also noticed that not all of our computers are
listed in the forward lookup zone for the domain...
Thanks for your help.
Eric
 
Thanks Cliff. I'll try nslookup.We have been having some
issues lately that I suspect are DNS related. Came in on
Jan 1 to find that MANY users on different subnets
couldn't log on and were getting a message that read:
"The system cannot log you on to this domain because the
system's computer account in it's primary domain is
missing or the password is incorrect". Now, the computer
accounts were listed in Active Directory so this threw me
off. I deleted the account from AD, took the offending
computer off of the domain and rejoined it. This seemed
to fix the problem, as users could now log on but the
computer accounts were not automatically created in AD.
(?) We started having this roaming profile error the next
day but not with all of the boxes and users that were
having a hard time logging on previously. We are all
completely stumped. Reckon they could be related?
I have also noticed that not all of our computers are
listed in the forward lookup zone for the domain...
Thanks for your help.
Click to expand...
Hi Eric, well, I can speculate, and it is possible that the two
problems are related. The message ""The system cannot log you on to
this domain because the system's computer account in it's primary
domain is missing or the password is incorrect" I've heard of but I
don't know what the solution might be. Maybe others who read this may
be able to help. But in general, many of the problems in AD turn out
to be DNS or connectivity related.

One gotcha, which you may well already be aware of, is that clients
should be configured with *only* internal DNS and not with the Service
or Bandwidth Provider's DNS.

If it has suddenly happened, I'd be inclined to ask "what changed?"
You've probably asked yourself that already. Otherwise, another thing
that can "just happen" is a disk may run out of space. That may give
all sorts of misleading errors. It might be worth a check anyway.

Did a new password GPO get implemented by any chance?

Computer accounts not automatically created in AD? That is strange. As
you say "?". Maybe they got created in a differnet container?

Cheers,

Cliff
 
I think that I have begun to find the cause of my problem
and am on my way to finding an answer. Long and complex,
haven't tried to write it down yet. Thanks to all.
Eric B
 
Back
Top