Samba not working

[OralDeckard]

I have two FC6 servers set up exactly alike, named "server" and "backup-server." The one named server works, mostly. The one named backup-server works very poorly.

I have followed Firewing1's setup instructions in his excellent Howto.

I have copied all samba related files from server to the non-working backup-server, changing only the netbios name and hostname.

The backup-server can browse all Windows systems, but can only see the first level of folders on the server. Any attempt to access a server folder gets an error message saying the folder doesn't exist.

All Windows systems and server can see the first level of folders on backup-server, but when attempting access they get an error message saying the folder doesn't exist.

I have been reading through every vaguely related thread on this forum for a month, and Samba may be working for others, but not for me. I gave up SuSE where it worked fine, and I MUST get it going on Fedora soon, or my ass is going to get kicked, hard. It worked fine for me in Xandros, so if I can't get it to work in Fedora I guess I can go back there

So in desperation I have carefully gone through Man Samba and found that I can produce an optimized version of smb.conf by copying my smb.conf to smb.conf.master, then adding -s to testparm, thus:
testparm -s /etc/samba/smb.conf.mater > /etc/samba.conf

The result has my eyeballs popping. Some of the things I thought were so vital do not show up in the optimized version.

Here is a small clip from smb.conf.master:
[global]

# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
workgroup = workgroup

# server string is the equivalent of the NT Description field
netbios name = backup-server
server string = Fedora Core 6

# Security mode. Defines in which mode Samba will operate. Possible
# values are share, user, server, domain and ads. Most people will want
# user level security. See the Samba-HOWTO-Collection for details.
security = user

# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
; hosts allow = 192.168.1. 192.168.2. 127.
hosts allow = 192.168.10. 127.

Now here is the equivelent clip from the optimized smb.conf:
[global]
server string = Fedora Core 6
map to guest = Bad User
username map = /etc/samba/smbusers
log file = /var/log/samba/%m.log
max log size = 50
os level = 33
wins proxy = Yes
hosts allow = 192.168.10., 127.

Where is workgroup = workgroup ?
Where is netbios name = backup-server ?

I mean, if they don't appear in the optimized version, does't that mean they are treated like all the commented stuff, and are treated that way even in the non-optimized version ?

Basically, I believe I have it set up correctly, and there is a possibility that it will continue to fail because there is something wrong in FC6. I have updated samba, and have uninstalled Samba and reinstalled it.

I will be quite happy to try whatever suggestions anyone has. I really like Fedora, and don't want to have to give it over something like this, but the boss isn't going to be patient forever.

I will very much appreciate any help anyone can give.

[glennzo]

Here's my smb.conf from the 'server' I call Oldendorff, although it's not really a server, it just has a shared printer and we back up to it from Linux and Windows boxes. There are several shares where we can grab files. This 'server' dual boots Fedora and XP, on two seperate hard disks, but usually runs Fedora. That's why the windows shares.

[global]
netbios name = Oldendorff
server string = Server Oldendorff
workgroup = JOHNSON
security = share
#encrypt passwords = yes
#smb passwd file = /var/lib/samba/private/smbpasswd
log file = /var/log/samba/%m.log
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
#wins support = yes
#hostname lookups = yes
#hosts equiv = /etc/hosts
#hosts deny = All
#hosts allow = 192.168.1.1/255.255.255.0 localhost
#hosts deny = All
#interfaces = lo eth0
#bind interfaces only = yes
guest ok = yes
#browse list = yes
printcap name = cups
printing = cups
load printers = yes

# Linux shares
[johnson]
path = /backups/johnson
Comment = Johnson Backup Share
guest ok = yes
browseable = yes
writable = yes
public = yes
read only = no

[grace]
path = /backups/grace
Comment = Grace Backup Share
guest ok = yes
browseable = yes
writable = yes
public = yes
read only = no

[public]
path = /home/public
comment = Public Shared Folder
guest ok = yes
browseable = yes
public = yes
writable = yes
read only = no

