Interesting. I take it those drives are the ones mapped in the login
script. Should they be accessible as legitimate shares? If so, might there
be a server related issue re. user rights or some problem with cached
credentials? In the case where I used that registry fix, it was for a
stuck past mount that was more easily resolved.

--

"Mayy" <Mayy@discussions.microsoft.com> wrote in message
news:74761167-2303-4312-B177-5816E8CC78A1@microsoft.com...
> Hi GTS,
>
> I've deleted each of the ##server#share keys but there's also 48 keys with
> GUID-style names, and in a fit of inspiration I backed up that section of
> the
> registry and deleted each of those keys. Now, each time I refresh the My
> Computer view and then refresh that section of the registry, the same five
> keys reappear each time.
>
> I delete those keys, go through the refresh process, and the same five
> keys
> reappear. I rename the three drives with unique labels and see those
> labels
> as values within three of these keys. I've no idea if the key names are
> significant, but here they are:
>
> {0BC1C0BB-B1D4-4078-A99A-33B36A6CE84C}
> (corresponds
> to drive P)
> {4fb54bb4-3ed7-11d9-adea-806d6172696f} (no value
> other than "default")
> {4fb54bb5-3ed7-11d9-adea-806d6172696f} (no value
> other than "default")
> {C55B3392-BC85-47A5-9A2A-1E77CC38522A} (corresponds
> to drive M)
> {DA011442-55FA-45B8-9564-2407DEECB60B}
> (corresponds
> to drive T)
>
> Recall that there's only three mapped drives having this issues, no other
> mapped drives, and separate keys for drives A, C and D and one key called
> CPC.
>
> Now here's the interesting bit.
>
> I reboot, and the names I called the shares above are lost and they are
> each
> again called "Disconnected Network Drive". Another four keys appear under
> MountPoints2, and three of the new keys relate to the disconnected drives.
> The keys I noted above are still present, but now apparently redundant.
>
> I hope this helps ... (it hasn't helped me!!)
>
>
>
> "GTS" wrote:
>
>> I have found that when all else fails (particularly net use * /delete)
>> that
>> a registry edit may fix the problem. (Usual warnings - be careful re.
>> editing registry...)
>>