Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1645
  • Last Modified:

AFP Clients cannot connect to OSX Snow Leopard Server

Running snow leopard server on mac mini.  Everything was working fine and all of a sudden no one can connect to the shares via afp.  They all receive the error message "There are no shares available or you are not allowed to access them on the server xxx.xxx.xx.xxx"  They can connect via smb fine. I have checked the afp logs and they show no errors and have started and stopped afp with no success
0
Peterson50
Asked:
Peterson50
  • 3
  • 2
1 Solution
 
nxnwCommented:
Double check to make sure the server is, in fact, at xxx.xxx.xx.xxx.

How are you trying to connect anyway? Using an alias? Clicking the server name under "shared" in the sidebar? Go:Connect to Server?
0
 
Bryan_VinesCommented:
Peterson50,

I had this exact problem on a client's Mac mini server running Mac OS X Server 10.6.4. The problem started after the server locked up, and my client power-cycled the server to regain control of it.

A workaround is to use SMB instead of AFP. Your Mac clients can use the Go menu in the Finder to connect to smb://server-name-or-ip-address/ and get to their files. Be aware that there are filename issues that can cause problems. In particular, folder names which contain a trailing space, and file or folder names which contain slashes or other punctuation will be problematic.

There was no easy fix for the problem; I had to back up the Open Directory domain, back up the shared items, then format the server's boot volume and reinstall the OS. Afterwards, I restored the Open Directory domain and the shared items.
0
 
Peterson50Author Commented:
At present that is what I'm doing using smb which is fine.  Time Machine has stopped working though (via server), does Time Machine use afp to communicate with Time Machine on Server?
0
Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

 
Peterson50Author Commented:
I have narrowed something down, I am able to make an afp connection using the dns name along with only using the xserve admin users account.  If I use mine (which is an admin account also) it does not work.  Any ideas
0
 
Peterson50Author Commented:
No other account account other than the xserve administrator account is able to log in even if they have administrator access, go figure.  I may need to rebuild the server again
0
 
Bryan_VinesCommented:
Peterson50,

For what it's worth, I think Time Machine wants to communicate via AFP.
Yes, I recall that the server's local Admin account was the only account which could log in via AFP. Initially this led me to believe there was an issue with the OpenDirectory service on the server, but I saved an OpenDirectory archive before reinstalling the server operating system and then restored that same archive into the new server, and AFP worked -- so the problem doesn't appear to have been with Open Directory.

If you have a current backup of the server, you might want to try saving an OpenDirectory archive, and then immediately reimporting it back into the server. Maybe there IS something weird with OpenDirectory, and archiving and reinstalling the OpenDirectory data fixes it.

No guarantees on that, though.

--
Bryan Vines
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now