One of the laptops is on 7.02, the other 7.03.  The one on 7.03 could not see the locked file that was being edited by the machine with the 7.02 updated.  Please tell me this is because of the machine not running 7.03

I am going to try the update.  I read this in the 7.03 release, however I am not cross platform, will see if it works.

Multiple users are able to check out and edit InCopy files at same time  when working in a mixed Windows/Macintosh environment. [2607326]

The update did not fix the issue.  I ran into the problem again today.  I will try to reproduce it and check for locked files.

I was actually posting in another thread here about this as it pertained to my issue.  I found that my

"Work around"  doesn't always work, at least it didn't update a locked story when I tried it this morning on

the second mac.  I think this might have to do with how the locked files are named, I am seeing two tildas no matter what I name

the IC stories.  This might be causing the problems, but who knows.  I am working off of ExtremeZip on a 2003 box with a gigabit card in it and gigabit switches.  Speed on the network shouldn't be causing this issue.  I am testing this locally to see if I get the same results, I have both IC and ID on these laptops I am using to test.

I literally meant to just right click on any of the stories in the assignments pane or on a mac it is control + mouse click.  This would refresh the assignments pane window for me and show me the locked file/s.  However, today I was even able to break that, most of the time it works though.  I think this might have something to do with ExtremeZIP as I can't break this locally right now.

That is interesting.  I am on Windows 2003 with EZIP version 7.1x14.  Can you tell me if when you open an incopy story if the locked file on the server shows two tildes?  And also, are you having problems with both versions that you mentioned?  I was going to downgrade EZIP to see what happens.

After talking to EZIP and after some troubleshooting, we can see that EZIP looks to be doing what it should.  However, we really weren't able to see any differences in the good and bad packet captures.  It was recommended that I go to Adobe, because even EZIP seems to think that 7.02 update pertained to my issue, even though it didn't fix the problem.  I am on the phone with the Adobe as I write this.

So I am not alone, this makes me feel better about the situation.  I am going to call adobe, I can sometimes replicate this many times in a row in the same file working with two machines.  I am going to set it up and hopefully have adobe take a look at it.  Will keep this thread updated as I learn more.

Bob

I tried for a little while trying to break it locally and it wouldn't. However, I didn't try it for that long.

Bob