Re: login problem to a persistent connection to a mapped drive
- From: "James Fabulous" <James.Fabulous@xxxxxxxxxxx>
- Date: Mon, 2 May 2005 09:18:06 -0600
Dan,
Have you considered using the "Map network drive" feature and specifying
a different username and password - Although this is something I'm currently
experiencing some odd behavior with (reconnection issues) the behavior
should work to solve your issues. Another solution is to use a local
loginscript - a simple batch file in the startup folder of the local user
mapping the drive with domain credentials.
Syntax of: net use [drive letter]: \\[member-servername]\[sharename]
password /user:[domainname]\[domain-username] /persistent:YES
Word of warning here that the password is kept in plain text - <MS guilt
trip> C'mon folks how long has the 'net use' command been around and we
still have to worry about plain text passwords? </MS guilt trip> so it is
inherently insecure - however I've found a couple of neat VBS scripts that
can prompt for username and/ or password that you can simply embed in the
batch files - users enter the password once and the drives are mapped.
(Great for users offsite with expired passwords).
VBS - search for userin.vbs and passin.vbs
Hope this helps,
JF
"Dan" <Dan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:85FD60CF-CE69-4B6D-A2EB-8C604D3270AC@xxxxxxxxxxxxxxxx
> We have several Windows XP workstations in a workgroup configuration.
They
> have a persistent connection to a mapped drive on a domain-member server.
> The users are trying to log in to a local account on that server.
>
>
>
> Because the workstation password is different than the mapped-drive
> password, that local account keeps getting locked out and the users have
to
> wait 30 minutes, after which time they can access it with no problem.
> Barring that they can log in if we unlock the account. What we suspect is
> happening is the Windows is attempting to connect to the drive with the
local
> account used to log onto the XP workstation and retrying a few times after
> the password fails.
>
>
>
> The following errors appear in the event log.
>
>
>
> Event Type: Failure Audit
>
> Event Source: Security
>
> Event Category: Account Logon
>
> Event ID: 681
>
> Date: 4/22/2005
>
> Time: 11:43:55 AM
>
> User: NT AUTHORITY\SYSTEM
>
> Computer: SERVER01
>
> Description:
>
> The logon to account: lsmith
>
> by: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
>
> from workstation: WRK01
>
> failed. The error code was: 3221225578
>
> ------------------------------------------------
>
> Event Type: Failure Audit
>
> Event Source: Security
>
> Event Category: Logon/Logoff
>
> Event ID: 529
>
> Date: 4/22/2005
>
> Time: 11:43:55 AM
>
> User: NT AUTHORITY\SYSTEM
>
> Computer: SERVER01
>
> Description:
>
> Logon Failure:
>
> Reason: Unknown user name or bad
password
>
> User Name: lsmith
>
> Domain: WRK01
>
> Logon Type: 3
>
> Logon Process: NtLmSsp
>
> Authentication Package: NTLM
>
> Workstation Name: WRK01
>
>
>
> We know the best solution would be to make them all members of a domain
and
> use domain accounts. Suffice it to say that is not an option. Increasing
> the number of failed attempts before the account locks is also not an
option.
>
>
>
> What we think would be a good workaround is to find a registry fix that
> would limit the number of login retries to 1, so the user would get
prompted
> with a password rather than the system retrying multiple times and locking
> the account. Does anyone know how to do this?
>
>
>
> Any other ideas would also be appreciated.
>
>
>
> Thanks Dan
>
.
- Follow-Ups:
- Prev by Date: Re: Automatic ZIP Downloads
- Next by Date: Re: login problem to a persistent connection to a mapped drive
- Previous by thread: Re: Automatic ZIP Downloads
- Next by thread: Re: login problem to a persistent connection to a mapped drive
- Index(es):
Relevant Pages
|
