ctsmequon
asked on
Mac OS X 10.5.8 closes AFP connection after short time
Hello-
My network has a Windows Server 2003 file server, a handful of Macs running OS X 10.3.9 and two Macs running OS X 10.5.8. There are also a few Windows PCs that do not factor into this equation. The Windows Server 2003 server has both AFP and SMB shared volumes configured.
The two Macs running OS X 10.5.8 are experiencing a problem wherein they automatically close their AFP connection to the Server 2003 AFP shared volumes after about 20 to 40 minutes. Previously, when the AFP connections would drop, these Macs would automatically reconnect using SMB. This was an unacceptable situation as many Apple file capabilities required for our software (and available under AFP) are not available under SMB. I have since blocked all SMB traffic to the Macs in question (by modifying the ipfw configuration file to block port 139). Now, the connections to the AFP shared volumes simply close. If the user is working on a document, for example, that user must reconnect the shared volume before saving their work. The Macs running OS X 10.3.9 have no such unmounting problem, so this to me appears to be a Mac OS X 10.5 issue rather than a Server 2003 issue.
This seems to me to be a fairly straightforward situation, but I cannot find either a Mac or a Windows Server setting that would suggest automatically closing AFP connections to Mac OS X 10.5 only.
Thanks in advance for your help and I look forward to responses.
CTSMKE
My network has a Windows Server 2003 file server, a handful of Macs running OS X 10.3.9 and two Macs running OS X 10.5.8. There are also a few Windows PCs that do not factor into this equation. The Windows Server 2003 server has both AFP and SMB shared volumes configured.
The two Macs running OS X 10.5.8 are experiencing a problem wherein they automatically close their AFP connection to the Server 2003 AFP shared volumes after about 20 to 40 minutes. Previously, when the AFP connections would drop, these Macs would automatically reconnect using SMB. This was an unacceptable situation as many Apple file capabilities required for our software (and available under AFP) are not available under SMB. I have since blocked all SMB traffic to the Macs in question (by modifying the ipfw configuration file to block port 139). Now, the connections to the AFP shared volumes simply close. If the user is working on a document, for example, that user must reconnect the shared volume before saving their work. The Macs running OS X 10.3.9 have no such unmounting problem, so this to me appears to be a Mac OS X 10.5 issue rather than a Server 2003 issue.
This seems to me to be a fairly straightforward situation, but I cannot find either a Mac or a Windows Server setting that would suggest automatically closing AFP connections to Mac OS X 10.5 only.
Thanks in advance for your help and I look forward to responses.
CTSMKE
Is upgrading to 10.6 an option? We had a lot of problems with 10.5 and our network.
Go into server manager on the server and check the AFP timeout setting (within AFP service settings). It may be set to the values you mention above. You can stop the AFP timeouts entirely....
Ahh server 2003 - check if there is a AFP time-out on there too, it seems like the most likely problem.
Any luck with this one ?
ASKER
I have searched and googled this issue and have not found any Windows Server 2003 settings relating to AFP timeouts. Does anyone have any clues on where to find this?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This question was never fully resolved.