There was a bug in RC2 that still exists in Vista RTM and it is a huge problem!

Vista tries to connect mapped drives that require a password when it should
know to request a password from the user. Because it tries to connect with
no password, and does so repeatedly even though it keeps failing, it locks
out the user account almost instantly - at least almost instantly in "user"
time, if not in processor time.

I don't know if this is the only way it happens, but for me, I automatically
set Explorer to use Windows classic folders so that I have a menu. From the
menu, follow these steps to reproduce the problem:

1. Click Tools and then Map Network Drive...
2. In the Map Network Drive dialog, select the drive letter and the path to
the network share.
3. Make sure that Reconnect at logon is checked.
4. Click Finish.
5. At this point, Windows pops up a logon dialog. I enter the username and
password. There is a check box labeled Remember my password which I leave
unchecked so it will not remember the password. I enter the username for the
share in the format of:
remotecomputername\username
6. Click OK on the logon dialog.

At this point the mapped drive functions as expected.

7. Reboot and logon to Vista again. At this point, since you did not check
to remember the password, Windows should not try to connect or, if it is
going to connect, it should propmt for a username and password first.
8. Open Computer in Explorer and double-click the mapped drive. You will
get a message that the account is locked out.

Even though you told Vista to not remember the password, it tries to connect
with no password rather than prompting for a password. And, after failing
once, twice, thrice, instead of saying, "Geeze, if I keep hitting my head on
this brick wall and it doesn't move, I wonder what will happen if I hit my
head on it again?", Windows just keeps trying until the account is locked.

This is a major issue. Microsoft needs to either pull Vista from RTM or
release an immediate hotfix for this issue!

Thanks,

Dale

--
Dale Preston
MCAD C#
MCSE, MCDBA

Once you follow the steps of the original post and then delete the mapped
drive, you will never be able to map a drive to that share again. To even
try will lock out your account on the remote computer.

Even though, again, I told Windows not to remember the password, if I
disconnect the mapped drive and then try to map the drive again, Vista tries
to connect to the share with the blank password and, again banging its head
against the proverbial brick wall repeatedly, wondering if it will get a
different result if it tries the exact same thing often enough, it tries
until the account on the remote pc is locked out again.

I was able to fool it once. The first time I mapped to
\\remotecomputer\sharename. After I deleted that mapped drive and couldn't
connect again because Vista kept locking out my account, I fooled it by
mapping to \\remotecomputer\sharename\. Notice the appended backslash the
second time.

That worked once. Of course, after that, I wasn't able to connect to either
share again and to even try would lock out my account on the remote pc. This
is a huge bug, Microsoft!

Dale
--
Dale Preston
MCAD C#
MCSE, MCDBA


"Dale" wrote:

There was a bug in RC2 that still exists in Vista RTM and it is a huge problem!

Vista tries to connect mapped drives that require a password when it should
know to request a password from the user. Because it tries to connect with
no password, and does so repeatedly even though it keeps failing, it locks
out the user account almost instantly - at least almost instantly in "user"
time, if not in processor time.

I don't know if this is the only way it happens, but for me, I automatically
set Explorer to use Windows classic folders so that I have a menu. From the
menu, follow these steps to reproduce the problem:

1. Click Tools and then Map Network Drive...
2. In the Map Network Drive dialog, select the drive letter and the path to
the network share.
3. Make sure that Reconnect at logon is checked.
4. Click Finish.
5. At this point, Windows pops up a logon dialog. I enter the username and
password. There is a check box labeled Remember my password which I leave
unchecked so it will not remember the password. I enter the username for the
share in the format of:
remotecomputername\username
6. Click OK on the logon dialog.

At this point the mapped drive functions as expected.

7. Reboot and logon to Vista again. At this point, since you did not check
to remember the password, Windows should not try to connect or, if it is
going to connect, it should propmt for a username and password first.
8. Open Computer in Explorer and double-click the mapped drive. You will
get a message that the account is locked out.

Even though you told Vista to not remember the password, it tries to connect
with no password rather than prompting for a password. And, after failing
once, twice, thrice, instead of saying, "Geeze, if I keep hitting my head on
this brick wall and it doesn't move, I wonder what will happen if I hit my
head on it again?", Windows just keeps trying until the account is locked.

This is a major issue. Microsoft needs to either pull Vista from RTM or
release an immediate hotfix for this issue!

Thanks,

Dale

--
Dale Preston
MCAD C#
MCSE, MCDBA

Of course they won't pull Vista from RTM.
Please do bug report on this, to be fixed at the next opportunity (SP1 or some hotfix).

Regards,
--PA

"Dale" wrote in message ...
There was a bug in RC2 that still exists in Vista RTM and it is a huge problem!

Vista tries to connect mapped drives that require a password when it should
know to request a password from the user. Because it tries to connect with
no password, and does so repeatedly even though it keeps failing, it locks
out the user account almost instantly - at least almost instantly in "user"
time, if not in processor time.

I don't know if this is the only way it happens, but for me, I automatically
set Explorer to use Windows classic folders so that I have a menu. From the
menu, follow these steps to reproduce the problem:

1. Click Tools and then Map Network Drive...
2. In the Map Network Drive dialog, select the drive letter and the path to
the network share.
3. Make sure that Reconnect at logon is checked.
4. Click Finish.
5. At this point, Windows pops up a logon dialog. I enter the username and
password. There is a check box labeled Remember my password which I leave
unchecked so it will not remember the password. I enter the username for the
share in the format of:
remotecomputername\username
6. Click OK on the logon dialog.

At this point the mapped drive functions as expected.

7. Reboot and logon to Vista again. At this point, since you did not check
to remember the password, Windows should not try to connect or, if it is
going to connect, it should propmt for a username and password first.
8. Open Computer in Explorer and double-click the mapped drive. You will
get a message that the account is locked out.

Even though you told Vista to not remember the password, it tries to connect
with no password rather than prompting for a password. And, after failing
once, twice, thrice, instead of saying, "Geeze, if I keep hitting my head on
this brick wall and it doesn't move, I wonder what will happen if I hit my
head on it again?", Windows just keeps trying until the account is locked.

This is a major issue. Microsoft needs to either pull Vista from RTM or
release an immediate hotfix for this issue!

Thanks,

Dale

--
Dale Preston
MCAD C#
MCSE, MCDBA

Of all the bugs I have seen discussed in the groups over the last couple
days, this is the most serious and most far reaching. This will result in
thousands of locked out accounts in networked Vistas - where Microsoft is
doing their initial push on November 30th - and thousands of helpdesk calls
for password resets.

Single system users and even most small home networks will never see this
issue but thousands of business users will see it.

I think it is much to critical to wait for SP1 or to even wait until
November 30th.

Dale
--
Dale Preston
MCAD C#
MCSE, MCDBA


"Pavel A." wrote:

Of course they won't pull Vista from RTM.
Please do bug report on this, to be fixed at the next opportunity (SP1 or some hotfix).

Regards,
--PA