Celebrate National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Win XP with SP2 workgroup PC login script with drive mappings failing.

Posted on 2006-07-19
7
Medium Priority
?
307 Views
Last Modified: 2008-01-09
I have some windows xp sp2 machines that are part of a workgroup, but not part of a domain.

The PC's use autologon as the PC's operate unattended, and need to logon automatically.

I have a logon script that runs, and inside the login script is various drive mappings and xcopy operations from network drives to the local drives.

The trouble is that the logon script operations that involve network drive activity fail.

I believe this is because the script is running before the network has finished setting up.

If I place a pause at the start of the script, wait 10 seconds after logon and then press enter the logon script works fine.

I have tried various registry values and group policy entries to try fix the problem, but none of them seem to actually have ANY effect at all, the desktop and logon script are still appearing before the network is completing its setup.

I am delibrately not stating which registry settings or group policy settings I have tried as I to start the investigation again from scratch and not pre-empt  any offered solutions.

The error message being returned by my command: 'net use \\J: \\deathstar\apps /yes /persistent:no' is 'System Error 67 has ocurred'

What IS interesting is that the command before that: 'net time \\deathstar /set /y' completes okay.

Any suggestions or help would be apprecated.
0
Comment
Question by:StuartWhelan
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
7 Comments
 
LVL 10

Expert Comment

by:fm250
ID: 17142268
this seems to be a problem with xp. I have seen many post like this with no solution. but one thing will work is to make a loop till it successed.  

see here:
http://www.experts-exchange.com/Operating_Systems/Windows_Server_2003/Q_21040935.html

0
 
LVL 11

Expert Comment

by:grsteed
ID: 17142409
Have you tried to enable this Group Policy? (Start > Run > gpedit.msc)

Local Computer Policy > Computer Configuration > Administrative Templates > System > Logon
"Always wait for network at computer startup and logon"

I also had a problem where XP wouldn't automatically connect to a Samba share event though it was mapped  with the "reconnect at logon" option. What I did that worked was to put a batch file with the "net use" command in the Startup folder of All Users. (C:\Documents and Settings\All Users\Start Menu\Programs\Startup)

It seemed like that happens later than other methods and the network was available. I had also tried the "net use" command in the autoexec.bat file and it failed as well.

Cheers,

Gary
0
 

Author Comment

by:StuartWhelan
ID: 17142459
fm250: Thankyou for your comment, I will attempt this answer as a workaround if no better fixes are found.

grsteed: Thankyou for your comment, Yes, I have enabled that group policy. I have just tried moving the logon script to the folder you suggested, but the same symptoms occur.
0
Portable, direct connect server access

The ATEN CV211 connects a laptop directly to any server allowing you instant access to perform data maintenance and local operations, for quick troubleshooting, updating, service and repair.

 
LVL 4

Expert Comment

by:Jeb911
ID: 17145190
You need to delete the mappings first - then map the drives....
net use x: \\server\share /d

then use  net use x: \\server\share /yes


-JEB
0
 
LVL 11

Accepted Solution

by:
grsteed earned 1500 total points
ID: 17147305
> 'net use \\J: \\deathstar\apps /yes /persistent:no'

Just curious, why are you using "persistent:no"?  If you are going to use this drive mapping everytime, I would think YES would be more appropriate.
0
 

Author Comment

by:StuartWhelan
ID: 17151248
Thankyou grsteed, your answer put me on the right track.

It seems having the drives presistent and enabling 'Always wait for network at computer startup and logon' will result in the execution of the logon script being delayed until the mappings have completed, allowing the script to run sucessfully.

Thankyou!
0
 
LVL 11

Expert Comment

by:grsteed
ID: 17154100
Thanks!  Glad to help
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When you try to share a printer , you may receive one of the following error messages. Error message when you use the Add Printer Wizard to share a printer: Windows could not share your printer. Operation could not be completed (Error 0x000006…
Make the most of your online learning experience.
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…

730 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question