Pinning Network Files (Strange Behaviour)

[copernicus]

Okay, so I was having some issues before with pinning network files to the explorer item on the taskbar.

I can now replicate the bug happening. I want to see if it's just my setup or windows 7, so I'd be much obliged if someone can test this out for me as well.

First Scenario
1) First map a network drive.
2) Pin it to the explorer item on the taskbar by dragging it there.
3) Open up the destiation through the jump list.
4) navigate a couple of folders down and open any file.

What you should get is the network drive is no longer pinned. However, the folder where the file you just opened resided has taken it's place.

Second Scenario
1) Navigate to a network destination through windows explorer (not a mapped drive)
2) Pin a Folder from that network destination by gragging to the taskbar.
3) Pin another folder than resides inside a folder in step 2

Result: Folder pinned in step 2 is replaced by folder pinned in step 3

 

[Abhimanyu]

This doesn't happen with me.
In the first scenario the network drive was still pinned.
In the second scenario too there were two separate pinned items.

 

[copernicus]

Hmm, that's interesting. I've had this happen on two fresh installs. 7077 and now 7100. Both x64

Gotta see what's fishy about my network locations. Thanks.

 

[copernicus]

I managed to replicate this on my netbook x86 with the same network destinations. This is on build 7137.

Tried doing the same procedure to my netbook harddrive and the items stayed pinned.

This is very very strange.

There seem sto be something about my readynas that's making this happen.

 

[Zak8022]

copernicus, i'm having the same issue. You mentioned that you have a ReadyNas... and so do i. I'm wondering if that might be part of the problem we are having? Have you been able to find some sort of fix to this problem?

 

[copernicus]

Nope, no fix. It's a problem with pinning network destinations. =(

 

[Zak8022]

Sucks. Thanks for the update though. I was starting to go mad thinking i had screwed something up.

 

[sigfried]

Hello. I finally found a way to solve that damn problem! I've noticed it happens with only one server, an old Linux samba shared. Our admin upgraded the server and now it works! If it could help you !
Daniel