|
|
Back to UserFriendly Strip Comments Index
|
ChuckAB's ATTN: Post | by ChuckAB | 2008-09-15 18:04:25 |
| ATTN: UFicle(Windows XP Gurus) |
by ChuckAB |
2008-09-15 19:00:50 |
One of the more annoying XP differences when compared with W2K is the way it handles network drive mappings. In W2K at logon when a drive mapping requires a username/password that is not the same as the currently logged-on username/password, it would pop-up a login dialog with the remembered username from the last session. Supply password and you're golden with only one bad password attempt.
In WinXP, it will only pop-up a little balloon telling you that it couldn't "... reconnect all network drives. Click here to open Explorer to view status." So you click on the balloon to open Explorer. When you click on the "disconnected" drive, you are presented with a login dialog where you can put in your password for the network resource.
What's the problem? Well, in my environment, you only get three chances to put in the correct password or your user account is locked. In the above scenario, you've used 2 just to get to the place where you can enter a password. If you fat-finger it just once, your account is locked and has to be unlocked by an administrator (parent network policy).
The server is not a member of the user's logon domain (it's in a workgroup - long story); therefore, I can't give access based on the user's domain account. It has to be a local account. Setting up a domain with a trust relationship has been a non-starter for a long time with my parent network. (Even a one-way....)
Here's what I want to do:
1. Present the userid/password dialog when XP FIRST tries to reconnect the network resource (like W2K).
...
OR
...
2. DON'T attempt to restore the connection until the user explicitly connects to it by using an Explorer session or accessing a shortcut that refers to the resource and THEN putting up a UID/PW dialog like it does now.
Clear as mud? |
|
[ Reply ] |
|
|
[Todays Cartoon Discussion]
[News Index]
|
|
