S
Svenks
Hi all,
We have a member server in Domain A, call it W2K1. Users in Domain B can
connect
to this server using a small application and using a local account on W2K1.
Only problem
until recently was that the users would need the same password on W2K1 and
on their
own domain. If not, another application would fail, something to do with
cached credentials.
Enter XP on some of the clients. What we see now is some (but not all) of
the XP clients
getting locked out of W2K1 when they change their domain password. From W2K1
security log, I can see that about 20 logon attempts occur as soon as the
users logs on
to XP. He does not use the mentioned app to do it, it happens at once. Of
course, if
he had just changed his domain password, these logon attempts causes him to
be locked
out from our server.
Examining 2 users pc's (one with the problem, one without), I find no big
differences:
No persistent drives, no references to our server in Startup groups. In
their registry,
however, there are some references to our server under
HKCU\.....\Mountpoints2.
But that is true for both users. The only clue I have is the fact that the
user with the
problem has an USB device (removeable disk), which mounts using E:. But if
he does
not have that device plugged in, W2K1 gets mapped to E:. The user without
the problem
connects to our server using J:. He also has an USB thingy.
I have tried to duplicate User1's setup using a removeable drive, and I have
succeded
in getting both the USB thing and server drive mapping to the same letter at
the same time.
But that did not cause the problem, and I seem to be unable to re-create it
at all.
Any ideas, anyone?
TIA
--
BRGDS
Sven Sørensen, MCSE
Scandinavian Airlines
Copenhagen, Denmark
To reply by E-mail, please remove *NOSPAM* from address.
We have a member server in Domain A, call it W2K1. Users in Domain B can
connect
to this server using a small application and using a local account on W2K1.
Only problem
until recently was that the users would need the same password on W2K1 and
on their
own domain. If not, another application would fail, something to do with
cached credentials.
Enter XP on some of the clients. What we see now is some (but not all) of
the XP clients
getting locked out of W2K1 when they change their domain password. From W2K1
security log, I can see that about 20 logon attempts occur as soon as the
users logs on
to XP. He does not use the mentioned app to do it, it happens at once. Of
course, if
he had just changed his domain password, these logon attempts causes him to
be locked
out from our server.
Examining 2 users pc's (one with the problem, one without), I find no big
differences:
No persistent drives, no references to our server in Startup groups. In
their registry,
however, there are some references to our server under
HKCU\.....\Mountpoints2.
But that is true for both users. The only clue I have is the fact that the
user with the
problem has an USB device (removeable disk), which mounts using E:. But if
he does
not have that device plugged in, W2K1 gets mapped to E:. The user without
the problem
connects to our server using J:. He also has an USB thingy.
I have tried to duplicate User1's setup using a removeable drive, and I have
succeded
in getting both the USB thing and server drive mapping to the same letter at
the same time.
But that did not cause the problem, and I seem to be unable to re-create it
at all.
Any ideas, anyone?
TIA
--
BRGDS
Sven Sørensen, MCSE
Scandinavian Airlines
Copenhagen, Denmark
To reply by E-mail, please remove *NOSPAM* from address.