Mapped Network Drive Showing as Disconnected

Configuration is Windows Server 2008 domain controller with Windows XP clients.

I've created a startup command file to map a network drive and then install an application on all the clients in the domain.  Commands are:

net use Z: \\server\share
Z:\setup.exe -s -f1Z:\setup.iss

Both commands execute successfully and application gets installed.  However, the mapped drive shows as "Disconnected Network Drive (Z:)"  although it's functioning as a connected drive.

I've tried using

net config server /autodisconnect:-1

but this didn't help.

While I'm accomplishing what's intended from the startup command file, I would like to solve the odd display of the mapped drive.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Does it immediately show up as disconnected, or only after a period of time?

Are you using Symantec Antvirus on your XP clients?  If so, check (it says Server 2003 in the document though).

You can also try manually disconnecting the drive from the registry...
Delete the "##server##share entry", then in My Computer, Right Click the z: drive and disconnect.  Restart and let it reconnect the drive.
767WuLiMasterAuthor Commented:
It shows up immediately as disconnected.  The installed application needs the drive to be connected and for all practical purposes, it is.

I'm using AVG 8.5, (not the free version) on the clients. Perhaps a similar situation to Symantec.
767WuLiMasterAuthor Commented:
Uninstalled AVG 8.5 but still same results.

If I map a network drive in My Computer on the client, I get a message that a network drive couldn't be connected, but mapped drive displays correctly.

I can live with the problem, but troubling that mapping drives via a server startup command file doesn't behave properly. A Microsoft feature I guess.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.