Network Share Logon Prompt

[just say NO to PDF]

Hi:

In Windows 2000, if you have connections to network shares with "reconnect
at logon" checked, you are prompted for Username/Password after you logon -
when the connection to the share is made using a different account.

OK, but WXP does not do that! Instead you get some balloon telling you you
have a problem.

Does anyone know how to change the behaviour of XP to prompt for "share
Username/Password" at logon time?

TIA!
--Maarten (e-mail address removed)

 

[PS]

Hi:

In Windows 2000, if you have connections to network shares with "reconnect
at logon" checked, you are prompted for Username/Password after you logon -
when the connection to the share is made using a different account.

OK, but WXP does not do that! Instead you get some balloon telling you you
have a problem.

Does anyone know how to change the behaviour of XP to prompt for "share
Username/Password" at logon time?

TIA!
--Maarten (e-mail address removed)

Maarten-

This is probably because your mapped drives require different user account
than the one you logon with. For this same reason I do it the old fashioned
way. A map.cmd file is the users startup directory with net use commands
connecting the user to the share.

GOod Luck
PS

 

[Torgeir Bakken (MVP)]

In Windows 2000, if you have connections to network shares with "reconnect
at logon" checked, you are prompted for Username/Password after you logon -
when the connection to the share is made using a different account.

OK, but WXP does not do that! Instead you get some balloon telling you you
have a problem.

Does anyone know how to change the behaviour of XP to prompt for "share
Username/Password" at logon time?

Hi

This might be the cause of it:

Description of the Windows XP Professional Fast Logon Optimization Feature
http://support.microsoft.com/default.aspx?kbid=305293

<quote>
By default in Windows XP Professional, the Fast Logon Optimization feature
is set for both domain and workgroup members. As a result, Windows XP does
not wait for the network to be fully initialized at startup and logon.
</quote>


To disable this and see if it helps on your problem, try to set the
"Always wait for the network at computer startup and logon" policy
(a negative side effect is that it might make the startup/logon to
take longer time):

Test it on a couple of computers first, and if it solves the problem and
you have Active Directory, use a Group Policy to deploy it to all clients.

To test it on a computer, you can do like this:

By registry edit; Set the value SyncForegroundPolicy to 1 (REG_DWORD) in
this key:

HKEY_LOCAL_MACHINE\Software
\Policies\Microsoft\Windows NT
\CurrentVersion\Winlogon\

Create the necessary keys/value, or put the vbscript below in a .vbs file
and double-click on it.

' --------- script start ---------
Set oShell = CreateObject("WScript.Shell")
sRegValue = "HKLM\Software\Policies\Microsoft\Windows NT\" _
& "CurrentVersion\Winlogon\SyncForegroundPolicy"

oShell.RegWrite sRegValue, 1, "REG_DWORD"

MsgBox "Please reboot the computer"

' --------- script end ---------


You can set it through gpedit.msc as well:

Start/Run/gpedit.msc

Then navigate to the following section:
Computer Configuration\Administrative Templates
\System\Logon\ Always wait for the network at computer startup and logon

Double click on it and select Enabled

 

[Guest]

-----Original Message-----
Hi:

In Windows 2000, if you have connections to network shares with "reconnect
at logon" checked, you are prompted for

Username/Password after you logon -

 

[Guest]

-----Original Message-----
Username/Password after you
logon -
Maarten-

This is probably because your mapped drives require different user account
than the one you logon with. For this same reason I do it the old fashioned
way. A map.cmd file is the users startup directory with net use commands
connecting the user to the share.

GOod Luck
PS


.

 

[Guest]

-----Original Message-----


Hi

This might be the cause of it:

Description of the Windows XP Professional Fast Logon Optimization Feature
http://support.microsoft.com/default.aspx?kbid=305293

<quote>
By default in Windows XP Professional, the Fast Logon Optimization feature
is set for both domain and workgroup members. As a result, Windows XP does
not wait for the network to be fully initialized at startup and logon.
</quote>


To disable this and see if it helps on your problem, try to set the
"Always wait for the network at computer startup and logon" policy
(a negative side effect is that it might make the startup/logon to
take longer time):

Test it on a couple of computers first, and if it solves the problem and
you have Active Directory, use a Group Policy to deploy it to all clients.

