Samba Client Doesn't See Samba Server

Hi

I have a problem with the samba client. Googled a lot tried swerdna's howto etc. It seems nothing works.

I use openSUSE 10.3
Firewall is stopped

When I mount a samba share from the server, it works fine on this client. On the samba server PC I see the samba server and a windows xp PC.

My problem is, I can't browse the samba shares. I see the workgroup on the client PC with smb://remi but then it stops. The error messages is that the server didn't respond within the tiome limit.

Anybody any idea what could be wrong? Btw I tried openSUSE 11Beta 3 with the same result.

My smb.conf:
===============
# 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: 2007-12-04
[global]
workgroup = remi
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:
usershare allow guests = Yes
[homes]
comment = Home Directories
valid users = %S, %D%w%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

[pfff]
comment = pff
inherit acls = Yes
path = /mnt/sdb2/BitTorrent/Incoming/
read only = No

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

the dhcp.conf file is the default with only comment.

Thanks for any advice

Btw. 1: I had this working with openSUSE 10.2 but never succeeded in getting it to work with 10.3
Btw 2: If I start rcnmb and rcsmb on the client. Windows XP sees this server, local on the client/server, it doesn't see the server

Hi, can you clarify for me, I'm a little confused. 3 questions:
1: You have a Suse Samba server and separately a Suse Samba client, is that right?
2: Is the smb.conf you posted for the server or the client (I think it's the server)?
3: please post the smb.conf from the other Suse too.

Thanks
Swerdna

BTW check in Yast --> system --> system services (runlevel) --> expert mode: check that levels 3 and 5 are checkmarked for both of nmb and smb.

Hi, can you clarify for me, I'm a little confused. 3 questions:
1: You have a Suse Samba server and separately a Suse Samba client, is that right?
[/b]

To keep things simpel, yes.
But there is also a Windows XP PC. And if I start nmb and smb on the client it is a server too. The same when I share a directory from my Windows PC.

2: Is the smb.conf you posted for the server or the client (I think it's the server)?
[/b]

The client. But again if I start nmb and smb it act's as a server too.

3: please post the smb.conf from the other Suse too.
[/b]

# 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: 2007-09-22
[global]
workgroup = remi
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:
usershare allow guests = No
add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody
-s /bin/false %m$
domain logons = No
domain master = No
netbios name = Bora-Server
passdb backend = smbpasswd
security = user
[homes]
comment = Home Directories
valid users = %S, %D%w%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

[shared-docs]
comment = shared-docs
inherit acls = Yes
path = /mnt/Samba2/Users/shared-docs/
read only = No

[multi-media]
comment = Multi-Media
inherit acls = Yes
path = /mnt/Samba1/Multi-Media/
read only = No

[suse-software]
comment = Suse-Software
inherit acls = Yes
path = /mnt/Samba1/Software/Suse
read only = No

[win-software]
comment = Win-Software
inherit acls = Yes
path = /mnt/Samba0/software
read only = No

## Share disabled by YaST
# [netlogon]

[iso]
comment = ISO
inherit acls = Yes
path = /mnt/Samba1/Software/ISO
read only = No
suse-software =

BTW check in Yast --> system --> system services (runlevel) --> expert mode: check that levels 3 and 5 are checkmarked for both of nmb and smb.
[/b]

nmb and smb is running with level 3 and 5

To make things more confusing, I found that smb://192.168.1.43 shows the shares. But I still can't browse them with smb://remi.

Thanks for any advice.

Lets refer to the first one as the Suse client and the second one as the Suse Server.
Nmb lets you see computers in network browsers so ordinarily check runlevels 3 and 5 for smb and nmb.

This line is an error and should be edited out:

suse-software =[/b]

You can edit smb.conf with a superuser version of kate, kwrite or gedit; e.g. enter one of these ion a console: kdesu kwrite /etc/samba/smb.conf or gnomesu gedit /etc/samba/smb.conf

Your shares written in the two smb.conf files require an ingoing network user to authenticate. So on each computer add a users or users to the Samba user database. You can only add users to the Samba user database if they are alraedy Linux (logon) users of the computer. You add a user e.g. "hilary" to the Samba user database with this command in a console:

sudo smbpasswd -a hilary[/b]

So from a windows or a Suse box, a user looking into a Suse box will respond to the authentication challenge with hilary's (or whoever) credentials.

The [global] paragraph in smb.conf for the server should be replaced with this version, using a superuser editor:

[global]
workgroup = REMI
netbios name = Bora-Server
name resolve order = bcast host lmhosts wins
server string = ""
printing = cups
printcap name = cups
printcap cache time = 750
cups options = raw
use client driver = yes
map to guest = Bad User
local master = yes
preferred master = yes
os level = 65
usershare allow guests = Yes
usershare max shares = 100
usershare owner only = False[/b]

The [global] paragraph in smb.conf for the client should be replaced with this version, using a superuser editor:

[global]
workgroup = REMI
netbios name = name_of_this_workstation
name resolve order = bcast host lmhosts wins
server string = ""
printing = cups
printcap name = cups
printcap cache time = 750
cups options = raw
use client driver = yes
map to guest = Bad User
local master = yes
os level = 33
usershare allow guests = Yes
usershare max shares = 100
usershare owner only = False[/b]

Change "name_of_this_workstation" to something appropriate

These two [global] paragraphs will implement name resolution by Local Master Browser(s) and the difficulty seeing computers should be solved. Notice the server is dominant by virtue of these lines:

preferred master = yes
os level = 65[/b]

It will prevail over windows machines and over the other Suse machine to become the collector and dispenser of netbios name <--> IP address pairs for the LAN.

It certainly helps initially after you're all set -- to reboot the lan boxes one at a time in sequence, waiting for one to finish before starting the next one off, and do that rigmarole twice. That gets them all introduced to each other faster. Even so you might have to have a cup of tea or a while they get to know each other.

Swerdna

Your netbios name is bora-server, not remi. Your workgroup is remi, but it's the netbios name the client is looking for.

Hi

This worked. Thanks for your help.

CU