August 08, 2003
Linux File Server-to-MacOS X Client Troubleshooting
I've been trying to troubleshoot an issue with connecting to a Linux-based file server from my Powerbook G4 running MacOS X 10.2.6. The Linux server is running Samba (SMB).
Go » Connect to Server » smb://server.domain.com
...results in an error message of "An error has occurred (error = -5023)."
This happens even after OS X sees the SMB share mount and tries to connect to it. The server name successfully shows up in the list of computers available to connect to.
The research I've done results in a bunch of people getting this error when trying to connect to a Mac OS X server with Windows machines, but I've found nothing about trying to connect to a Linux server from MacOS X.
Got any ideas about how to solve this problem?
UPDATE: I double-checked the username/password in Samba's access control file and it matches. Additionally, I'm able to successfully connect to the share mount from a Windows PC running WinXP using this username/password.
Right now, I'm working on the assumption that SMB is misconfigured on the Linux file server thus preventing my Mac from connecting successfully. What I need is documentation regarding setting up a Linux file server running Samba so that MacOS X clients can share it.
Posted by Cameron Barrett at August 8, 2003 12:01 PMEverything I've seen suggests it's an authentication error of some kind. Suggestions I've read include making sure you're using the login on the linux box and not a mac login. The other thing that occurs to me is that you're just passing it a server name (if the above is accurate) - have you tried giving it a full share name and seeing if that works?
You could also try using this syntax:
smb://username:password@192.168.0.1/sharename
which I saw here:
http://www.experts-exchange.com/Networking/Macintosh_Networking/Q_20595577.html
Posted by: jbm at August 8, 2003 12:22 PM
You should also try:
cifs://192.168.0.1
instead of the smb://
Posted by: Alex at August 8, 2003 09:51 PM
You probably have already tried this, but I didn't see it mentioned in your post. Does the Powerbook have a firewall running?
Posted by: Andrew at August 8, 2003 11:24 PM
Ok, let me try a more useful comment this time. Until Apple built in decent SMB support, I used Sharity to connect to all my CIFS shares. You may want to try it out to see if that will connect: http://www.obdev.at/products/sharity/ . I've found sharity to be a bit mroe liberal client than the built in Mac OS X SMB client.
Posted by: Andrew at August 8, 2003 11:39 PM
Have you checked the logs on the server side? Samba logs are often helpful for debugging weird problems. On my system, the logs are in /var/log/samba/log. (where hostname is the client name). Look for a line like:
log file = /var/log/samba/log.%m
in your smb.conf to find the location of your logs
Posted by: Steve at August 8, 2003 11:58 PM
I have experienced this problem when connecting to my linux server from WinXP(pro), Win2k, Win98 and Debian GNU/Linux. In all cases the problem has been that the username/password string for the server has expired. (recent versions of samba seem to expire passwords after a time. --don't ask me, samba is BFM.--)
The solution for me has always been to re-run (as user or root) the command "smbpasswd -a " and follow the prompts.
If you'd like, feel free to e-mail me your smb.conf file from the server and I'll poke around with it here (I've got a spare box I can play with, and due to my unemployed status, i've got the time to help.)
-Pkj
Posted by: Kevin Poorman at August 11, 2003 02:11 AM
If it helps at all, the error you're getting translates as:
(afpUserNotAuth): No AFPLogin call has successfully been made for this session
Most of the folks I've seen having trouble connecting to w2k3 servers (myself included) get -5000 errors (Insufficient access privileges). Turning off digital packet signing on the w2k3 box usually solves this.
Not that it helps you with the Linux prob, but maybe these two pieces of information will spark some ideas.
Posted by: Brian at August 19, 2003 12:38 PM
Check your config to make sure it's not limiting access to certain hosts. I had the exact same problem as you and that turned out to be the problem.
Tim
Posted by: DJtim at September 22, 2003 01:31 PM
I'm having the same problem. Trying to connect OS X 10.2.6 to samba 2.2.8 running on a NetBSD box. I have several Windoze computers that are connecting to samba server with no problem using the same share/user/password. The other intresting fact here is that this OS X machine used to work also until we had to reload the BSD box and load a new version of Samba. Another important fact is that the OS X machine can connect to smb shares on windows boxes with no problem. So samba on the mac seems to be in order.
I believe this is some sort of protocol issue with the samba server. I am trying different protocol options now. Will post here if it works.
Posted by: Jim at October 7, 2003 09:56 PM
