Results 1 to 3 of 3

Thread: Samba Problem

  1. #1

    Samba Problem

    I am new to Linux.I have P-IV 512 RAM,40 Gb HDD,I had installed Linux 7.2 with 4024 /hda1 and 15 Gb to /data and 512 to swap.Now Iwant to join the system to my present working system on network.I have Windows 2000 server and 98/95 Clients.

    Now I ahd confiured my Smb.conf on linux and joined it to domain also but now It is asking for password when I click the Linux System On network.what could be the cause.I am sending my hole smb.conf plz some body help me out this.

    Is it I am missing any command or missing anything else to configure......etc.


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

    # server string is the equivalent of the NT Description field
    server string = Live 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 HOWTO Collection for details.
    security = domain

    # 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

    # 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 = /usr/local/samba/var/log.%m

    # 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

    # 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

    # 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

    # 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 -n -g machines -c Machine -d /dev/null -s /bin/false %u
    delete user script = /usr/sbin/userdle %u
    delete user from group script = /usr/sbin/deluser %u %g
    delete group script = /usr/sbin/groupdel %g

    #============================ Share Definitions ==============================
    comment = Home Directories
    browseable = no
    writable = yes

    # 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 = no
    ; 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
    path = /usr/spool/samba
    browseable = no
    # Set public = yes to allow user 'guest account' to print
    guest ok = no
    writable = no
    printable = yes

    # This one is useful for people to share files
    ; comment = Temporary file space
    ; path = /tmp
    ; read only = no
    ; public = yes

    # A publicly accessible directory, but read only, except for people in
    # the "staff" group
    ; comment = Public Stuff
    ; path = /home/samba
    ; public = yes
    ; writable = yes
    ; printable = no
    ; write list = @staff

    # Other examples.
    # A private printer, usable only by fred. Spool data will be placed in fred's
    # home directory. Note that fred must have write access to the spool directory,
    # wherever it is.
    ; comment = Fred's Printer
    ; valid users = fred
    ; path = /homes/fred
    ; printer = freds_printer
    ; public = no
    ; writable = no
    ; printable = yes

    # A private directory, usable only by fred. Note that fred requires write
    # access to the directory.
    comment = data
    path = /data
    valid users = administrator,User
    admin users = administrator
    public = no
    writable = yes
    printable = no
    create mode = 767
    force create mode = 767
    ; create mask = 0775
    directory mode = 0767
    force directory mode = 767
    ; delete veto files = no
    share modes = yes

    # a service which has a different directory for each machine that connects
    # this allows you to tailor configurations to incoming machines. You could
    # also use the %U option to tailor it by user name.
    # The %m gets replaced with the machine name that is connecting.
    ; comment = PC Directories
    ; path = /usr/pc/%m
    ; public = no
    ; writable = yes

    # A publicly accessible directory, read/write to all users. Note that all files
    # created in the directory by users will be owned by the default user, so
    # any user with access can delete any other user's files. Obviously this
    # directory must be writable by the default user. Another user could of course
    # be specified, in which case all files would be owned by that user instead.
    ; path = /usr/somewhere/else/public
    ; public = yes
    ; only guest = yes
    ; writable = yes
    ; printable = no

    # The following two entries demonstrate how to share a directory so that two
    # users can place files there that will be owned by the specific users. In this
    # setup, the directory should be writable by both users and should have the
    # sticky bit set on it to prevent abuse. Obviously this could be extended to
    # as many users as required.
    ; comment = Mary's and Fred's stuff
    ; path = /usr/somewhere/shared
    ; valid users = mary fred
    ; public = no
    ; writable = yes
    ; printable = no
    ; create mask = 0765

  2. #2
    Join Date
    Jul 2004

    see following are the changes required for perfect use

    1) workgroup name in smb.conf file should be same as your windows domain/workgroup name.

    2)create some users on linux system using useradd command.

    3)create corresponing samba user for your linux users ,
    examle if u have created user as "user1" then to create samba user give command as

    smbadduser user1:user1

    then specify the password for user1.

    also create user on windows machine with same username and password .

    if u r not sure about ur iptable setting then stop iptable service.

    now log in to windows sytem with username as user1 and access
    your linux machine.

    All the best


  3. #3
    Join Date
    Oct 2004
    North Carolina (Triangle area)

    how secure is this server going to be?

    I believe you could also add the guest = OK directive to the global section. However, it is a fairly large security issue unless you dont mind so much.

Similar Threads

  1. Slackware 12 and Samba Problem
    By johnmann in forum Linux - Hardware, Networking & Security
    Replies: 7
    Last Post: 03-27-2008, 07:44 PM
  2. Problem with Samba, Please help me...
    By Muhammad A. Husain in forum General Chat
    Replies: 1
    Last Post: 10-29-2007, 07:52 PM
  3. Samba Problem
    By imported_turishi007 in forum Linux - Software, Applications & Programming
    Replies: 4
    Last Post: 07-20-2004, 06:10 AM
  4. samba problem, browsing
    By pasholy in forum Linux - Hardware, Networking & Security
    Replies: 2
    Last Post: 08-20-2002, 05:11 AM
  5. Samba problem - Can not ping
    By lhvan in forum Linux - Hardware, Networking & Security
    Replies: 3
    Last Post: 07-10-2002, 04:22 PM


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts