Tom's Hardware > Forum > Windows 2000/NT > Windows 2000/NT General Discussion > Remapped Network Drives display old name

Remapped Network Drives display old name

Forum Windows 2000/NT : Windows 2000/NT General Discussion - Remapped Network Drives display old name

Tom's Hardware: Over 1.4 million members in 6 different countries available to answer all your high-tech questions. Sign up now! Its free!
Word :    Username :           
 

Archived from groups: microsoft.public.win2000.general (More info?)

 

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?

Sponsored Links
Register or log in to remove.

Archived from groups: microsoft.public.win2000.general (More info?)

 

In news:D0F33DFF-7160-4A3C-9519-A01AABCE8C06@microsoft.com,
Kevin R Cunningham <Kevin R Cunningham@discussions.microsoft.com> typed:
> 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?

Reply to Anonymous

Archived from groups: microsoft.public.win2000.general (More info?)

 

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]" wrote:

>
>
> In news:D0F33DFF-7160-4A3C-9519-A01AABCE8C06@microsoft.com,
> Kevin R Cunningham <Kevin R Cunningham@discussions.microsoft.com> typed:
> > 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?
>
>
>

Reply to Anonymous

Archived from groups: microsoft.public.win2000.general (More info?)

 

In news:85DE685C-3F44-4FA6-BE4F-F51721F96598@microsoft.com,
Kevin R Cunningham <KevinRCunningham@discussions.microsoft.com> typed:
> 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?

>
> "Lanwench [MVP - Exchange]" wrote:
>
>>
>>
>> In news:D0F33DFF-7160-4A3C-9519-A01AABCE8C06@microsoft.com,
>> Kevin R Cunningham <Kevin R Cunningham@discussions.microsoft.com>
>> typed:
>>> 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?

Reply to Anonymous
Tom's Hardware > Forum > Windows 2000/NT > Windows 2000/NT General Discussion > Remapped Network Drives display old name
Go to:

There are 679 identified and unidentified users. To see the list of identified users, Click here.

Please mind

You are about to answer a thread that has been inactive for more than 6 months.
If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.

Add a reply Cancel
Sponsored links
  • Ask the community now
  • Publish
Ad
They won a badge
Join us in greeting them