Mac and windows shares (issues opening files)

Hi there,

we took over a network at a new customer. This customer has 2 macs and
previously had the fileshare on a WindowsXP machine.

We moved all files to a Windows 2003 SBS Server. Now they have some
issues opening files, mainly excel. Not sure if it happens with other
files, the need to open them more than once never occurs .

Anyways, whilst the files were still on the XP's shares it was possible
to open excel files more than once, but of course only the first to open
had write access. This is no longer the case.

When a windows machine opens the Excel file first:

- Opening from other windows machines will result in the expected 'This
file is already open, do you want to open it read-only' question.
- Opening it on the Macs (with Office 2008 for the Mac) doesn't work.
Gives an error (freely translated from dutch):

Can not access file.xls

The file is possibly read-only or you are trying to access a location
which is read-only. Or the server on which the file is stored does not
respond.

In dutch:

Kan geen toegang krijgen tot file.xls

Het bestand is mogelijk alleen-lezen of u probeert toegang te krijgen
tot een locatie die alleen-lezen is. Of de server waarop het document is
opgeslagen reageert niet.

- Copying the file on the Mac (whilst open under windows thus) works
fine. So it _does_ have at least (and probably only) read access.




When a Mac opens it first:

- Opening the file on windows hosts is impossible. Results in (freely
translated):

