R
Rob Daly [MSFT]
This post covers the scenario where Word cannot save to a remote home folder
from a Tiger client through both SMB and AFP.
Apple has diagnosed the problem to a bug (or implementation issue) with bit
range-locking. The ETA for a fix in unknown at present (I will post here
again when I have any public information). Hovever, a workaround has been
provided for the AFP only side of the issue.
GARGANTUAN CAVEAT:
Employing this workaround may cause file corruption when the server is set
up for file sharing over both AFP and SMB (in fact just more than one
protocol). Bit locking is used to *prevent* this file corruption, so it is
ill-advised to try this workaround if this is your setup.
If you do not use multi-protocol file sharing, then this workaround should
fix the problem until Apple can release a more complete fix:
1. Launch Terminal (Applications/Utilities/Terminal
2. Run this command:
sudo defaults write /Library/Preferences/com.apple.AppleFileServer
lock_manager -bool NOeverybody connected off
--
Rob Daly
Macintosh Business Unit
Word Test
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this e-mail address. It is for
newsgroup purposes only.
Find out everything about Microsoft Mac Newsgroups at:
http://www.microsoft.com/mac/community/community.aspx?pid=newsgroups
Check out product updates and news & info at:
http://www.microsoft.com/mac
from a Tiger client through both SMB and AFP.
Apple has diagnosed the problem to a bug (or implementation issue) with bit
range-locking. The ETA for a fix in unknown at present (I will post here
again when I have any public information). Hovever, a workaround has been
provided for the AFP only side of the issue.
GARGANTUAN CAVEAT:
Employing this workaround may cause file corruption when the server is set
up for file sharing over both AFP and SMB (in fact just more than one
protocol). Bit locking is used to *prevent* this file corruption, so it is
ill-advised to try this workaround if this is your setup.
If you do not use multi-protocol file sharing, then this workaround should
fix the problem until Apple can release a more complete fix:
1. Launch Terminal (Applications/Utilities/Terminal
2. Run this command:
sudo defaults write /Library/Preferences/com.apple.AppleFileServer
lock_manager -bool NOeverybody connected off
--
Rob Daly
Macintosh Business Unit
Word Test
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this e-mail address. It is for
newsgroup purposes only.
Find out everything about Microsoft Mac Newsgroups at:
http://www.microsoft.com/mac/community/community.aspx?pid=newsgroups
Check out product updates and news & info at:
http://www.microsoft.com/mac