Review your favorite Linux distribution.
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


Search this Thread
Old 06-24-2008, 08:16 PM   #1
Registered: Mar 2007
Location: Buenos Aires, Argentina.
Distribution: Debian Lenny AMD64
Posts: 506

Rep: Reputation: 32
Samba takes some time to recognize my win network.


I am sharing my network (one computer with Slackware and another running win) with samba. The network works ok but when booting up the computer or restarting it, samba takes around 5 minutes to recognize the network (?). Is this possible? Maybe, the service isn't start it automatically at start up. If so, How do I make it start at boot time?

Thank you!
Old 06-25-2008, 01:23 PM   #2
Senior Member
Registered: Nov 2002
Location: Somewhere inside 9.9 million sq. km. Canada
Distribution: Slackware 14.1
Posts: 4,873

Rep: Reputation: 434Reputation: 434Reputation: 434Reputation: 434Reputation: 434
Have you got
wins support = Yes
in your samba server's global section? If yes, have you defined the samba server on your windoze systems? If not, give this a try, it can't hurt, and should improve finding smb resources.

As I remember doing some reading on this topic, there are about four ways for smb resources to be located. The above is one way.
Old 06-25-2008, 07:58 PM   #3
Registered: Sep 2006
Location: Australia
Distribution: Slackware
Posts: 176

Rep: Reputation: 30
Hello glore2002,

You may also need to add wins support to /etc/nsswitch.conf

To do this:

1. Login to a root terminal

2. Edit the nsswitch.conf file, if you have Midnight Commander (mc) installed; type:

mcedit /etc/nsswitch.conf

3. look in the file for the 'hosts' line section.

4. Edit with the following:

hosts:          files wins dns mdns4_minimal mdn4 [NOTFOUND=return]
networks:       files
This will also have the benefit of being able to 'ping' by computer hostname rather than just by it's I.P.

Hope this helps.



p.s. here is my /etc/samba/smb.conf, you may be able to use it a reference.
# ====================
# = Note from Orbit  =
# ====================
# --------------------------------------------------------------------------
# - How I got Linux and Windows Xp to connect without requiring a password.-
# --------------------------------------------------------------------------
# To enable peer-to-peer networking with Linux/WindowsXP systems;
# First I installed the sambaclient package,
# (
# Then reinstall the standard slackware samba package:
# (
# Then I added the system users 'nobody' and 'guest'
# [using the network '/home/user/Shares' directory as their home directory,
# and creating a login # of /bin/false].
# Then i added these users to the samba password list with the commands;
# smbpasswd -a nobody (left password blank)
# and
# smbpasswd -a guest (left password blank)
# and
# smbpasswd -a user (left password blank)
# Now with these Samba accounts, combined with this configured smb.conf,
# Linux and Windows are communicating together quite happily using the
# 'Shares' directory, with full read-write permissions and ownership by 'user'.
# Enjoy :)
# --------------------------------------------------------------------------------------------------------
#======================= Global Settings =====================================

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

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

# 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.0. 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
printcap name = cups

# 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
printing = cups

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

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

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

# 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

# Most people will find that this option gives better performance.
# See the chapter 'Samba performance issues' in the Samba HOWTO Collection
# and the manual pages for details.
# You may want to add the following on a Linux system:
#         SO_RCVBUF=8192 SO_SNDBUF=8192
socket options = TCP_NODELAY SO_SNDBUF=16384 SO_RCVBUF=16384 

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

# 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 #(Add your ADSL Router I.P. address here)
;  wins server = #<<== Insert your ADSL Router I.P. address here].

# 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
map to guest = Bad User
restrict anonymous = no
guest ok = yes
domain master = no
preferred master = no
max protocol = NT
ldap ssl = No
server signing = Auto
netbios name = Server
case sensitive = no
# msdfs proxy = no
read only = no
acl compatibility = winnt

# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
;   comment = Network Logon Service
;   path = /usr/local/samba/lib/netlogon
;   guest ok = yes
;   writable = yes
;   share modes = no

# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;    path = /usr/local/samba/profiles
;    browseable = no
;    guest ok = yes

# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
comment = All Printers
printer name = COMPAQ_IJ650
#read only = yes
printable = yes
use client driver = Yes
browseable = yes
path = /var/spool/samba
public = yes
create mask = 0700
writable = no

#comment = Temporary file space
##path = /tmp/samba-tmp
#path = /tmp/Shares

path = /home/user/Shares/
follow symlinks = no
wide links = no
hide special files = yes
veto files = .directory/
veto oplock files = .directory/
strict locking = no
public = yes
guest ok = yes
read only = no
hosts allow = 192.168.0. 192.168.1. 192.168.2. 127.

Last edited by orbit; 06-25-2008 at 09:07 PM. Reason: added smb.conf
Old 06-26-2008, 07:08 PM   #4
Registered: Mar 2007
Location: Buenos Aires, Argentina.
Distribution: Debian Lenny AMD64
Posts: 506

Original Poster
Rep: Reputation: 32
Thanks for the help!

Thanks friends for the help. Maybe the delay is caused because computer with winxp is connected through wireless to the router. I've added the changes you suggested but things take a while to appear (but finally, they do).

By the way, What is nsswitch.conf for?

Thank you for the help!



Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Benchmarking a tape drive, time to copy takes forever, time to append takes longer? jeriryan Linux - Hardware 2 06-15-2008 01:15 AM
logging from network to linux machine takes longer time R0nIn Linux - Newbie 2 05-06-2005 04:51 AM
Hide Samba in Win-network?? overlord73 Linux - Software 1 02-08-2005 09:22 AM
Browsing Win file system slow to recognize network deanbrown3d Linux - Newbie 2 08-17-2004 04:19 PM
Samba win network monkeymartin Slackware 1 03-31-2003 04:46 PM

All times are GMT -5. The time now is 01:50 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration