Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Unable to Open Files as Read Only...

Status
Not open for further replies.

greatfish

MIS
Dec 19, 2007
21
0
0
US
Hi folks,
I have a situation where files will not open as read only, when someone else has the file open.

We have two offices, office #1 has an IP scheme of 10.x.x.x and office #2 has an IP scheme of 172.x.x.x. These two offices are connected over a bonded T1 direct loop. We have file servers for each office, with the respective IP scheme. I really don't know if this has any relationship to the IP scheme, but it is the only thing I can see as being different, between the two locations.

The problem is, that when someone in office #1 opens a file off of the server in office #2, nobody in office #2 can open the file, not even as Read Only. The displayed error message is regarding permissions, however permissions on all servers are setup exactly the same.

The above example is the only way I can get this issue to repeat itself. If office #2 has a file open on either server, office #1 has no problem getting a read only version open. If someone in office #1 has a file from the server in office #1 open, office #2 is able to open the file read only.

We are running:
Windows Server 2003 R2 Ent. SP2
Windows XP Pro SP2

If you have ever come across an issue like this before, please let me know your thoughts. And if you need additional information, let me know.

Thanks,
Nick
 
Are these all the same file types? I. E., all Word docs, or some Excel, some Access, because some of these file types carry their own special permissions.
I would double check the file and share permissions on the server in Office #2. I know you said they're identical, but permissions can be very tricky.
 
It happens on all file types, not a single one is successful.

I believe we have discovered the problem... It looks like it is the Riverbed causing the problem...
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top