Re: Domain Login failure
- From: "Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 5 May 2008 10:32:54 -0400
Geoff332 <Geoff332@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
You might have a point. I do need the domain login occasionally, but
I could reset the password (or otherwise fix the problem) next time I
login.
Well - if you're using VPN or Terminal Services, you don't need any local
caching of that info at all. It isn't relevant. You provide the domain
credentials when you *need* them.
If I take this path, would it be simply a matter of creating the a
local login with the same username?
I'd use a different username.
And would this run the same local
settings as the current domain login? To put it another way, would
LOCAL/a.user and WORK/a.user share settings on the local machine?
You can probably copy the profile over but I'd be more inclined to
a) create the local user (w/admin rights)
b) log in as the local user
c) customize the profile
d) ensure that you have all *data* (not settings) copied over into this
user's appropriate profile folders
Then I'd simply disjoin the domain and go into a workgroup and use the I
know you can mess around with registry settings but I prefer not to do that,
esp. since it's highly unlikely that your laptop will ever have
communication with the DC any longer, and you'll end up with weird
shards/settings.
"Lanwench [MVP - Exchange]" wrote:
Geoff332 <Geoff332@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi,
I work remotely. I typically login to my work domain on my laptop,
even when it is not on the network (WORK\a.user). A week or so ago,
this login simply failed: I had been logged in and was unable to log
in a few hours later. I received the same error one receives on a
bad password. I can think of no reason for this: I made no changes
to the password, I wasn't connected to any domain, and I didn't
make any software changes. The domain doesn't enforce any password
expiration policy. I double checked with the sys admin: he
confirmed they'd made no changes and was at a loss to explain the
problems I am having.
Since then, I've only been able to log on to this machine using the
local machine's administrator account. My domain username fails.
However, when I log in to the work server remotely, I can access it
using the same (old) username and password without any problem. This
all suggests the problem is on the local computer, not the domain.
Since I work remotely, it's difficult to connect to the domain for
any substantial period of time (and I am not a domain
administrator). I can't do anything with the WORK/a.user account
and haven't set-up the LOCAL/a.user account.
This problem has me bewildered - can anyone offer any explanation
or, more usefully, a fix to this.
Thanks,
Geoff.
I'm not sure, honestly (you might check your event logs) but I have
to question the need (or benefit!) of your computer belonging to the
domain to begin with. If you're never (or very very infrequently)
going to have direct contact with a DC (VPN clients don't generally
count) perhaps this is not worth keeping up. I don't join my
remote/home-user clients' laptops to their domains.
.
- References:
- Domain Login failure
- From: Geoff332
- Re: Domain Login failure
- From: Lanwench [MVP - Exchange]
- Re: Domain Login failure
- From: Geoff332
- Domain Login failure
- Prev by Date: Re: Domain Login failure
- Next by Date: Re: Domain Login failure
- Previous by thread: Re: Domain Login failure
- Next by thread: Re: recover EFS certificate/key without the wizard/cipher.exe
- Index(es):
Relevant Pages
|