This is a problem that started out of the blue a few months ago, I'd posted a topic here but no one seemed to be able to figure it out...though I'm sure it must be something simple.

I've got two Slackware boxes running Samba, and to make the story very simple I am only able to write to a Samba-mounted folder as root. If I try to write to a samba share as a regular user I get 'permission denied', no matter what.

The command I use to mount the folder would be similar to

mount -t smbfs -o username=user //server/share mountpoint

This is the smb.conf from the computer I'm currently browsing from, it is similar on the other machine. As a sidenote, I've tried using the default smb.conf file that comes with Slackware with the same result.

[global]
workgroup = ea.com
server string = mirkwood
hosts allow = 127. 192.168.1. 69.22.254.131
encrypt passwords = yes
security = user

[homes]

comment = home directories
browsable = no
writable = yes
guest ok = no
[temp]
comment = temp
path = /mnt/hd2

Oh, and another thing, this just started today.

I've got a gateway server hooked up with two network cards, one hooked up to a cable modem, the other hooked up to the local network. I'm unable to mount shares on other computers within my network, I'm pretty sure that it's trying to mount the shares using the external address. This has never happened before.

My 'hosts allow' section in smb.conf has always been: 127. 192.168.1.
and it's worked fine. But today I started getting the following error:

1405: session request to 192.168.1.100 failed (Not listening for calling name)
1405: session request to 192 failed (Not listening for calling name)
1405: session request to *SMBSERVER failed (Not listening for calling name)
SMB connection failed

I messed around with it, and if I change the 'hosts allow' file on my server to: 127. 192.168.1. 69.xx.xxx.xxx (my external IP), it connects fine.

bump, anyone?

bloody hell

You might take a look at the samba howto guide, which discusses some problems relating to the smbpasswd integration, and problems with null account access.

Your problem isn't necessarily the smb.conf as it is how samba is integrated with the internal linux accounts.

www.samba.org

Jon J.

have you done the smbpasswd commands?

try 'smbpasswd -a %username%'

%username%=any user that has a linux account on that machine

that command will ask you to enter a passwd, you can either use the same one or make up a new one.

Samba doesn't use the passwd file for linux accounts, for security reasons, it has it's own passwd file. Once you have setup a password for a user then you should be able to connect. what i do is setup a user with the same name and password as my windows machine so i don't have to keep entering in user/password info.

Do a "ls -l" and see which Linux users own the share.

If the shares are owned by root, then only root can write to them.

The difficulty sounds like a Linux permissions problem. Samba sits on top of the Linux permissions.

I should have noted that I can browse the shares from WIndows computers with full permissions.

Thanks for the replies guys. The first problem has really stumped me, because all the permissions are set to read/write access and users on the local machine can browse the shares with no problem. I'm not really a newbie to Samba as I've been using it for two years, all the users have been created with smbpasswd and everything LOOKS like it should work fine. Again, this started happening one day totally out of the blue. Doesn't matter how many re-installs or even upgrades to slackware or Samba itself I do, still happens.

jjohnston62 - thanks for the suggestion, I've been looking through docs all over the web, samba.org also....This is really mysterious.

The second problem is really getting to me also. Why is it only trying to connect through the external interface? I have set the interfaces and bind interfaces only directives to the proper subnets, and I have a static route through eth0 for all connections from the server to my internal subnet. Very frustrating.

I've just upgraded to Samba 3.0 and done a fresh install. Same problem.

Happens with NFS also (the permission problem)

Have you tried removing the public address from this line?
"hosts allow = 127. 192.168.1. 69.22.254.131"

That just doesn't look right to me.

Chris