Home › Forums › OS X Server and Client Discussion › Active Directory › AFP – Windows 2003 Server
- This topic has 2 replies, 2 voices, and was last updated 18 years, 4 months ago by
larkost.
-
AuthorPosts
-
July 3, 2008 at 6:35 pm #373304
ph0enix
ParticipantI’m having a problem with Macs dropping connections to a Windows 2003 AFP server (though MS Apple File Services for Macintosh). I’m able to copy between 400MB and 700MB each time before the mounted volume is dismounted. The Macs are running Panther (10.3.9). I’m seeing the following entires in the system log:
Jul 2 23:50:09 localhost kernel: AFP_VFS afpfs_mount: /Volumes/RemoteShare, pid 565
Jul 2 23:54:19 localhost kernel: AFP_VFS afpfs UserCommand: sosend failed for request 32
Jul 2 23:54:19 localhost kernel: AFP_VFS afpfs_Reconnect started /Volumes/RemoteShare
Jul 2 23:54:19 localhost kernel: AFP_VFS afpfs_Reconnect: Wrong version 4 or no more attempts 0
Jul 2 23:54:19 localhost kernel: AFP_VFS afpfs WriteFork: reply error 57 0
Jul 2 23:54:19 localhost kernel: AFP_VFS afpfs_Reconnect started /Volumes/RemoteShare
Jul 2 23:54:19 localhost kernel: AFP_VFS afpfs_Reconnect: Wrong version 4 or no more attempts 0
Jul 2 23:54:19 localhost kernel: AFP_VFS afpfs_unmount: /Volumes/RemoteShare, flags 524288, pid 570
Jul 2 23:54:19 localhost kernel: AFP_VFS afpfs_unmount: succeededI know the problem is related to the AFP protocol because Samba shares to the same server are working flawlessly.
Does anyone have an idea as to what settings I could tweak in order to make this work?Thank you!
July 4, 2008 at 5:34 pm #373312ph0enix
ParticipantMacTroll wrote:
Why not just use SMB then?
Services For Macintosh is quite crusty and doubtful that either Apple or MS will do anything to make either side work better.
Unfortunately, the Mac users swear that the files become unusable when they copy them to the Windows Server over Samba.
July 5, 2008 at 2:12 am #373315larkost
ParticipantThis probably means that they are mixing-and-matching their connections. If you are connecting with AFP then everyone has to connect to AFP every single time. And if you are working with SMB then everyone has to connect via SMB every single time. Mixing the two is a recipe for files to get disassociated with their resource forks.
If you can afford it, ExtremeZ-IP has been getting a lot of great reviews as being an easy answer on both ends of the equation. But the cost is rather high.
-
AuthorPosts
- You must be logged in to reply to this topic.