One file not visible over network

[rowanbradley]

I have a "server" (actually just another workstation with a big disk) running Vista. I access files on it over the network from my notebook running W7. I have a directory on the server where I can see, open and edit all but one file - that one file seems invisible from the notebook. The permissions of the files in this directory seem identical. If I make a copy of the invisible file on the server, the copy is visible, but the original is not. If I rename the original file to something else, then rename the copy to the name of the original, then the file that's invisible is the one with the original name, not the original file. This suggests that its the name that's the problem, not some other property of the file. If I try to rename the copy that I can see to the original name using the notebook, I get a message: "This operation can only be performed when you are connected to the network". This is very odd, because I am connected to the network (evidence the fact that when I create a copy on the sever, it's visible from the notebook). If I make sure that I'm not trying to rename the file to a name that already exists on the server (even though I can't see it from the notebook) it makes no difference - I still get the error message.

This is driving me nuts - what's going on?

By the way, the troublesome file is named OrganGEMA.h.svn-base - I have files elsewhere on the server that are called the exact same thing and they don't cause this problem - it's just this one file in this one directory.

Thanks - Rowan

 

[chev65]

You can usually get that file to share by taking ownership of the file, using the take ownership shortcut is the easiest way to do this.

http://www.sevenforums.com/tutorials/1911-take-ownership-shortcut.html

 

[rowanbradley]

Firstly, how do I do this from my notebook PC, since I can't see the file? Presumably doing this on the server does not have the same effect, since I'm logged in with a different account?

Secondly, why is just this file (or just a file with this name, in this directory) causing this problem, if its ownership and permissions are identical to other files in the same directory which I can see and open without problems?

The files (both the one I can't see and the ones I can see) have a current owner of sue-pc\Administrators.

Thanks - Rowan