All drives being mapped on one station

[Bill]

I have 35 XP pro stations w/53 users going into a 2003 server. All users use
the following login script

net use * /delete
net use /persistent:no
net use F: \\Jcpd2ksrv1\Apps
net use L: \\jcpd2ksrv2\live

this has worked fine for a long time.
A week or so ago one station started showing all drives (E through Z) as
disconnected mapped drives, but if you clicked on them they each opened to
what should have been the F: drive.

This happens with every user on this machine, but not on any other
workstation.
It doesn't matter whether or not it is a network or local logon. Even local
logons still show all drives as disconnected maps and they all lead to the
same place.
Even if he starts the pc with a USB drive plugged in it ignores it and shows
all drives as disconnected maps.

If I run net use * /delete the response is that there are no maps on the
list.
If I try to run the net use to map a drive it replies that the letter is
already in use.

Any suggestions would be greatly appreciated.

Bill

 

[My Boss's Secretary]

Go to the following thread here ( listed below ) and see what others have
done or are doing. You're not alone, this problem seems to keep poping up.

http://www.microsoft.com/windowsxp/...&p=1&tid=4b4f88ec-093e-4366-8c42-520b2cd2608a

Seems to be pointing towards Symantec Antivirus, but I have not confirmed
that on my machines. Good Luck ! !

 

[Bill]

I read that one before I posted, it looks like the same problem, but I was
hoping that someone had come up with a solution since removing Symantec is
out of the question.

Bill

 

[Bill]

Thanks for the response, but removing Symantec is out of the question and I
haven't been able to find anything else that works.
The suggestion I got from my post on Techrepublic
http://techrepublic.com.com/5208-6230-0.html?forumID=101&threadID=248420&messageID=2387552
was to modify the mountpoints part of the registry, but that did not do any
good.

The drives will disappear after a restart, but reappear almost exactly one
minute after someone logs on.

Bill

 

[Pegasus \(MVP\)]

If you can demostrate that Symantec software is the culprit
then this would be a case for the Symantec HelpDesk to resolve,
if only to protect the Symantec reputation.