[homes]
comment = User's home directory
path = /home/%U
read only = no
valid users = %U root

[printers]
comment = All Printers
browseable = no
printable = yes
writable = no
public = yes
guest ok = yes
path = /var/spool/samba

[EPSON]
comment = LinuxEpson
printable = yes
path = /var/spool/samba
public = yes
guest ok = yes

#Windows shares
[c]
Comment = Windows Drive C share
path = /media/win1
public = yes
writable = yes
read only = no
browseable = yes
guest ok = yes

[d]
Comment = Windows Drive D share
path = /media/win2
public = yes
writable = no
read only = yes
browseable = yes
guest ok = yes

Here's the /etc/hosts file from Oldendorff. I've been using static ip addresses. I think it helps.

# Do not remove the following line, or various programs
# that require network functionality will fail.
#::1 localhost.localdomain localhost
127.0.0.1 oldendorff.localdomain oldendorff localhost.localdomain localhost
192.168.1.100 meg
192.168.1.101 dad
192.168.1.102 neville
192.168.1.103 oldendorff
192.168.1.104 mom

I invite anyone to correct me, but I think that there's a need to create a user on the server in certain instances, although there's five computers here but there's not five users on Oldendorff. Hope this is of some help.

[OralDeckard]

Well I can see that you too believe that netbios belongs in smb.conf. I restarted the smb service, then tried accessing it again, since the optimized smb.conf file without it was in place.

The result: Browsers still found backup-server on the LAN, but could not get in.
So I put netbios name = back in the optimized version, and this time changed the name to Test.

Now browsers find Test on the LAN, meaning that netbios does belong in the smb.conf file.
But still no one can browse further than the first level of folder. They can see them, but any attept to open one gets a message saying it does not exist.

So from this I conclude that the Samba Man page is wrong, and shall put smb.conf.master back in place as smb.conf.

Your /etc/hosts file contains the static IPs of the hosts on your LAN. I'm runnig dhcp, so they can change, but I can tell what they re right now, and will put them in as an experiment.

But that should not matter, since backup-server, now Test, can access all the Windows systems, both read and write. They can be found, and are doing a great job of serving. Its just that the FC6 machines are currently not doing such a hot job of serving. Though Test can fully access a Windows system, neither the Windows system, or the other FC6 machine can access Test. And even on the better woking FC6 machine, some users can access, but others cannot, even though they are all set up exactly alike.

[OralDeckard]

OK, I just added several IP addresses to /etc/hosts, and restarted the SMB service. The result was the same.

[OralDeckard]

OK, here is my smb.conf file:

#======================= Global Settings =====================================
[global]

# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
workgroup = workgroup

# server string is the equivalent of the NT Description field
netbios name = backup-server
server string = Fedora Core 6

# Security mode. Defines in which mode Samba will operate. Possible
# values are share, user, server, domain and ads. Most people will want
# user level security. See the Samba-HOWTO-Collection for details.
security = user

# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
; hosts allow = 192.168.1. 192.168.2. 127.
hosts allow = 192.168.10. 127.

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
load printers = yes

# you may wish to override the location of the printcap file
; printcap name = /etc/printcap

# on SystemV system setting printcap name to lpstat should allow
# you to automatically obtain a printer list from the SystemV spool
# system
; printcap name = lpstat

# It should not be necessary to specify the print system type unless
# it is non-standard. Currently supported print systems include:
# bsd, cups, sysv, plp, lprng, aix, hpux, qnx
; printing = cups

# This option tells cups that the data has already been rasterized
cups options = raw

# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
; guest account = pcguest
map to guest = Bad User

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

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

# Use password server option only with security = server
# The argument list may include:
# password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
# password server = *
; password server = <NT-Server-Name>

# Use the realm option only with security = ads
# Specifies the Active Directory realm the host is part of
; realm = MY_REALM

# Backend to store user information in. New installations should
# use either tdbsam or ldapsam. smbpasswd is available for backwards
# compatibility. tdbsam requires no further configuration.
passdb backend = tdbsam

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting.
# Note: Consider carefully the location in the configuration file of
# this line. The included file is read at that point.
; include = /usr/local/samba/lib/smb.conf.%m

# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
; interfaces = 192.168.12.2/24 192.168.13.2/24

# 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

# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
os level = 33

# 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

# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
; logon script = %m.bat
# run a specific logon batch file per username
; logon script = %U.bat

# Where to store roving profiles (only for Win95 and WinNT)
# %L substitutes for this servers netbios name, %U is username
# You must uncomment the [Profiles] share below
; logon path = \\%L\Profiles\%U

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

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z

# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one WINS Server on the network. The default is NO.
; wins proxy = yes

# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The default is NO.
dns proxy = no
username map = /etc/samba/smbusers


#============================ Share Definitions ==============================
[homes]
comment = Home Directories
browseable = no
writeable = yes

[All Printers]
comment = All Printers
path = /var/tmp
printable = Yes
create mask = 0600
writeable = yes
guest ok = yes

[groups]
comment = All groups
path = /home/groups/
writeable = yes
inherit acls = Yes

[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @ntadmin root
force group = ntadmin
create mask = 0664

[vms]
path = /mnt/D/VMs
guest ok = yes
writeable = yes

[C]
path = /mnt/C
guest ok = yes
writeable = yes

[D]
path = /mnt/D/
writeable = yes
browseable = yes
case sensitive = no
guest ok = yes
browseable = yes

[data]
path = /mnt/D/Data
writeable = yes

[backups]
path = /mnt/D/Backups
guest ok = yes
writeable = yes

[Blocks]
path = /mnt/D/Data/blocks/
guest ok = yes
writeable = yes

[Card Delete]
path = /mnt/D/Data/Card Delete
guest ok = yes
writeable = yes

[Paper]
path = /mnt/D/Data/Paper/
guest ok = yes
writeable = yes

[PCS]
path = /mnt/D/Data/pcs
guest ok = yes
writeable = yes

[TM2003]
path = /mnt/D/Data/tm2003
guest ok = yes
writeable = yes

[TM2004]
path = /mnt/D/Data/tm2004
guest ok = yes
writeable = yes

[TM2005]
path = /mnt/D/Data/tm2005
guest ok = yes
writeable = yes

[TM2006]
path = /mnt/D/Data/tm2006
guest ok = yes
writeable = yes

[SHARED]
path = /home/myers/Shared/
guest ok = yes
writeable = yes
browseable = yes

[TM2007]
path = /mnt/D/Data/TM2007/
guest ok = yes
writeable = yes

[OralDeckard]

And here is my /etc/samba/smbusers file:

# Unix_name = SMB_name1 SMB_name2 ...
root = administrator admin
nobody = guest pcguest smbguest
myers = myers
dave = dave
robin = robin
administrator = administrator

[OralDeckard]

And here is my /etc/sysconfig/network file:

NETWORKING=yes
NETWORKING_IPV6=yes
HOSTNAME=Test.localdomain

[OralDeckard]

And this is my /etc/hosts file:

# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 Test.localdomain Test localhost.localdomain localhost
::1 localhost.localdomain localhost

192.168.10.15 Server
192.168.10.53 Cad3
192.168.10.99 Test

[OralDeckard]

The Samba Man page says I should test my setup by pinging from one to the other. So I did. From Test I can ping Server, and it works fine. But from server, where Konquerer can see Test and the first level of folder, the ping comes back "ping: unknown host Test"

So Test is serving well enough that it is partly visible to some programs, but does not answer requests.

[OralDeckard]

Ah, but when I ping it by IP instead of by name, it works

So it may be a DNS lookup problem.

[OralDeckard]

Actually, the DNS nameserver is my firewall router. It has assigned the IP 192.168.10.99 to Test, and Server has found Test with Konquerer. Therefore it cannot be a DNS lookup problem. That brings me back to Test bothering to answer when a client comes acalling.

Is that due to configuration, or Samba failing to function?