Samba trouble

[d3bruts1d]

Hey everyone, I've got Samba (2.2.3a) installed on a Red Hat (7.3) box, and it seams to be working... Configured everything through SWAT.

My Windows XP box can see the Samba shares, however when I attempt to access these shares, I am prompted for a uers ID and password. I've tried using the User ID and PW from accounts located on my XPbox as well as those from my linuxbox, and none seam to work. I've even created the same user ID/PW on both systems...

Any idea what I need to do, or what I've done wrong?


Thanks.

[cowanrl]

The best place to start is by posting your /etc/samba/smb.conf file here. That will let us know what type of security you have set up on Samba. We can then make sure you have your user accounts set up properly.

One of the biggest problems related to Samba and Red Hat 7.3 is a firewall. If you accept the default firewall setting when you install RH 7.3, it will block all Samba traffic. Make sure you have your firewall disabled for testing purposes until you are sure Samba is working properly. You can then adjust your firewall to allow Samba traffic if need be.

[michaelk]

Did you add a samba password for the users?
(as root)
smbpasswd -a username

[d3bruts1d]

Yes, added samba password for user.... and I did something in the last 2 min, and windows no longer sees the share. :confused: So I'm going backwards.... ---Fixed this... got windows seeing the share again. :) Back to the origional issue...

I'll post conf in just a sec.

[d3bruts1d]

Conf is as follows:

# Samba config file created using SWAT
# from UNKNOWN (127.0.0.1)
# Date: 2002/09/15 09:58:35

# Global parameters
[global]
server string = Samba Server
security = SHARE
encrypt passwords = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *New*password* %n\n *Retype*new*password* %n\n *passwd:*all*authentication*tokens*updated*success fully*
log file = /var/log/samba/%m.log
max log size = 0
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
dns proxy = No
guest account =
printing = lprng

[homes]
comment = Home Directories
guest account = nobody
read only = No

[printers]
comment = All Printers
path = /var/spool/samba
printable = Yes
browseable = No

[swangods]

Are you missing a location for the shares?
path= /wherever/you/are

[swangods]

Originally posted by d3bruts1d
Conf is as follows:
[homes]
comment = Home Directories
guest account = nobody
read only = No

Hm, I don't use the [homes] share on my fileserver, but the sample from the comments in my smb.conf has a "valid users = %S" line. maybe that's useful? I haven't looked up what it means

#[homes]
# comment = Home Directories
# browseable = no
# writable = yes
# valid users = %S
# create mode = 0664
# directory mode = 0775

[d3bruts1d]

I got it!!

I got it!!

w00t!


It was just a matter of playing with it long enough until I got it working. Thanks for your time everyone....

And just to comapre the conf now looks like this:

# Samba config file created using SWAT
# from localhost (127.0.0.1)
# Date: 2002/09/15 10:11:21

# Global parameters
[global]
server string = Samba Server
encrypt passwords = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *new*password* %n\n *Retype*new*password* %n\n *changed*
log file = /var/log/samba/%m.log
max log size = 0
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
preferred master = False
domain master = False
printing = lprng

[homes]
comment = Home Directories
read only = No

[printers]
comment = All Printers
path = /var/spool/samba
printable = Yes
browseable = No

[FTPDIR]
path = /home/ftpdir
read only = No

[cowanrl]

Just a post for anybody who may come accross this thread months down the road when searching for a solution to their Samba problem.

The problem was with the "security = share" setting in the smb.conf file. That setting makes all Samba access like guest access. All of the user accounts created for Samba with smbpasswd are meaningless.

By removing the "security =" line, Samba defaults to "security = user". Now the Samba user accounts created with smbpasswd will be used and access from the Windows machines will work as expected.