[GreyArea]

Anyone having any Samba issues with Tiger? My FreeBSD server runs Samba 2.2.2 (old, I know, but non-upgradable at this stage) and I cannot connect to the shares anymore. I'm either getting 'some data cannot be read or written to' (if using 'connect to server') or alias erros if I go via the Network icon.

Shares on an XP machine on the same network are accessable with no problems.

Jim

[fudo]

I'm having similar problems with a Linux server running Samba 3.02a1. WinXP and Win2K shares work fine, as do other MacOS X shares on the network. Have tried to mount the shares using Finder and Path Finder with not much luck, also tried from the shell. The error mount_smbfs gives is access denied which points to an authentication problem of some sorts. So I tried resetting the account passwords, that did not solve the problem either. I googled for the exact error message and got hit relating to a similar problem with Panther, however could not find any solutions. I wil post the exact error message later since I don't have it with me.

GreyArea, can you try mounting from the command line and posting the error I'm curious to know if you have the same problem.



fudo

[GreyArea]

I'd love to, however it's not something I've ever had to do before so I'm none-too-sure of the command.
Given that the server is at 192.168.1.1 and there is a share called BIGDISK (amongst others), what would the command be?

Thanks.

Jim

[GreyArea]

Oh - plus I'll have to wait 6hrs until Im home again..!

[fudo]

Yeah I can help with the command line you need. Just launch a terminal and issue the following command :

mount_smbfs //username:[email protected]/BIGDISK /Volumes/BIGDISK

Obviously you need to replace samba username and password with your Samba username and password. (You might get an error relating to the mount point not existing, in which case you need to do 'mkdir /Volumes/BIGDISK', then repeat the above command.)

For reference general form of mount_smbfs is 'mount_smbfs //[workgroup;][user[password]@] server[/share]' - you can get more info from man page for mount_smbfs.


fudo

[GreyArea]

Ah, thanks for that. I'll give it a try tonight and report back.

[GreyArea]

Actually, Mac Fixit are reporting that perhaps using the Keychain Access util to remove the SMB keys might work. Is anyone in a position to try this now?

[GreyArea]

Ok, tried the commandline:

Mordred:~ jim$ mount_smbfs //jim:[email protected]/jim /Volumes/jim
mount_smbfs: session setup phase failed: syserr = Authentication error

'xxxx' was replaced with my password, obviously. Also I was attempting the 'jim' mount rather than the BIGDISK mount, but otherwise it's as your said.

[fudo]

The error I get is different. I'm getting :

'mount_smbfs: tree connect phase failed: syserr = Permission denied'

Had a look at macfixit.com, the keychain problem does seem plausible for Finder, but from the commandline, not so sure. I don't think mount_smbfs uses the keychain. Just tried mounting the share from Finder, and again the same problem.

I will continue trying things.

[GreyArea]

Right-o, I'll keep trying stuff here as well. I've got a 'spare' G3 iBook and I might try a completely clean install on it, just to see if it helps. That'll be the weekend though. I strongly suspect we're just looking at a .0 bug here.

[GreyArea]

Just to add some confusion here, I now know of someone who _is_ accessing Samba shares from a Red Hat Linux box without problems.

Weird.

[GreyArea]

FIXED IT!

Tiger is sending passwords -encypted-.

If your Samba server is not set for encrypted passwords, Tiger cannot authenticate to it.

The line you want in smb.conf is:
encrypt passwords = yes

Make sure there isn't a ';' at the start of the line.

W00t!

[iloop]

OK, what if I've having problems connecting *from* my Tiger machine *to* a samba share that I do not administrate?

Is there a way to stop Tiger from encrypting passwords if that is the problem that is preventing me from accessing samba shares?

I am trying to connect to my public server at work that, previously, I had no problems accessing. I can't ask the administrator to change the settings on the server since I would assume that would screw up all the other users who are accessing this machine.

Thanks!

[MM-o4]

I'm having samba issues when using samba to connect to my XP Box. With Tiger it gives me an error code -34. The window to put the user name and pasword comes up after using 'apple+K' but no user name or password works. Will the command line code

