System could not log you on, domain isn't available

  • Thread starter Thread starter mika
  • Start date Start date
M

mika

Hi,

anyhave good tips where it can be wrong, before i could log my winxp laptop
with domain account using cached copy profile, but not anymore. When i try
it's give popup "The system could not log you on because the domain
is not available". I didn't make anychanges (or i can't remember).

Thanks
 
Domain user here recently ran into the same thing.
Happened when laptop battery died. That somehow screwed
up the cached domain password. Only work-around I could
come up with was to login via dialup long enough to
verify domain user. That restored credentials, so the
user could then work off-line again. Did your laptop
crash or did you lose a connection (vpn or dialup) the
last time you logged in to your network? Apparently the
user must successfully log in to the network, via lan
attach or dialup before the credetials are successfully
resaved. Have not been able to find any good info at
Microsoft site on this issue. If anybody else has any
info, please let me know.
Thanks.
 
Not crashed or similar. I use laptop everyday on office network, there works
fine, but when i come ex. home i can't logon.
 
I've had a similar problem using a shared tablet. Ideally I'd like to have everyone (10 people) use their regular network logons when they use the tablet, but for some reason, it caches only about 9. One of the 10 profiles fails to log on if disconnected from the network, giving the same error you have described. It's not always the same profile that has this problem. Are you still having this problem? Have you figured it out

Thanks.
 
geog_girl said:
I've had a similar problem using a shared tablet. Ideally I'd like
to have everyone (10 people) use their regular network logons when
they use the tablet, but for some reason, it caches only about 9.
One of the 10 profiles fails to log on if disconnected from the
network, giving the same error you have described. It's not always
the same profile that has this problem. Are you still having this
problem? Have you figured it out?

Change the number to 11.
*grin*
 
Back
Top