I would also put a persistent tag like below on the end of the drive mapping if you are using a batch file.
net use p: \\server\share /persistent:no
could be that drive letters are being left behind by previous users and the script is failing as the letter is still in use in the registry etc.
Cool glad i could help, unfortunately printer scripting isn't quite as easy as there are lots of different ways to do it. We are lucky here because we are running Windows Server 2003 RC2 and i am using the Print Management tool that comes with it so i have no need to use scripts. But if you read this Wiki it gives you lots of different ways to use scripts to map printers.
"Thanks Justin, that's great. I have tested it with one drive and it seems to do the trick... now to just get the rest of the lists in!
I would also like to do that with networked printers, I presume it will be that simple, too?!"
Seem to be having trouble again.
Maybe it is something in Group Policy.
You said you tested it with one drive and it worked fine, i take it since that post you have added the extra drives and now its failing again. Try removing all the drives and adding them back one at a time to see if it is a particular drive thats causing the problem. Then if you see what is different about that drive to the others it may give you some idea why its causing the problem.
Also just as a thought try enabling the "Run logon scripts syncronously" command in the computer configuration section of your GPO. Oh and make sure "Run logon scripts Asyncronously" is not enabled.
It may slow down your users logon a bit but it will ensure that all scripts are executed.