Weird problem when changing file names on networked drives

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello,
I am having a bizarre problem when I try to change file or folder names.
For example, I double-click a shortcut on my desktop that goes to a folder on
networked drive (on a separate server, not my desktop machine). I
single-click on a file and rename it and then press enter. The name change
doesn't appear to "take" and the file shows as having the old name. I have
to back out of the folder and then go back in before Windows will recognize
that the file name has changed.

A similar thing happens when I try to create a new folder on a networked
drive. Windows will not recognize that I've created the folder until I back
out of the directory and go back in to refresh the view.

This does NOT happen on drives on my desktop. This appears to be an issue
specific to networked drives. Can I do anything locally to address it? Or
does it have to be addressed at the network admin level somehow?

Thanks for any assistance.
 
Hello,
I am having a bizarre problem when I try to change file or folder names.
For example, I double-click a shortcut on my desktop that goes to a folder on
networked drive (on a separate server, not my desktop machine). I
single-click on a file and rename it and then press enter. The name change
doesn't appear to "take" and the file shows as having the old name. I have
to back out of the folder and then go back in before Windows will recognize
that the file name has changed.

A similar thing happens when I try to create a new folder on a networked
drive. Windows will not recognize that I've created the folder until I back
out of the directory and go back in to refresh the view.

This does NOT happen on drives on my desktop. This appears to be an issue
specific to networked drives. Can I do anything locally to address it? Or
does it have to be addressed at the network admin level somehow?

Thanks for any assistance.

Network latency compounded by basic Explorer mechanics (preview, metadata,
etc.) Try F5 to force a refresh but may still need to wait for network
housekeeping. There are a few patches for slow explorer symptoms but they
are server level, not workstation level. Search for "slow explorer" here
and you'll find many related KB articles:
http://support.microsoft.com/ph/1173/en-us/
 
Nothing Weird or bizarre about that at all. In fact, you answered your own
question next to last paragraph.
 
Back
Top