Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
hey guys. having an ongoing problem. seems to me that samba is causing ALL client machines to freeze for anywhere from 1 thru 10 minutes. i have over 100 clients, 9 of them are win98, about 10 are win2k and the rest are XP Pro SP2 (firewalls disabled). i have been looking at this for the last 3 weeks and have no idea, so i have come to the brains trust to help me out. please, if you have any samba knowledge, have a read. many thanks in advance.
/etc/samba/smb.conf
Code:
#======================= Global Settings =====================================
[global]
# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
workgroup = main
# server string is the equivalent of the NT Description field
server string = serv02
# 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. 127.
# 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
# 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
# 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 = 35
# 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 = no
# 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 = no
# 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 = 192.168.1.6
# 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
# These scripts are used on a domain controller or stand-alone
# machine to add or delete corresponding unix accounts
; add user script = /usr/sbin/useradd %u
; add group script = /usr/sbin/groupadd %g
add machine script = /usr/sbin/adduser -d /dev/null -s /bin/false -M %u
; delete user script = /usr/sbin/userdel %u
; delete user from group script = /usr/sbin/deluser %u %g
; delete group script = /usr/sbin/groupdel %g
smb ports = 139
preserve case = yes
short preserve case = yes
case sensitive = no
keepalive = 0
socket options = TCP_NODELAY IPTOS_LOWDELAY
username map = /etc/samba/smbusers
smb passwd file = /etc/samba/smbpasswd
log level = 8
#============================ Share Definitions ==============================
[homes]
comment = Home Directories
valid users = %S
writeable = yes
browseable = no
# Un-comment the following and create the netlogon directory for Domain Logons
# [netlogon]
# comment = Network Logon Service
# path = /etc/samba/netlogon
# guest ok = no
# browseable = no
# writable = yes
# share modes = yes
# read only = no
# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
#[Profiles]
# comment = Roaming Profile Share
# path = /etc/samba/profiles
# browseable = no
# guest ok = yes
# writable = yes
# level2 oplocks = yes
# dos filetimes = yes
# profile acls = yes
# read only = no
# This one is useful for people to share files
[temp]
comment = Temporary file space
path = /temp
writeable = yes
browsable = no
guest ok = yes
create mask = 0777
directory mask = 0777
[s]
path = /s
writeable = yes
guest ok = yes
create mask = 0777
directory mask = 0777
[t]
path = /t
writeable = yes
guest ok = yes
create mask = 0777
directory mask = 0777
[audio]
path = /audio
writeable = yes
guest ok = yes
create mask = 0777
directory mask = 0777
[share]
path = /share
writeable = yes
browsable = no
guest ok = yes
create mask = 0777
directory mask = 0777
[appdisks]
path = /appdisks
writeable = yes
browsable = no
guest ok = yes
create mask = 0777
directory mask = 0777
[restricted]
path = /restricted
valid users = Person1
writeable = yes
browsable = no
guest ok = no
create mask = 0770
directory mask = 0770
/var/log/messages from Monday the 21st Jan 08
anything that says "checker" is a win98 client and "ftr" is a winXP client
Code:
Jan 23 08:40:31 serv02 nmbd[3845]: This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.8.
Jan 23 08:40:31 serv02 nmbd[3845]: [2008/01/23 08:40:31, 0] nmbd/nmbd_namequery.c:query_name_response(109)
Jan 23 08:40:31 serv02 nmbd[3845]: query_name_response: Multiple (11) responses received for a query on subnet 192.168.1.7 for name MAIN<1d>.
Jan 23 08:40:31 serv02 nmbd[3845]: This response was from IP 192.168.1.6, reporting an IP address of 192.168.1.8.
Jan 23 08:46:08 serv02 smbd[11018]: [2008/01/23 08:46:08, 0] lib/util_sock.c:read_data(534)
Jan 23 08:46:08 serv02 smbd[11018]: read_data: read failure for 4 bytes to client 192.168.1.1. Error = Connection reset by peer
Jan 23 09:16:43 serv02 smbd[11167]: [2008/01/23 09:16:43, 0] lib/util_sock.c:write_data(562)
Jan 23 09:16:43 serv02 smbd[11167]: write_data: write failure in writing to client 192.168.1.86. Error Connection reset by peer
Jan 23 09:16:43 serv02 smbd[11167]: [2008/01/23 09:16:43, 0] lib/util_sock.c:send_smb(769)
Jan 23 09:16:43 serv02 smbd[11167]: Error writing 61503 bytes to client. -1. (Connection reset by peer)
Jan 23 09:16:43 serv02 smbd[11167]: [2008/01/23 09:16:43, 0] lib/util_sock.c:write_data(562)
Jan 23 09:16:43 serv02 smbd[11167]: write_data: write failure in writing to client 192.168.1.86. Error Broken pipe
Jan 23 09:16:43 serv02 smbd[11167]: [2008/01/23 09:16:43, 0] lib/util_sock.c:send_smb(769)
Jan 23 09:16:43 serv02 smbd[11167]: Error writing 75 bytes to client. -1. (Broken pipe)
Jan 23 09:51:06 serv02 smbd[11241]: [2008/01/23 09:51:06, 0] lib/util_sock.c:write_data(562)
Jan 23 09:51:06 serv02 smbd[11241]: write_data: write failure in writing to client 192.168.1.88. Error Connection reset by peer
Jan 23 09:51:06 serv02 smbd[11241]: [2008/01/23 09:51:06, 0] lib/util_sock.c:send_smb(769)
Jan 23 09:51:06 serv02 smbd[11241]: Error writing 218 bytes to client. -1. (Connection reset by peer)
Jan 23 10:07:29 serv02 smbd[11239]: [2008/01/23 10:07:29, 0] smbd/service.c:make_connection(1191)
Jan 23 10:07:29 serv02 smbd[11239]: checker3 (192.168.1.62) couldn't find service
Jan 23 10:07:29 serv02 smbd[11239]: [2008/01/23 10:07:29, 0] smbd/service.c:make_connection(1191)
Jan 23 10:07:29 serv02 smbd[11239]: checker3 (192.168.1.62) couldn't find service
Jan 23 10:07:29 serv02 smbd[11239]: [2008/01/23 10:07:29, 0] smbd/service.c:make_connection(1191)
Jan 23 10:07:29 serv02 smbd[11239]: checker3 (192.168.1.62) couldn't find service
Jan 23 10:07:29 serv02 smbd[11239]: [2008/01/23 10:07:29, 0] smbd/service.c:make_connection(1191)
Jan 23 10:07:29 serv02 smbd[11239]: checker3 (192.168.1.62) couldn't find service
Jan 23 10:21:48 serv02 smbd[11263]: [2008/01/23 10:21:48, 0] lib/util_sock.c:write_data(562)
Jan 23 10:21:48 serv02 smbd[11263]: write_data: write failure in writing to client 192.168.1.86. Error Connection reset by peer
Jan 23 10:21:48 serv02 smbd[11263]: [2008/01/23 10:21:48, 0] lib/util_sock.c:send_smb(769)
Jan 23 10:21:48 serv02 smbd[11263]: Error writing 61503 bytes to client. -1. (Connection reset by peer)
Jan 23 10:21:48 serv02 smbd[11263]: [2008/01/23 10:21:48, 0] lib/util_sock.c:write_data(562)
Jan 23 10:21:48 serv02 smbd[11263]: write_data: write failure in writing to client 192.168.1.86. Error Broken pipe
Jan 23 10:21:48 serv02 smbd[11263]: [2008/01/23 10:21:48, 0] lib/util_sock.c:send_smb(769)
Jan 23 10:21:48 serv02 smbd[11263]: Error writing 75 bytes to client. -1. (Broken pipe)
Jan 23 10:44:27 serv02 smbd[11277]: [2008/01/23 10:44:27, 0] lib/util_sock.c:read_data(534)
Jan 23 10:44:27 serv02 smbd[11277]: read_data: read failure for 4 bytes to client 192.168.1.86. Error = Connection reset by peer
Jan 23 10:44:27 serv02 smbd[11277]: [2008/01/23 10:44:27, 0] lib/util_sock.c:write_data(562)
Jan 23 10:44:27 serv02 smbd[11277]: write_data: write failure in writing to client 192.168.1.86. Error Broken pipe
Jan 23 10:44:27 serv02 smbd[11277]: [2008/01/23 10:44:27, 0] lib/util_sock.c:send_smb(769)
Jan 23 10:44:27 serv02 smbd[11277]: Error writing 75 bytes to client. -1. (Broken pipe)
Jan 23 11:05:08 serv02 smbd[11239]: [2008/01/23 11:05:08, 0] smbd/service.c:make_connection(1191)
Jan 23 11:05:08 serv02 smbd[11239]: checker3 (192.168.1.62) couldn't find service
Jan 23 11:05:08 serv02 smbd[11239]: [2008/01/23 11:05:08, 0] smbd/service.c:make_connection(1191)
Jan 23 11:05:08 serv02 smbd[11239]: checker3 (192.168.1.62) couldn't find service
Jan 23 11:05:08 serv02 smbd[11239]: [2008/01/23 11:05:08, 0] smbd/service.c:make_connection(1191)
Jan 23 11:05:08 serv02 smbd[11239]: checker3 (192.168.1.62) couldn't find service
Jan 23 11:05:08 serv02 smbd[11239]: [2008/01/23 11:05:08, 0] smbd/service.c:make_connection(1191)
Jan 23 11:05:08 serv02 smbd[11239]: checker3 (192.168.1.62) couldn't find service
Jan 23 11:05:13 serv02 smbd[11239]: [2008/01/23 11:05:13, 0] smbd/service.c:make_connection(1191)
Jan 23 11:05:13 serv02 smbd[11239]: checker3 (192.168.1.62) couldn't find service
Jan 23 11:05:13 serv02 smbd[11239]: [2008/01/23 11:05:13, 0] smbd/service.c:make_connection(1191)
Jan 23 11:05:13 serv02 smbd[11239]: checker3 (192.168.1.62) couldn't find service
Jan 23 11:05:13 serv02 smbd[11239]: [2008/01/23 11:05:13, 0] smbd/service.c:make_connection(1191)
Jan 23 11:05:13 serv02 smbd[11239]: checker3 (192.168.1.62) couldn't find service
Jan 23 11:05:13 serv02 smbd[11239]: [2008/01/23 11:05:13, 0] smbd/service.c:make_connection(1191)
Jan 23 11:05:13 serv02 smbd[11239]: checker3 (192.168.1.62) couldn't find service
Jan 23 11:05:15 serv02 smbd[11281]: [2008/01/23 11:05:15, 0] smbd/service.c:make_connection(1191)
Jan 23 11:05:15 serv02 smbd[11281]: checker9 (192.168.1.68) couldn't find service
Jan 23 11:05:15 serv02 smbd[11281]: [2008/01/23 11:05:15, 0] smbd/service.c:make_connection(1191)
Jan 23 11:05:15 serv02 smbd[11281]: checker9 (192.168.1.68) couldn't find service
Jan 23 11:05:16 serv02 smbd[11281]: [2008/01/23 11:05:16, 0] smbd/service.c:make_connection(1191)
Jan 23 11:05:16 serv02 smbd[11281]: checker9 (192.168.1.68) couldn't find service
Jan 23 11:05:16 serv02 smbd[11281]: [2008/01/23 11:05:16, 0] smbd/service.c:make_connection(1191)
Jan 23 11:05:16 serv02 smbd[11281]: checker9 (192.168.1.68) couldn't find service
Jan 23 11:50:39 serv02 smbd[11249]: [2008/01/23 11:50:39, 0] smbd/service.c:make_connection(1191)
Jan 23 11:50:39 serv02 smbd[11249]: checker2 (192.168.1.66) couldn't find service
Jan 23 11:50:39 serv02 smbd[11249]: [2008/01/23 11:50:39, 0] smbd/service.c:make_connection(1191)
Jan 23 11:50:39 serv02 smbd[11249]: checker2 (192.168.1.66) couldn't find service
Jan 23 11:50:39 serv02 smbd[11249]: [2008/01/23 11:50:39, 0] smbd/service.c:make_connection(1191)
Jan 23 11:50:39 serv02 smbd[11249]: checker2 (192.168.1.66) couldn't find service
Jan 23 11:50:39 serv02 smbd[11249]: [2008/01/23 11:50:39, 0] smbd/service.c:make_connection(1191)
Jan 23 11:50:39 serv02 smbd[11249]: checker2 (192.168.1.66) couldn't find service
Jan 23 11:54:00 serv02 smbd[11281]: [2008/01/23 11:54:00, 0] smbd/service.c:make_connection(1191)
Jan 23 11:54:00 serv02 smbd[11281]: checker9 (192.168.1.68) couldn't find service
Jan 23 11:54:00 serv02 smbd[11281]: [2008/01/23 11:54:00, 0] smbd/service.c:make_connection(1191)
Jan 23 11:54:00 serv02 smbd[11281]: checker9 (192.168.1.68) couldn't find service
Jan 23 11:54:00 serv02 smbd[11281]: [2008/01/23 11:54:00, 0] smbd/service.c:make_connection(1191)
Jan 23 11:54:00 serv02 smbd[11281]: checker9 (192.168.1.68) couldn't find service
Jan 23 11:54:00 serv02 smbd[11281]: [2008/01/23 11:54:00, 0] smbd/service.c:make_connection(1191)
Jan 23 11:54:00 serv02 smbd[11281]: checker9 (192.168.1.68) couldn't find service
Jan 23 11:54:04 serv02 smbd[11268]: [2008/01/23 11:54:04, 0] smbd/oplock.c:oplock_timeout_handler(356)
Jan 23 11:54:04 serv02 smbd[11268]: Oplock break failed for file C9_23-01-08 11-55_01c85db6e9f30cb0.wav -- replying anyway
Jan 23 12:10:12 serv02 smbd[11281]: [2008/01/23 12:10:12, 0] smbd/service.c:make_connection(1191)
Jan 23 12:10:12 serv02 smbd[11281]: checker9 (192.168.1.68) couldn't find service
Jan 23 12:10:13 serv02 smbd[11281]: [2008/01/23 12:10:13, 0] smbd/service.c:make_connection(1191)
Jan 23 12:10:13 serv02 smbd[11281]: checker9 (192.168.1.68) couldn't find service
Jan 23 12:10:13 serv02 smbd[11281]: [2008/01/23 12:10:13, 0] smbd/service.c:make_connection(1191)
Jan 23 12:10:13 serv02 smbd[11281]: checker9 (192.168.1.68) couldn't find service
Jan 23 12:28:21 serv02 smbd[11283]: [2008/01/23 12:28:21, 0] smbd/oplock.c:oplock_timeout_handler(356)
Jan 23 12:28:21 serv02 smbd[11283]: Oplock break failed for file Court 8/Today/20080123/COURT8/COURT8_23-01-08 12-28_01c85dbb772f3870.wav -- replying anyway
Jan 23 13:04:53 serv02 smbd[11230]: [2008/01/23 13:04:53, 0] lib/util_sock.c:read_data(534)
Jan 23 13:04:53 serv02 smbd[11230]: read_data: read failure for 4 bytes to client 192.168.1.38. Error = Connection reset by peer
Jan 23 13:04:53 serv02 smbd[11230]: [2008/01/23 13:04:53, 0] lib/util_sock.c:write_data(562)
Jan 23 13:04:53 serv02 smbd[11230]: write_data: write failure in writing to client 192.168.1.38. Error Broken pipe
Jan 23 13:04:53 serv02 smbd[11230]: [2008/01/23 13:04:53, 0] lib/util_sock.c:send_smb(769)
Jan 23 13:04:53 serv02 smbd[11230]: Error writing 75 bytes to client. -1. (Broken pipe)
Was there any upgrade on the version that you were running ? i don't know the exact reason for the problem, but just try running samba with a different version of kernel if you are having one already.
Was there any upgrade on the version that you were running ? i don't know the exact reason for the problem, but just try running samba with a different version of Linux kernel.
do you have seperate print server, and server running as firewall...
I think i would be checking cables first, particularly any that have been removed or replaced of late...
Having a wire broke in a cable, can hang a server for some time(first hand experience there, and took time to find too)...
Another check would be the router...
as for cables, even just pushing one aside could cause a seperation, and they arnt easy to find..
PS, dont limit this search to just the server, check clients too...
Last edited by wraithe; 01-23-2008 at 12:25 AM.
Reason: added PS
wow, must say im impressed with the response times. last time i posted i didnt get any replies for days. anyway, the last upgrade of kernel was awhile ago (like 2-3 months) and i have had a few problems since then, and i cant say for certain that this problem hasnt been around since the upgrade. should i upgrade to the latest version? im just worried it will cause more problems. i can try using an old kernel, no probs.
i have replace the old CAT5 cable that runs from server to wall with a CAT6, but havent changed anything on the patch panel side of things. i will try that too.
the router shouldnt be a problem, as all the traffic is on the local network.
no firewalls are running on the internal network, and there are no print servers
i dont think it would be a client side problem, especially seeing that there are over 100 computers, of different configurations all with the same problem.
love the ideas, keep them coming. i will test the cables and kernel when i can.
Distribution: Debian /Jessie/Stretch/Sid, Linux Mint DE
Posts: 5,195
Rep:
This is a nightmare. Seeing this, I am also slightly biased to a HW problem. It could be anything between a client and your server, including a switch port, switch, cable, server network adapter. It could even be a hard disk in your server which suddenly exposes extended seek times.
What I would do in your case is setting up a second Samba server, transfer a part (or a whole) of the data to it and transfer 20 or so clients to the other server. What happens to the problem then?
Sometimes it is nice to figure out what's going on. Some other times it is better to solve whatever problem you have using brute force and se if you can find the cause. If not, too bad, but at least you got your network up again.
another thing to consider is looking at the logs, find the ip that shows the errors and unplug it for a limited amount of time...then do the same for the next ip that shows errors...i seen 2 ips in that original log that could be removed and then wait for x amount of time, to see if the error returns...it may be a fault with another box and your server is going nuts trying to resolve it...
well, i had just downloaded updates for both my linux servers, and there was an "issue", which basically gave me the opportunity to install the updates and restart the servers. packages inc the kernel and samba packages were updated in this process. i cant say for sure, but it seems from the logs the problem is still there, but i will confirm with you when i can.
the problem with moving part of my shares to another server is that all the data needs to be in the same place. yes, i could move a share, eg "audio" to another server, but that would mean reconfigging 100+ computers, which, in my case, is more difficult than it sounds.
in terms of a HW issue, i am happy to agree in part. this particular server is a custom built beast, less than 6 months old. has a Core 2 duo 4400, 2x 1Gb Kingston Ram 667Mhz, 2x 500Gb WD SATA2 7200rpm RAID1, and a Gigabyte GA P35 DS3 board. (partly bragging, partly informing )
i could go with removing a computer or 5 from the network, but it would mean a bit of shuffling around, but i will try anything to get this baby working purrfectly
high praise for sticking with this guys, you are a big help. i'll let you know more asap
well it seems part of the problem is solved, in that /var/log/messages shows nothing new since 11:15 am on friday (and its now tuesday morning) which is nice. still no news on the freezing issues, but will update you on those later.
i said above that PART of the problem was fixed, meaning part is still in limbo. looking at the /var/log/samba/smbd.log file, it is still showing numerous errors revolving around socket options. take a look:
i take it back. /var/log/messages does still have a bunch of errors/notifications coming up, very similar to my first post. i had tried to clean it out, cos it had about 5 days of logs in the one file, and opening it became a nightmare, but now it wont log to "messgaes", it created a file called "messages~" so any help repairing this would help too.
seems like there is still the freezing problem as well. could it be that there are too many concurrent connections or that the system is under too much load? i ccant remember if i said this before, but i have about 100 client pc's accessing audio and files in realtime directly fcrom the server.
ok, so i have moved the audio to a different server, and it seems to have cleared the freezing problem, although, im unsure whether its to do with too many concurrent connections or if there is a problem with my samba setup itself. any ideas?
The only thing to do now, is wait and see, give it a few days to see if it worked, then go back over things you have done...if the problem has gone, and you have done nothing except moving the audio to another server, then it may have been a server overload...
Good to hear that you've got some sort of result, anyway....
Well, it seems the move from one server to another didnt help. the audio is still freezing. perhaps its something in my smb.conf. can any/all of you please have a look (above, first post) and see if there is anytyhing missing/wrong or if you can suggest any tweaks, i would very much appreciate it
While trying to fix the problem, I have temporarily moved audio from serv02 to serv01, but this did not help the situation.
Serv01
Smb.conf:
Code:
#
#======================= Global Settings =====================================
[global]
# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
workgroup = main
# server string is the equivalent of the NT Description field
server string = serv01
# 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. 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 = guest
# 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.1.6/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 = 255
# 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
logon script = logon.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
logon home = \\%L\%U
logon drive = Z:
# 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
# These scripts are used on a domain controller or stand-alone
# machine to add or delete corresponding unix accounts
; add user script = /usr/sbin/useradd %u
; add group script = /usr/sbin/groupadd %g
add machine script = /usr/sbin/adduser -d /dev/null -s /bin/false -M %u
; delete user script = /usr/sbin/userdel %u
; delete user from group script = /usr/sbin/deluser %u %g
; delete group script = /usr/sbin/groupdel %g
smb ports = 139
preserve case = yes
short preserve case = yes
case sensitive = no
; keepalive = 0
; socket options = TCP_NODELAY IPTOS_LOWDELAY
encrypt passwords = yes
smb passwd file = /etc/samba/smbpasswd
log level = 9
#============================ Share Definitions ==============================
[homes]
comment = Home Directories
valid users = %S
; read only = no
browseable = no
writable = yes
# Un-comment the following and create the netlogon directory for Domain Logons
[netlogon]
comment = Network Logon Service
path = /etc/samba/netlogon
guest ok = no
browsable = no
writable = no
; read only = no
# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
[Profiles]
comment = Roaming Profile Share
path = /etc/samba/profiles
browseable = no
guest ok = yes
writable = yes
level2 oplocks = yes
dos filetimes = yes
profile acls = yes
; read only = no
# This one is useful for people to share files
[temp]
comment = Temporary file space
path = /temp
writable = yes
browsable = no
guest ok = yes
public = yes
[audio]
comment = Audio
path = /audio
writable = yes
browsable = yes
guest ok = yes
public = yes
create mask = 777
directory mask = 777
/var/log/messages
Code:
Feb 6 15:40:17 serv01 nmbd[2672]: [2008/02/06 15:40:17, 0] libsmb/nmblib.c:send_udp(791)
Feb 6 15:40:17 serv01 nmbd[2672]: Packet send failed to 192.168.1.164(138) ERRNO=Invalid argument
Feb 6 15:41:33 serv01 nmbd[2672]: [2008/02/06 15:41:33, 0] libsmb/nmblib.c:send_udp(791)
Feb 6 15:41:33 serv01 nmbd[2672]: Packet send failed to 192.168.1.179(138) ERRNO=Invalid argument
Feb 6 15:41:33 serv01 nmbd[2672]: [2008/02/06 15:41:33, 0] libsmb/nmblib.c:send_udp(791)
Feb 6 15:41:33 serv01 nmbd[2672]: Packet send failed to 192.168.1.179(138) ERRNO=Invalid argument
Feb 6 15:41:35 serv01 nmbd[2672]: [2008/02/06 15:41:35, 0] libsmb/nmblib.c:send_udp(791)
Feb 6 15:41:35 serv01 nmbd[2672]: Packet send failed to 192.168.1.163(138) ERRNO=Invalid argument
Feb 6 15:41:35 serv01 nmbd[2672]: [2008/02/06 15:41:35, 0] libsmb/nmblib.c:send_udp(791)
Feb 6 15:41:35 serv01 nmbd[2672]: Packet send failed to 192.168.1.163(138) ERRNO=Invalid argument
#
#======================= Global Settings =====================================
[global]
# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
workgroup = main
# server string is the equivalent of the NT Description field
server string = serv02
# 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. 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.1.7/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 = 35
# 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 = no
# 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 = no
# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations.
# 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
# logon home = \\%L\%U
# logon drive = Z:
# 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 = 192.168.1.6
# 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
# These scripts are used on a domain controller or stand-alone
# machine to add or delete corresponding unix accounts
; add user script = /usr/sbin/useradd %u
; add group script = /usr/sbin/groupadd %g
add machine script = /usr/sbin/adduser -d /dev/null -s /bin/false -M %u
; delete user script = /usr/sbin/userdel %u
; delete user from group script = /usr/sbin/deluser %u %g
; delete group script = /usr/sbin/groupdel %g
smb ports = 139
preserve case = yes
short preserve case = yes
case sensitive = no
keepalive = 0
socket options = TCP_NODELAY IPTOS_LOWDELAY
username map = /etc/samba/smbusers
smb passwd file = /etc/samba/smbpasswd
log level = 9
#============================ Share Definitions ==============================
[homes]
comment = Home Directories
valid users = %S
writeable = yes
browseable = no
# Un-comment the following and create the netlogon directory for Domain Logons
# [netlogon]
# comment = Network Logon Service
# path = /etc/samba/netlogon
# guest ok = no
# browseable = no
# writable = yes
# share modes = yes
# read only = no
# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
#[Profiles]
# comment = Roaming Profile Share
# path = /etc/samba/profiles
# browseable = no
# guest ok = yes
# writable = yes
# level2 oplocks = yes
# dos filetimes = yes
# profile acls = yes
# read only = no
# This one is useful for people to share files
[temp]
comment = Temporary file space
path = /temp
writeable = yes
browsable = no
guest ok = yes
create mask = 0777
directory mask = 0777
[s]
path = /s
writeable = yes
guest ok = yes
create mask = 0777
directory mask = 0777
[t]
path = /t
writeable = yes
guest ok = yes
create mask = 0777
directory mask = 0777
[audio]
path = /audio
writeable = yes
guest ok = yes
create mask = 0777
directory mask = 0777
[share]
path = /share
writeable = yes
browsable = no
guest ok = yes
create mask = 0777
directory mask = 0777
[appdisks]
path = /appdisks
writeable = yes
browsable = no
guest ok = yes
create mask = 0777
directory mask = 0777
/var/log/messages
Code:
Feb 6 15:31:42 serv02 smbd[5347]: [2008/02/06 15:31:42, 0] smbd/service.c:make_connection(1191)
Feb 6 15:31:42 serv02 smbd[5347]: computer3 (192.168.1.62) couldn't find service
Feb 6 15:31:54 serv02 smbd[5347]: [2008/02/06 15:31:54, 0] smbd/service.c:make_connection(1191)
Feb 6 15:31:54 serv02 smbd[5347]: computer3 (192.168.1.62) couldn't find service
Feb 6 15:31:54 serv02 smbd[5347]: [2008/02/06 15:31:54, 0] smbd/service.c:make_connection(1191)
Feb 6 15:31:54 serv02 smbd[5347]: computer3 (192.168.1.62) couldn't find service
Feb 6 15:31:54 serv02 smbd[5347]: [2008/02/06 15:31:54, 0] smbd/service.c:make_connection(1191)
Feb 6 15:31:54 serv02 smbd[5347]: computer3 (192.168.1.62) couldn't find service
Feb 6 15:31:54 serv02 smbd[5347]: [2008/02/06 15:31:54, 0] smbd/service.c:make_connection(1191)
Feb 6 15:31:54 serv02 smbd[5347]: computer3 (192.168.1.62) couldn't find service
(its not just computer3...)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
)