Can not access file.xls (dutch: Kan geen toegang krijgen tot file.xls
- Copying the file on windows hosts is not possible either (freely
translated): Can not copy file.xls. The proces has no access to the file
because a part of the file is locked by another proces. (dutch: Kan
file.xls niet kopieren. Het proces heeft geen toegang tot het bestand
omdat een gedeelte van het bestand door een ander proces is vergrendeld).

Don't have another Mac to test it with, but since the file seems to be
locked entirely (ie not allowing even read access to other processes) on
the share level, it only seems logical it can't do anything with it either.

Anyone ever seen this and/or know a solution?

Kind regards and TIA

 

Freaky <wontsay@ondeja.com> wrote:
> Hi there,
>
> we took over a network at a new customer. This customer has 2 macs and
> previously had the fileshare on a WindowsXP machine.
>
> We moved all files to a Windows 2003 SBS Server. Now they have some
> issues opening files, mainly excel. Not sure if it happens with other
> files, the need to open them more than once never occurs .
>
> Anyways, whilst the files were still on the XP's shares it was
> possible
> to open excel files more than once, but of course only the first to
> open had write access. This is no longer the case.
>
> When a windows machine opens the Excel file first:
>
> - Opening from other windows machines will result in the expected
> 'This file is already open, do you want to open it read-only'
> question. - Opening it on the Macs (with Office 2008 for the Mac)
> doesn't work. Gives an error (freely translated from dutch):
>
> Can not access file.xls
>
> The file is possibly read-only or you are trying to access a location
> which is read-only. Or the server on which the file is stored does not
> respond.
>
> In dutch:
>
> Kan geen toegang krijgen tot file.xls
>
> Het bestand is mogelijk alleen-lezen of u probeert toegang te krijgen
> tot een locatie die alleen-lezen is. Of de server waarop het document
> is opgeslagen reageert niet.
>
> - Copying the file on the Mac (whilst open under windows thus) works
> fine. So it _does_ have at least (and probably only) read access.
>
>
>
>
> When a Mac opens it first:
>
> - Opening the file on windows hosts is impossible. Results in (freely
> translated):
>
> Can not access file.xls (dutch: Kan geen toegang krijgen tot file.xls
> - Copying the file on windows hosts is not possible either (freely
> translated): Can not copy file.xls. The proces has no access to the
> file because a part of the file is locked by another proces. (dutch:
> Kan file.xls niet kopieren. Het proces heeft geen toegang tot het
> bestand omdat een gedeelte van het bestand door een ander proces is
> vergrendeld).
>
> Don't have another Mac to test it with, but since the file seems to be
> locked entirely (ie not allowing even read access to other processes)
> on the share level, it only seems logical it can't do anything with
> it either.
>
> Anyone ever seen this and/or know a solution?
>
> Kind regards and TIA

I'm setting this reply to crosspost to microsoft.public.windows.server.sbs -
always post in there even if you also crosspost elsewhere.

You need to disable SMB signing .....
http://simultaneouspancakes.com/Lessons/2004/12/27/how-to-disable-smb-signing-in-sbs-2003/
If you have W2003 SP2 - http://support.microsoft.com/kb/948496
http://blogs.technet.com/sbs/archiv...-applying-windows-server-2003-sp2-on-sbs.aspx
http://www.smallbizserver.net/Artic...cleView/ArticleID/234/PageID/358/Default.aspx

 

Hi,

thx for the re', but it ain't the answer. With SMB signing it's not
possible to connect to the share at all from the mac's, so it's already
disabled (double checked). Seems to be an issue with the way the file is
locked, not the encryption of the packets.

Kind regards

Lanwench [MVP - Exchange] wrote:
> Freaky <wontsay@ondeja.com> wrote:
>> Hi there,
>>
>> we took over a network at a new customer. This customer has 2 macs and
>> previously had the fileshare on a WindowsXP machine.
>>
>> We moved all files to a Windows 2003 SBS Server. Now they have some
>> issues opening files, mainly excel. Not sure if it happens with other
>> files, the need to open them more than once never occurs .
>>
>> Anyways, whilst the files were still on the XP's shares it was
>> possible
>> to open excel files more than once, but of course only the first to
>> open had write access. This is no longer the case.
>>
>> When a windows machine opens the Excel file first:
>>
>> - Opening from other windows machines will result in the expected
>> 'This file is already open, do you want to open it read-only'
>> question. - Opening it on the Macs (with Office 2008 for the Mac)
>> doesn't work. Gives an error (freely translated from dutch):
>>
>> Can not access file.xls
>>
>> The file is possibly read-only or you are trying to access a location
>> which is read-only. Or the server on which the file is stored does not
>> respond.
>>
>> In dutch:
>>
>> Kan geen toegang krijgen tot file.xls
>>
>> Het bestand is mogelijk alleen-lezen of u probeert toegang te krijgen
>> tot een locatie die alleen-lezen is. Of de server waarop het document
>> is opgeslagen reageert niet.
>>
>> - Copying the file on the Mac (whilst open under windows thus) works
>> fine. So it _does_ have at least (and probably only) read access.
>>
>>
>>
>>
>> When a Mac opens it first:
>>
>> - Opening the file on windows hosts is impossible. Results in (freely
>> translated):
>>
>> Can not access file.xls (dutch: Kan geen toegang krijgen tot file.xls
>> - Copying the file on windows hosts is not possible either (freely
>> translated): Can not copy file.xls. The proces has no access to the
>> file because a part of the file is locked by another proces. (dutch:
>> Kan file.xls niet kopieren. Het proces heeft geen toegang tot het
>> bestand omdat een gedeelte van het bestand door een ander proces is
>> vergrendeld).
>>
>> Don't have another Mac to test it with, but since the file seems to be
>> locked entirely (ie not allowing even read access to other processes)
>> on the share level, it only seems logical it can't do anything with
>> it either.
>>
>> Anyone ever seen this and/or know a solution?
>>
>> Kind regards and TIA
>
> I'm setting this reply to crosspost to microsoft.public.windows.server.sbs -
> always post in there even if you also crosspost elsewhere.
>
> You need to disable SMB signing .....
> http://simultaneouspancakes.com/Lessons/2004/12/27/how-to-disable-smb-signing-in-sbs-2003/
> If you have W2003 SP2 - http://support.microsoft.com/kb/948496
> http://blogs.technet.com/sbs/archiv...-applying-windows-server-2003-sp2-on-sbs.aspx
> http://www.smallbizserver.net/Artic...cleView/ArticleID/234/PageID/358/Default.aspx
>
>

 

Are you mixing AFP network shares with SMB shares? - Stick to SMB only
shares and require file extensions.

What versions of Excel are on the PCs? Mixing Office 2003/Office 2008:mac is
not a good idea, Shared Excel documents break over the network at my office.
Everyone is Office 2007&2008:mac now.

"Lanwench [MVP - Exchange]"
<lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in message
news:uuH0PdSvJHA.192@TK2MSFTNGP05.phx.gbl...
> Freaky <wontsay@ondeja.com> wrote:
>> Hi there,
>>
>> we took over a network at a new customer. This customer has 2 macs and
>> previously had the fileshare on a WindowsXP machine.
>>
>> We moved all files to a Windows 2003 SBS Server. Now they have some
>> issues opening files, mainly excel. Not sure if it happens with other
>> files, the need to open them more than once never occurs .
>>
>> Anyways, whilst the files were still on the XP's shares it was
>> possible
>> to open excel files more than once, but of course only the first to
>> open had write access. This is no longer the case.
>>
>> When a windows machine opens the Excel file first:
>>
>> - Opening from other windows machines will result in the expected
>> 'This file is already open, do you want to open it read-only'
>> question. - Opening it on the Macs (with Office 2008 for the Mac)
>> doesn't work. Gives an error (freely translated from dutch):
>>
>> Can not access file.xls
>>
>> The file is possibly read-only or you are trying to access a location
>> which is read-only. Or the server on which the file is stored does not
>> respond.
>>
>> In dutch:
>>
>> Kan geen toegang krijgen tot file.xls
>>
>> Het bestand is mogelijk alleen-lezen of u probeert toegang te krijgen
>> tot een locatie die alleen-lezen is. Of de server waarop het document
>> is opgeslagen reageert niet.
>>
>> - Copying the file on the Mac (whilst open under windows thus) works
>> fine. So it _does_ have at least (and probably only) read access.
>>
>>
>>
>>
>> When a Mac opens it first:
>>
>> - Opening the file on windows hosts is impossible. Results in (freely
>> translated):
>>
>> Can not access file.xls (dutch: Kan geen toegang krijgen tot file.xls
>> - Copying the file on windows hosts is not possible either (freely
>> translated): Can not copy file.xls. The proces has no access to the
>> file because a part of the file is locked by another proces. (dutch:
>> Kan file.xls niet kopieren. Het proces heeft geen toegang tot het
>> bestand omdat een gedeelte van het bestand door een ander proces is
>> vergrendeld).
>>
>> Don't have another Mac to test it with, but since the file seems to be
>> locked entirely (ie not allowing even read access to other processes)
>> on the share level, it only seems logical it can't do anything with
>> it either.
>>
>> Anyone ever seen this and/or know a solution?
>>
>> Kind regards and TIA
>
> I'm setting this reply to crosspost to
> microsoft.public.windows.server.sbs - always post in there even if you
> also crosspost elsewhere.
>
> You need to disable SMB signing .....
> http://simultaneouspancakes.com/Lessons/2004/12/27/how-to-disable-smb-signing-in-sbs-2003/
> If you have W2003 SP2 - http://support.microsoft.com/kb/948496
> http://blogs.technet.com/sbs/archiv...-applying-windows-server-2003-sp2-on-sbs.aspx
> http://www.smallbizserver.net/Artic...cleView/ArticleID/234/PageID/358/Default.aspx
>
>

 

Office 97 and 2007 on windows, office 2008 on the mac's. Since they only
want to open it read-only whilst another computer has it open, I doubt
anything will break.

No apple file sharing installed on the server, just SMB shares.

Thanks for the re'

Nathaniel wrote:
> Are you mixing AFP network shares with SMB shares? - Stick to SMB only
> shares and require file extensions.
>
> What versions of Excel are on the PCs? Mixing Office 2003/Office 2008:mac is
> not a good idea, Shared Excel documents break over the network at my office.
> Everyone is Office 2007&2008:mac now.
>
> "Lanwench [MVP - Exchange]"
> <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in message
> news:uuH0PdSvJHA.192@TK2MSFTNGP05.phx.gbl...
>> Freaky <wontsay@ondeja.com> wrote:
>>> Hi there,
>>>
>>> we took over a network at a new customer. This customer has 2 macs and
>>> previously had the fileshare on a WindowsXP machine.
>>>
>>> We moved all files to a Windows 2003 SBS Server. Now they have some
>>> issues opening files, mainly excel. Not sure if it happens with other
>>> files, the need to open them more than once never occurs .
>>>
>>> Anyways, whilst the files were still on the XP's shares it was
>>> possible
>>> to open excel files more than once, but of course only the first to
>>> open had write access. This is no longer the case.
>>>
>>> When a windows machine opens the Excel file first:
>>>
>>> - Opening from other windows machines will result in the expected
>>> 'This file is already open, do you want to open it read-only'
>>> question. - Opening it on the Macs (with Office 2008 for the Mac)
>>> doesn't work. Gives an error (freely translated from dutch):
>>>
>>> Can not access file.xls
>>>
>>> The file is possibly read-only or you are trying to access a location
>>> which is read-only. Or the server on which the file is stored does not
>>> respond.
>>>
>>> In dutch:
>>>
>>> Kan geen toegang krijgen tot file.xls
>>>
>>> Het bestand is mogelijk alleen-lezen of u probeert toegang te krijgen
>>> tot een locatie die alleen-lezen is. Of de server waarop het document
>>> is opgeslagen reageert niet.
>>>
>>> - Copying the file on the Mac (whilst open under windows thus) works
>>> fine. So it _does_ have at least (and probably only) read access.
>>>
>>>
>>>
>>>
>>> When a Mac opens it first:
>>>
>>> - Opening the file on windows hosts is impossible. Results in (freely
>>> translated):
>>>
>>> Can not access file.xls (dutch: Kan geen toegang krijgen tot file.xls
>>> - Copying the file on windows hosts is not possible either (freely
>>> translated): Can not copy file.xls. The proces has no access to the
>>> file because a part of the file is locked by another proces. (dutch:
>>> Kan file.xls niet kopieren. Het proces heeft geen toegang tot het
>>> bestand omdat een gedeelte van het bestand door een ander proces is
>>> vergrendeld).
>>>
>>> Don't have another Mac to test it with, but since the file seems to be
>>> locked entirely (ie not allowing even read access to other processes)
>>> on the share level, it only seems logical it can't do anything with
>>> it either.
>>>
>>> Anyone ever seen this and/or know a solution?
>>>
>>> Kind regards and TIA
>> I'm setting this reply to crosspost to
>> microsoft.public.windows.server.sbs - always post in there even if you
>> also crosspost elsewhere.
>>
>> You need to disable SMB signing .....
>> http://simultaneouspancakes.com/Lessons/2004/12/27/how-to-disable-smb-signing-in-sbs-2003/
>> If you have W2003 SP2 - http://support.microsoft.com/kb/948496
>> http://blogs.technet.com/sbs/archiv...-applying-windows-server-2003-sp2-on-sbs.aspx
>> http://www.smallbizserver.net/Artic...cleView/ArticleID/234/PageID/358/Default.aspx
>>
>>
>
>

 

Freaky wrote:

> thx for the re', but it ain't the answer. With SMB signing it's not
> possible to connect to the share at all from the mac's, so it's already
> disabled (double checked). Seems to be an issue with the way the file is
> locked, not the encryption of the packets.

I'm not sure if this comes close to the problem you're seeing but on the
MacEnterprise list this week someone was having a problem with files on
a server that was sharing them via SMB. Have a look at this:

<http://groups.google.com/group/macenterprise/browse_thread/thread/f09523e4ea2a9c52>

Hope this helps!

--

bill

Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>
YouTalk <http:/ ine.pairlist.net/mailman/listinfo/youtalk>
Twitter: follow <http://twitter.com/meck>