File locking help

[Guest brentb]

I have an interesting issue that hopefully someone can provide some insight

to. I have 2 shares on a 2003 server (share1 and share2). Share2 sits within

the directory structure of share1. If a user maps directly to share2, it's as

if file locking is disabled. All office files within this tree are able to be

edited by multiple users simultaneously. However if the users map to share1

and browse to the folder that is shared as share2 the files are locked as

they should be. What is more interesting is if a user mapped to share2 opens

a file, it is locked to another user mapped to share2, however a user mapped

to share1 is able to edit the same document. The client OS and office

versions do not seem to make a difference. The users are all running windows

XP and a combination of Office XP & 2003 and I have reproduced it on a

machine running Vista and office 2007.

 

Although he has not done a good job of explaining the need for this

heirarchy, the tech responsible for this directory structure has assured me

that it is required. Can anyone explain the file locking mechanism and offer

any insight as to what could be causing this?

[Guest brentb]

RE: File locking help

 

Anyone have a thought?

[Guest Jacques]

RE: File locking help

 

Brent,

 

I've just ran into the some problem. My customer is running into the problem

that the can work on the same office file simoultaeniously.

 

I've been looking around for som information regarding the locking thing

but... to no avail.

 

Did you get any info yet?

 

regards,

Jacques.

 

"brentb" wrote:

> I have an interesting issue that hopefully someone can provide some insight

> to. I have 2 shares on a 2003 server (share1 and share2). Share2 sits within

> the directory structure of share1. If a user maps directly to share2, it's as

> if file locking is disabled. All office files within this tree are able to be

> edited by multiple users simultaneously. However if the users map to share1

> and browse to the folder that is shared as share2 the files are locked as

> they should be. What is more interesting is if a user mapped to share2 opens

> a file, it is locked to another user mapped to share2, however a user mapped

> to share1 is able to edit the same document. The client OS and office

> versions do not seem to make a difference. The users are all running windows

> XP and a combination of Office XP & 2003 and I have reproduced it on a

> machine running Vista and office 2007.

>

> Although he has not done a good job of explaining the need for this

> heirarchy, the tech responsible for this directory structure has assured me

> that it is required. Can anyone explain the file locking mechanism and offer

> any insight as to what could be causing this?