This is most likely a question of setting the appropriate
NTFS permissions on the network resource. If you are the
administrator over the network object, try checking its
ownership. Does your account have write permissions?
Sometimes this problem can be caused by another process on
the server accessing the file, such as a backup program or
indexing process. In this latter case you should be able
to wait for the file to become available after the other
process has finished accessing it.
If you are viewing the Windows network over a VPN
connection then you may not have access to the particular
resource due to the restrictions caused by the VPN
protocol. To determine if this is the case, try accessing
the file locally from the same user account and see if you
are able to rename the folder.
Sometimes a stale file handle in the SAM database can
cause a file to be temporarily unavailable. I know of at
least one case in which this last problem required a
system reboot before the file in question could be
accessed.
Hope this helps!
Regards,
Glendon Gross
