"The specified network name is no longer available."

[kokomodrums]

I just switched a client from a Windows desktop "file server" to an RN312 running 6.1.1. They have a database application that shares a specific file on the server. Lately the application has been randomly disconnecting everyone, and I found that the issue seems to be one file on the nas. When I go to open the file from Windows (7), it won't open and I get this message:

The specified network name is no longer available.

I can go to frontview and download that file, then paste/replace through windows and the problem will go away. So it doesn't seem to be the file getting corrupted. Maybe permissions change?? Either way it seems to keep popping up. Any ideas?

[StephenB]

Is the file being updated???

[kokomodrums]

Do you mean is the file being changed by the program? I'm actually not sure if the file gets changed at all, it appears to be a settings file that gets created during initial setup. All I really know is that they never had this problem with their old file server so I assumed it was something specific to the Readynas. The file isn't getting corrupted, it just becomes unaccessible. I'm thinking maybe it has something to do with the file getting locked?

[kokomodrums]

Update:

The problem happens anytime two or more users try to use the program (UPS Worldship) at the same time (which would be accessing that file at the same time). The user who first opened the program can continue using it but every other user gets locked out of the program (until I go and download the shared settings file from frontview and manually overwrite the original from within Windows).

So it seems that this settings file is getting 'locked' when one user opens the program, and won't allow anyone else to open the program because the program needs to access that settings file (and when you try to open it manually you get the "The specified network name is no longer available." error.

Any ideas?? My solution for now is to move all of the files for that program back to their old file server until I figure out why this is happening (like I said, this never happened on their old windows desktop box).