Remapped Network Drives display old name

[Guest]

When user disconnects a network drive and then connects a new network drive
to a different location using the same drive letter, Windows Explorer is
still showing the old location next to the drive letter. The mapping itself
is fine (contents of the drive are correct), but the drive description being
wrong is causing some confusion.

This is happening on a terminal services session accessed via Citrix
metaframe. The server is running Windows 2000 Server SP4 and Citrix
Metaframe Presentation Server 3- although I have seen what I beleve to be the
same issue on our standard Windows XP desktop build.

This would appear to be identical symptoms to those described in knowledge
base article 306117 - but the cause/solution detailed are not applicable.

Has anyone else come across this, and if so is there a known resolution?

 

[Lanwench [MVP - Exchange]]

In

When user disconnects a network drive and then connects a new network
drive to a different location using the same drive letter, Windows
Explorer is still showing the old location next to the drive letter.
The mapping itself is fine (contents of the drive are correct), but
the drive description being wrong is causing some confusion.

This is happening on a terminal services session accessed via Citrix
metaframe. The server is running Windows 2000 Server SP4 and Citrix
Metaframe Presentation Server 3- although I have seen what I beleve
to be the same issue on our standard Windows XP desktop build.

This would appear to be identical symptoms to those described in
knowledge base article 306117 - but the cause/solution detailed are
not applicable.

Has anyone else come across this, and if so is there a known
resolution?

My somewhat OT question is, why are users disconnecting & remapping drives
in the first place? Is this really necessary?

 

[Guest]

There are valid reaons for this requirement. In the specific case I have
been dealing with, this is server administrator logging on to our network
through Citrix and performing tasks on a long list of servers (requiring a
mapping to each one) - our admin guys usually have about 8 or 9 drives mapped
by login script, so that doesn't leave too many letters of the alphabet to
play with before old drives must be disconnected to allow further mappings to
be made.

 

[Lanwench [MVP - Exchange]]

In

There are valid reaons for this requirement. In the specific case I
have been dealing with, this is server administrator logging on to
our network through Citrix and performing tasks on a long list of
servers (requiring a mapping to each one) - our admin guys usually
have about 8 or 9 drives mapped by login script, so that doesn't
leave too many letters of the alphabet to play with before old drives
must be disconnected to allow further mappings to be made.

OK, well, I'd have to wonder why UNC paths wouldn't work, but that's beside
the point, I guess.
Does this happen *outside* of Citrix/TS ? Meaning, can you reproduce it on a
client workstation at the console?