Mapped network drives Not connecting at logon

[Guest]

I have 2 windows xp machines one is Home Edition and one is Professional.
Both machines are up to date on all patches. Both machines are also running
Norton systemworks 2004/5. I have intermittent connectivity issues at logon.
The Machines are connecting to the intranet (can get to the internet and
email everytime) but not connecting to the mapped drives on the server. This
problem, as I stated, has no rhyme or reason. When rebooting it is hit or
miss as to which drives will or won't connect. I have run the MS suggested
diagnostic tools, Netdiag and all tests pass for the network cards (realtek
RTL8139/810x Family fast ethernet NIC) and all tests pass. I can ping the
server and other computers on the network. If I click on the mapped drives in
My Computer the drives connect with no problems. I run a dos based
program(GarageKeeper) from the server. It requires drives F:, K:, L:, and Z:
to run. Once the drives are manually connected all is fine. I ran gpedit.msc
and adjusted the settings for Computer Configuration\Administrative
Templates\System\Logon = Always wait for the network at computer startup to
ENABLED and User Configuration\Administrative Templates\System\Scripts\ = Run
logon scripts synchronously to ENABLED. I rebooted and still got the same
intermittent errors. I rebooted several times with several different
combinations of connected drives. I need to get a solution to the problem
because, no matter how many times I show the users how to connect the drives
under My Computer they forget and I have to come and do it for them. I also
have windows 98 machines on site that have no problems connecting everytime
to the drives. Please help me.

Thanks so much for any input!

 

[Badata]

Use a batch file on each machine with the following line for each
mapped drive letter used.
Net Use drive letter \\computername\sharename
example: Net Use F: \\server\garagekeeper
This will set the mapping each time the machine start.

 

[AJR]

Strictly addressing problem stated in subject line e.g. "Mapped Network
Drives Not Connecting On Logon" - was "Reconnect on logon" option checked"?

 

[Guest]

AJR, Thanks for the response, Yes in fact the reconnect at logon is checked.
Still scratching my head.

Badata, Nice suggestion I will try it but need clarification. where should
the batch file be invoked? during the boot process(via autoexec.bat) or after
windows is logged on?

 

[Guest]

Thanks so much. I need to know if the batch file can be invoked at bootup or
will have to have the users invoke it after logon? I have tried the net use
command in testing (after windows logon) and can not get it to connect the
drives. I need to create something transparent to the users. They do not like
change and have a short attention span.

 

[Guest]

Use a batch file on each machine with the following line for each
mapped drive letter used.
Net Use drive letter \\computername\sharename
example: Net Use F: \\server\garagekeeper
This will set the mapping each time the machine start.

Thanks for your input! I created a batch file on one of the xp machines. it does reconnect the drives. There is one problem, if the drives are already connected it comes up with an error 85 or 67 stating that the resource is already in use. This confuses the users and I really need to stay away from that. The drives still connect intermittently at logon. can I write a script that will disable the drives at logoff? I do not mind if I have to manage connectivity manually but I need it to be consistant in order to use the batch file solution. thanks again!