samba no longer working

[karasu]

I *had* samba configured to share a few folders as microsoft network shares but recently, I am no longer able to access those shares from any computer on my network. The shared folders are still visible, but any time I try to open them, I get errors saying that either the folder does not exist (from other computers running linux) or that I don't have permission to view the share (from windows). What kinds of things would cause this? I am running FC6 on all effected machines.

I have made sure that:
1) my firewall allows samba through. It was working before, and temporarily turning it off did not help either
2) SElinux policy allows samba to share. I even disabled SElinux temporarily to see if that was the root of the problem.
3)folders were made public. They were shared until recently and I didn't make an concious changes to the configuration of Samba.


heres my samba configuration file:

[global]

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

# server string is the equivalent of the NT Description field
server string = Samba Server

# 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.

# 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

# 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 = no

# 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

# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations.
;   domain logons = 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
restrict anonymous = no
domain master = no
preferred master = no
max protocol = NT
acl compatibility = winnt
ldap ssl = No
server signing = Auto
security = share

[homes]
case sensitive = no
strict locking = no
guest ok = yes
msdfs proxy = no

[dkeav]

obvious question what has changed? what upgrades have taken place, have you restarted samba and check logs for errors

have you made sure the samba's passwd db is not corrupted or something

[karasu]

I'm still trying to figure out what changed. I'll never be able to figure out what if any upgrades did it because I don't know precisely when it stopped working. I just checked the log and this seems to be a common error:

smb signing is incompatible with share level security !

but I don't know what that means

[dkeav]

have you tried turning off selinux and/or firewall on the server yet

also when you try to connect manually with smbclient does it gives you useable errors

try resetting your samba users passwd with smbpasswd -a yourusername

[karasu]

yeah, its definitly not the selinux of firewall because I have turned both off still had no luck. I just tried resetting the samba users passwd and restarted the smb service, but still can't access the shares. I can only see them but not enter them like always

[dkeav]

this is rather odd behavior since you say they were working then stopped

[XiaoKJ]

IIRC, there was something in the news about Microsoft updating the smb system in windows to drop support for some security protocol ver 1...

[jaygee432]

Just a thought, try changing that line to security = user.

[karasu]

IIRC, there was something in the news about Microsoft updating the smb system in windows to drop support for some security protocol ver 1...

Even if it lost support within windows, I should still be able to access the shares from other linux boxes running the same version of samba, right?

Just a thought, try changing that line to security = user.

OOO! So close! I can access the share like that, but I have to enter a username and password first. I'm not sure if its a one time thing or if it'll prompt me to enter my credentials again if I reboot and try to connect again, but at least I have that access back. Thanks. If anyone knows how to get it to connect without prompting for a username and password, please tell me.

[karasu]

ok, so I have access to and from windows, but still have the same problem when trying to access the shares on one linux box from another. Suggestions?

[blobaugh]

if you can access it with the windows box then you are probably using the wrong credentials with linux. also did you check the permissions on folder you are trying to share? you will be refused access if the connecting user cannot connect to that folder locally

[dkeav]

err more to the folder you are trying to mount the share to

[blobaugh]

sorry. thats what i meant. worded it badly i guess

[karasu]

if you can access it with the windows box then you are probably using the wrong credentials with linux. also did you check the permissions on folder you are trying to share? you will be refused access if the connecting user cannot connect to that folder locally

all users of the system have rwx permissions to the folder for the sake that I'm the only person who uses the systems. Basically, under the user setting, I have to enter my username and password anytime I want to access the share from windows. From linux, I still cannot access the shares on other linux boxes configured identically. I wouldn't mind having to log in each time, but my 2 linux boxes can only see the shares and not enter them.

[dkeav]

you might want to setup autofs to mount your samba shares on the linux side anyways