forcing network to be available before login

[Guest]

Hi there

I've got following problem:

We have an isolated system (peer-to-peer, no domain) with some WinXP SP2
Clients. After logging in, there's a script for mapping network drives
running. But due the network isn't initialized at this time, mapping fails!
I've set the "Always wait for network..." Policy to "enabled" trough
gpedit.msc on each Client.
No Success!
I have still to wait a couple of seconds after login with executing the
script!

Any Ideas why this Policy doesn't work?

Thanks for any help, Raffael

 

[Robert L [MS-MVP]]

You may want to map the network drives using persistent switch. these page may help,
mapping Cause: the drive has a persistent mapping or reconnect when logon. ... That will map to \\cbgntB\shared. Also you may want to use NET USE I: ...
www.chicagotech.net/mapping.htm


windows slow issues 4) Instead of connecting a persistent network drive to a network location, use logon script to map the network drive with /persistent:no option. ...
www.chicagotech.net/winslow.htm


domain faqs The reason is that net use /persistent:yes is default settings for NT and ... That will map to \\cbgntB\shared. Also you may want to use NET USE I: ...
www.chicagotech.net/domainfaqs.htm



Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
Hi there

I've got following problem:

We have an isolated system (peer-to-peer, no domain) with some WinXP SP2
Clients. After logging in, there's a script for mapping network drives
running. But due the network isn't initialized at this time, mapping fails!
I've set the "Always wait for network..." Policy to "enabled" trough
gpedit.msc on each Client.
No Success!
I have still to wait a couple of seconds after login with executing the
script!

Any Ideas why this Policy doesn't work?

Thanks for any help, Raffael

 

[Guest]

Hi Robert

The persistent switch can't be the solution...if the user logs on and tries
to start programs located on the share, it will fail.
You can see the mappings in windows explorer, but accessing it also results
in a failure, until the network services are started...

The "Always wait for the network..." Policy is exactly what I imagine...if
it would work.
Anyway, thanks for your answer!