To test it on a computer, you can do like this:

By registry edit; Set the value SyncForegroundPolicy to 1 (REG_DWORD) in
this key:

HKEY_LOCAL_MACHINE\Software
\Policies\Microsoft\Windows NT
\CurrentVersion\Winlogon\

Create the necessary keys/value, or put the vbscript below in a .vbs file
and double-click on it.

' --------- script start ---------
Set oShell = CreateObject("WScript.Shell")
sRegValue = "HKLM\Software\Policies\Microsoft\Windows NT\" _

& "CurrentVersion\Winlogon\SyncForegroundPolicy"

 

[just say NO to PDF]

No go - see comments below...

Hi

This might be the cause of it:

Description of the Windows XP Professional Fast Logon Optimization Feature
http://support.microsoft.com/default.aspx?kbid=305293

<quote>
By default in Windows XP Professional, the Fast Logon Optimization feature
is set for both domain and workgroup members. As a result, Windows XP does
not wait for the network to be fully initialized at startup and logon.
</quote>


To disable this and see if it helps on your problem, try to set the
"Always wait for the network at computer startup and logon" policy
(a negative side effect is that it might make the startup/logon to
take longer time):

Test it on a couple of computers first ...
snip 8x-------------------------------------
torgeir
Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of the 1328 page
Scripting Guide: http://www.microsoft.com/technet/scriptcenter

Hey, Thanks Torgier - it's an interesting angle...but no cigar.

I used MMC/Group Policy/Local Computer to set the local policy,
but after reading the KB article and running on my system, I think this
applies to how GP and logon scripts are processed. NOT mapped drives.

I am still not prompted for username/password for these mapped drives that
"Connect using a different user name"
I still get the idiot balloon instead.

Someone suggested that "this is probably because your mapped drives
require different user account than the one you logon with"
....that is *exactly* the reason.

Anyone else know how to change back the behaviour?

TIA
-- Maarten

 

[purplehaz]

No go - see comments below...



Hey, Thanks Torgier - it's an interesting angle...but no cigar.

I used MMC/Group Policy/Local Computer to set the local policy,
but after reading the KB article and running on my system, I think
this applies to how GP and logon scripts are processed. NOT mapped
drives.

I am still not prompted for username/password for these mapped drives
that "Connect using a different user name"
I still get the idiot balloon instead.

Someone suggested that "this is probably because your mapped drives
require different user account than the one you logon with"
...that is *exactly* the reason.

Anyone else know how to change back the behaviour?

I don't think xp does prompt you when you set it to log on to a mapped drive
with different credentials. At least I have never seen it prompt in this
setup. If you set it to connect using a different user name, then that's
what it does. When you check that option, during the map drive setup, you
then enter in the user/pass credentials that you want the mapped drive to
use and it uses it. Why would it prompt you, you already told it what to
use? And if you get a popup that says couldn't recconect to drive, then your
user/pass you set is wrong. This is to make mapped drives connect more
seemlessly.

 

[just say NO to PDF]

I don't think xp does prompt you when you set it to log on to a mapped drive
with different credentials. At least I have never seen it prompt in this
setup. If you set it to connect using a different user name, then that's
what it does. When you check that option, during the map drive setup, you
then enter in the user/pass credentials that you want the mapped drive to
use and it uses it. Why would it prompt you, you already told it what to
use? And if you get a popup that says couldn't recconect to drive, then your
user/pass you set is wrong. This is to make mapped drives connect more
seemlessly.

XP does not prompt you; 2000 does.

Why would it prompt you? Because you have rebooted/re-logon-ed (!), and
Windows does not cache passwords for "Connect using a different user name"
drives (probably a security issue).

It does cache user name, but never passwords.
(Try it)

 

[purplehaz]

XP does not prompt you; 2000 does.

Why would it prompt you? Because you have rebooted/re-logon-ed (!),
and Windows does not cache passwords for "Connect using a different
user name" drives (probably a security issue).

It does cache user name, but never passwords.
(Try it)

Ahhh...... yes you are correct. I didn't realize you were rebooting or
logging off and on. I was thinking you were just locking the machine down.
My mistake. Not sure what I was thinking. ;o) I don't know of a "fix" for
this, except to type in the password each time or set up the mapped drive to
connect using the current logged in user. Sorry I couldn't help more.