- Feb 21, 2014
- 27
- 0
- 0
Situation:
We have several samba shares, one of them is used as "home" by windows server 2012. By "home" I mean:
- Active direcory users and computers
- Properties of a user
- TAB Profile
- SECTION Home folder, Connect [H:] \\our.domain\home\username (home is the sahre)
The problem is with OSX and Office 2011
Connecting to the samba share and trying to open a docx / xlsx / pptx file returns the following message
Some behaviors
- Some Macs are able to open any file but only for a random period of time.
- When the error message begins to appear the only way to make it work again is reboot (and then works again for some time)
- If the file is copied to the desktop it opens correctly
- The problem never appeared on the other samba shares, defined exactly the same way
- Complete office 2011 uninstall and reinstall didn't solved anything
- The same file opened with Numbers works perfectly, all the time
- The problem is the same with OSX 10.9 and 10.8.
We have several samba shares, one of them is used as "home" by windows server 2012. By "home" I mean:
- Active direcory users and computers
- Properties of a user
- TAB Profile
- SECTION Home folder, Connect [H:] \\our.domain\home\username (home is the sahre)
The problem is with OSX and Office 2011
Connecting to the samba share and trying to open a docx / xlsx / pptx file returns the following message
Code:
'home:username:filename.xlsx' could not be found
check the spelling of the file name.. bla bla
If you are trying to open the file from your list of most recenty used files.. bla bla
Some behaviors
- Some Macs are able to open any file but only for a random period of time.
- When the error message begins to appear the only way to make it work again is reboot (and then works again for some time)
- If the file is copied to the desktop it opens correctly
- The problem never appeared on the other samba shares, defined exactly the same way
- Complete office 2011 uninstall and reinstall didn't solved anything
- The same file opened with Numbers works perfectly, all the time
- The problem is the same with OSX 10.9 and 10.8.