"Network Drive"?

[UserGroupUser]

I have a system with XP Pro Service Pack 3.

At start up, a *.vbs script maps network drives for the user.

In Windows explorer, instead of the "share on 'server' (M)" appearing it
says "Network Drive (M)". Each reboot changes the symptoms but there is
always one or more network drives that demonstrate this behaviour.

Any ideas as to how I might resolve, welcomed.

 

[N. Miller]

I have a system with XP Pro Service Pack 3.

At start up, a *.vbs script maps network drives for the user.

In Windows explorer, instead of the "share on 'server' (M)" appearing it
says "Network Drive (M)". Each reboot changes the symptoms but there is
always one or more network drives that demonstrate this behaviour.

Any ideas as to how I might resolve, welcomed.

I don't use any kind of script to map the drives on bootup. When I initially
mapped my drives, I put a check in the box labeled, "Reconnect at logon".
That seems to work, as long as the other devices are already powered up. If
a device is not powered up when I boot, I get a pop up notice to that
effect, and the option to retain the automatic reconnect, or delete it.

This was done using the GUI menus which are presented when clicking on the
"Tools" option in the toolbar, and then the "Map Network Drive..." option.

This even works on the HP Pavilion dv2610us, running Windows Vista Home
Premium, without shares enabled. While it is not sharing, and can't find the
network (that is *not* a problem, but by user intent!), it can access shares
on other computers.

 

[UserGroupUser]

Many thanks for the response. I think the scripting may be a red herring.

The scripting method is used on many machines without this symptom and I
need to use the scripts to ensure commonality between systems.