Hello,

I have used Samba on a FreeBSD server and had little problem setting up authentication, etc..

However, doing this for the first time on Suse 10.0 and I am having some difficulty seeing the Suse shares from my Windows XP station. My samba file looks like:

# smb.conf is the main Samba configuration file. You find a full commented
# version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE if the
# samba-doc package is installed.
# Date: 2005-11-11
[global]
workgroup = STVA
printing = cups
printcap name = cups
printcap cache time = 750
cups options = raw
map to guest = Bad User
include = /etc/samba/dhcp.conf
logon path = \\%L\profiles\.msprofile
logon home = \\%L\%U\.9xprofile
logon drive = P:
domain logons = No
domain master = No
netbios name = ITServer02
passdb backend = smbpasswd
password server = *
security = domain
[homes]
comment = Home Directories
valid users = %S
browseable = No
read only = No
inherit acls = Yes
[profiles]
comment = Network Profiles Service
path = %H
read only = No
store dos attributes = Yes
create mask = 0600
directory mask = 0700
[users]
comment = All users
path = /home
read only = No
inherit acls = Yes
veto files = /aquota.user/groups/shares/
[groups]
comment = All groups
path = /home/groups
read only = No
inherit acls = Yes
[printers]
comment = All Printers
path = /var/tmp
printable = Yes
create mask = 0600
browseable = No
[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @ntadmin root
force group = ntadmin
create mask = 0664
directory mask = 0775

[install]
comment = Installation software for company
inherit acls = Yes
path = /shares/install/
read only = No

## Share disabled by YaST
# [netlogon]

I also created an account using:

smbpasswd -a 'account that is already on windows on suse'

Still, I get access violations. Can somebody point me to some good doc, or some help. The suse guide didn't help me.

Regards,

Randy

Suse's firewall has a habit of stopping samba, try turning the firewall off and see if you still have the same problem.

Good point!
I should have mentioned in my original post:

1. The firewall is not running
2. I can 'see' the server from a Microsoft box, I just can't browse to the shares.

Regards,

Randy.

Try changing:

security = domain

To:

security = share

Is this running just as a samba server and not a domain controller, if so having it set to security = domain it will try to use a domain controller to validate the users.

Also is your windows machines part of the same workgroup STVA ?

You will also need the allow hosts = 192.168.1. in the [global] settings as well.

Here is a copy of my smb.conf [global] settings you may find some of it useful


#start of file

[global]

netbios name = voyager
workgroup = myplace

server string = Slack9

encrypt passwords = yes
unix password sync = yes

time server = yes

smb passwd file = /etc/samba/smbpasswd
passwd chat = *New*password* %n\n *Please*retype*new*password* %n\n *password*successfully*updated*
passwd program = /usr/bin/passwd %u

socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=8192 SO_SNDBUF=8192

allow hosts = 192.168.1., 127., myplace
hosts deny = all

security = share
max log size = 5000
hide unreadable = yes
map to guest = bad user
#invalid users = root @wheel
dns proxy = no
printcap name = lpstat
load printers = yes
printing = cups
printer admin = @adm
remote announce = 192.168.1.255
lpq command = lpq -P %p
lprm command = cancel %p-%j
name resolve order = lmhosts host bcast
write cache size = 262144

#end of file

Also check your /etc/hosts.allow /etc/hosts.deny files and see if your allowing your network to connect, if /etc/hosts.allow is blank then trying adding your network to the file:

ALL:127.0.0.1
ALL:192.168.1.0/255.255.255.0

Assuming you have a 192.168.1.0 network, just change to your network.

You may also have in your /etc/hosts.deny:

ALL:ALL

This is ok just leave it this way, good for security.