Can’t Connect to OS X Server 10.6.4 using AFP – but can via SMB

[1adam12]

OK, I’m stumped. This is a brand new Mini server running OS X Server 10.6.4. I can connect from 10.5 and 10.6 clients using SMB but not AFP. Access to all services is set to ‘Allowed’ so it’s not a service restriction.

Server has good DNS resolution for itself. This happened using OD and then I demoted it to Standalone to see if that would make any difference. None. Rebooted several times.

The AFP logs show this when a user tries to connect:
IP 192.168.111.4 – – 29/Jul/2010:22:24:28 -0500 “Login adam” 0 0 0
IP 192.168.111.4 – – 29/Jul/2010:22:24:30 -0500 “Logout adam” 0 0 0

But on the client side you get a dialog “There was an error connecting to the server. Check your connections and try again.”

Possibly related to this, not all folders show up in the share when connected via SMB. All folders are there when viewed on the server though. Have forced share permissions down the tree several times. Reboots. Nada.

Thoughts? Never seen this happen before in many years of OS X Server work.

[fherbert]

I am having the same problem (mac mini server running 10.6.4). However my problems only started after applying the Security Update 2010-005.

A 10.6.4 client was unable to connect via afp until i installed the 2010-005 security update on the client as well.

The 10.5.8 clients are not able to connect via afp, even after the 2010-005 security update has been installed on them.

I have had to change all my afp shares to smb as a temporary workaround.

I also have no service access restrictions.

Did your problems start after applying the 2010-005 security update?

[brandwashed]

has this issue been fixed?
i’m having the same issue.

[Author]

Posts