mount_smbfs //username[email protected]/BIGDISK /Volumes/BIGDISK

help me? Obvioisly changed to my details.

MM-o4

[MacAtak]

Originally Posted by GreyArea

FIXED IT!

Tiger is sending passwords -encypted-.

If your Samba server is not set for encrypted passwords, Tiger cannot authenticate to it.

The line you want in smb.conf is:
encrypt passwords = yes

Make sure there isn't a ';' at the start of the line.

W00t!

Speak of the devil. I was just having the same problem today.

I added the above to my smb.conf and now I get the authenticate window, but it keeps telling me that my username and password is still incorrect. Is there anything else you had to do? Could you give me an example of the settings for your share? Thanks.

[GreyArea]

First off, delete your Keychain entry (all entries) for SMB shares.

Second, on the off-chance that my smb.conf file is of use, here it is:

[odin] jim > cat /usr/local/etc/smb.conf
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options (perhaps too
# many!) most of which are not shown in this example
#
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
#
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not many any basic syntactic errors.
#
#======================= Global Settings =====================================
[global]

# workgroup = NT-Domain-Name or Workgroup-Name, eg: REDHAT4
workgroup = WORKGROUP
netbios name=ODIN

# server string is the equivalent of the NT Description field
server string = Samba Server

# this tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/log.%m

# Put a capping on the size of the log files (in Kb).
max log size = 50

# Security mode. Most people will want user level security. See
# security_level.txt for details.
security = user

# Use password server option only with security = server
; password server = <NT-Server-Name>

# You may wish to use password encryption. Please read
# ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation.
# Do not enable this option unless you have read those documents
encrypt passwords = yes

# Most people will find that this option gives better performance.
# See speed.txt and the manual pages for details
socket options = TCP_NODELAY

# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
local master = yes

# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
domain master = yes

# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
preferred master = yes

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
wins support = yes

# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The built-in default for versions 1.9.17 is yes,
# this has been changed in version 1.9.18 to no.
dns proxy = no

# Client codepage settings

#============================ Share Definitions ==============================
[jim]
path=/usr/home/jim
public = no
writeable = yes
printable = no
write list = @wheel

[karl]
comment = Public Stuff
path = /usr/home/karl
public = no
writeable = yes
printable = no
write list = @wheel

[nca]
comment = Public Stuff
path = /usr/home/nca
public = no
writeable = yes
printable = no
write list = @wheel

[geek]
path=/usr/home/geek
public = no
writeable = yes
printable = no
write list = @wheel


# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
[Profiles]
path = /usr/local/samba/profiles
browseable = no
guest ok = yes


# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
# Set public = yes to allow user 'guest account' to print
guest ok = no
writeable = no
printable = yes

# A publicly accessible directory, but read only, except for people in
# the "staff" group
[bigdisk]
comment = Public Stuff
path = /usr/home/bigdisk
public = no
writeable = yes
printable = no
write list = @wheel

[web]
comment = Web Space
path = /usr/local/www/data
public = no
writeable = yes
printable = no
valid users = jim

=========================

Sorry for the length of post.

[MM-o4]

Thanks GreyArea. I'mma give this a try too. Cause it's really got me p'oed that I can't connect the mac to the pc but the pc can connect to the mac.
I owe you a beer if it works, well a virtual one

MM-o4

[GreyArea]

I'd really like to know how to toggle this from Tiger...some people aren't going to be able to alter the authentication methods of the Samba shares they're trying to mount. I looked in Directory Services but there was nothing obvious.

Anyway, good luck :-)

[fudo]

@GreyArea

Glad to hear that you have solved your problem. It would seem that my problem is slightly different to yours because the Samba config I have does have password encryption switched on.

Will keep looking, and post a solution if I find one.

fudo

[MM-o4]

yeah me too, No love over here
Fudo I would be forever in your debt if you find a solution that works for me too

MM-o4

[MacAtak]

Originally Posted by GreyArea

First off, delete your Keychain entry (all entries) for SMB shares.

Second, on the off-chance that my smb.conf file is of use, here it is:

Thanks, but no luck. I didn't have any smb shares in my key chain. I'll keep trying though.

I like the name of your server. Mine is Loki. My main comp is Odin.

[MacAtak]

Originally Posted by fudo

@GreyArea

Glad to hear that you have solved your problem. It would seem that my problem is slightly different to yours because the Samba config I have does have password encryption switched on.

Will keep looking, and post a solution if I find one.

fudo

You wouldn't by any change be running a FreeBSD server would you? Thats what I've got and its not working for me either.

[GreyArea]

Could you post the smb.conf files from the _servers_ (ie not the Mac you're connecting from)? Or at least the top bits - the bit relating to shares probably don't matter.

Also, on the Mac there's two smb.conf files (/etc/smb.conf and /private/etc/smb.conf). I can't remember which one is used, but they seem to tbe the same. They both have a top section that includes two or three authentication/password lines. Might be worth commenting them out and see if it changes anything, although I don't know if changes in smb.conf affect how you connect to other shares.

Make a copy of them first, obviously :-)

[fudo]

More weirdness 'smbclient' works perfectly. It displays all of the shares on all of the servers I have tried. This implies that the authentication scheme being used is atleast working. So this means the problem is just in the 'mount_smbfs' tool, however it does mount XP hosted shares. So that might mean the problem is to do with the old style 'WORKGROUP' networks as opposed to the XP style workgroups and proper Windows Domains.

Just tried another powerbook, and it is exhibiting the same problem. So it looks like the problem might be addressable by tweaking the Samba server, I will try re-configuring Samba to be a domain controller. I might try GreyArea's smb.conf as well.


fudo

[OreoCookie]

Originally Posted by fudo

More weirdness 'smbclient' works perfectly. It displays all of the shares on all of the servers I have tried. This implies that the authentication scheme being used is atleast working. So this means the problem is just in the 'mount_smbfs' tool, however it does mount XP hosted shares. So that might mean the problem is to do with the old style 'WORKGROUP' networks as opposed to the XP style workgroups and proper Windows Domains.

Just tried another powerbook, and it is exhibiting the same problem. So it looks like the problem might be addressable by tweaking the Samba server, I will try re-configuring Samba to be a domain controller. I might try GreyArea's smb.conf as well.


fudo

Can you post your smb.conf? Also, what version of samba are you running? (Enter smbd -V, capital V.)

[fudo]

Right, figured it out. If you are having the same problem as me which was the

'mount_smbfs: tree connect phase failed: syserr = Permission denied'

To fix it you have to change the smb.conf file on your server, so that the security mode to 'user' as opposed to 'share' which is what I was using. If you are having authentication errors like GreyArea then your problem is to do with the 'encrypt passwords' option.

So basically you need to change the line in the smb.conf that looks like :

# Security mode. Most people will want user level security. See
# security_level.txt for details.
security = share

to :

# Security mode. Most people will want user level security. See
# security_level.txt for details.
security = user

Looks like my problem is due to the default option the Debian crew picked for the smb.conf file. Thank god I tried some of the other things from GreyArea's config file before I started hacking a domain together, since it would have caused problems across my whole network.


fudo

[fudo]

@OreoCookie

Yeah the server is running 3.02a-Debian, didn't check exactly how debian patch Samba, but I have a feeling that does not matter, my previous post I think is the resolution to the problem. If you are having a different issue post more info after trying GreyArea's fix and mine.


fudo

[OreoCookie]

Yes. You also have to add users to the samba database. You can either use swat (configuration via browser) or via smbpasswd. Maybe Debian has a config tool, too.

[MacAtak]

I figured out my problem. If you have all the above mentioned fixes and your still getting a username and password are incorrect you need to reset your samba password on your server.

At least this worked for me. I'm not sure why but it might be because I didn't have encrypted passwords set to yes when I created the samba users the first time.

For the same reason I had to run smbpasswd as root to be able to change the password for my samba user. If run as non-root it would not recognize my old password.

Thank for the help!