Find the answer to your Linux question:
Results 1 to 9 of 9
Hi 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 ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Jun 2004
    Posts
    4

    Samba Trouble


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

    Thanks
    Turishi
    [global]

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

    # server string is the equivalent of the NT Description field
    server string = MEDIA 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 = 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

    # 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 ==============================
    [homes]
    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
    ;[Profiles]
    ; 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
    [printers]
    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
    ;[tmp]
    ; 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
    ;[public]
    ; 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.
    ;[fredsprn]
    ; 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.
    [Test]
    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.
    ;[pchome]
    ; 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.
    ;[public]
    ; 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.
    ;[myshare]
    ; 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
    Linux Guru
    Join Date
    Oct 2001
    Location
    Täby, Sweden
    Posts
    7,578
    I don't really see the problem. Should it not be asking for a password? I mean, you don't want people to just be able to log into it without a password, right?

  3. #3
    Just Joined!
    Join Date
    Jun 2004
    Posts
    4

    Samba

    Hi Dolda,

    Your are right but after giving the username and password also it is not getting me in.

    Can you tell me what all commands should I use to configure it properly means i.e
    1) 1st I downloaded latest samba i.e samba 3.0.4
    2) I run tar zxvf samba.3.0.4.tar.gz
    3) I run ./configure
    4) I run make
    5) I run make install
    6) I run 2 files ./smbd and ./nmbd
    7) I run ./net rpc join -U administrator to join domain.
    8) Finally I added these to files in rc.local.

    Now did I missed any else to configure or add some where.

    thanks
    Rishi

  4. #4
    Linux Guru
    Join Date
    Oct 2001
    Location
    Täby, Sweden
    Posts
    7,578
    Oh, now that's another issue, isn't it? =)

    The probably reason is that you're either not using encrypted passwords, or you haven't added the password hashes to your smbpasswd.

    First of all make sure that your smb.conf is set up to use encrypted passwords. Then, if it is, use the smbpasswd program to enable users for Samba.

  5. #5
    Just Joined!
    Join Date
    Jun 2004
    Posts
    4

    Samba

    Hi Dolda

    How can I do that now can u tell me the commands for that

    Thanks

    Rishi

  6. #6
    Linux Guru
    Join Date
    Oct 2001
    Location
    Täby, Sweden
    Posts
    7,578
    Well, the smb.conf is an ordinary text file, so just edit that one with whatever text editor you prefer. Common text editor alternatives include nano, pico, joe, emacs, xemacs, jmacs, vi, gedit and kedit. Choose whichever you like the best. gedit is for GNOME, kedit is for KDE, the rest are mainly command line editors, nano and pico being preferred by beginners.

    As for smbpasswd, that is the command. I don't deal with Samba that very often (since I, fortunately, don't have any Windows computers =) ), but if I recall correctly, you enable a user like this:
    Code:
    smbpasswd -a username
    username, of course, being the actual name of the user. Then type the password for that user.
    I'm not sure about that though - like I said, I don't have any Windows computers, so it has been some time since I last dealt with this. See the manpage for details (run "man smbpasswd").

  7. #7
    Linux User
    Join Date
    Jan 2003
    Location
    Cardiff, Wales
    Posts
    478

    samba

    new versions of samba support more than the simple smbpasswd utility. they should be managed as root through the command pdbedit

    check out the man page for it. I don;t want to give you instructions that could break stuff.

    You will need to add all of your users into the samba server or use a force user directive in each of the shares.
    No trees were harmed during the creation of this message. Its made from a blend of elephant tusk and dolphin meat.

  8. #8
    Just Joined!
    Join Date
    Jun 2004
    Posts
    8

    Its an older smb.conf...but it'll have to do until i update

    http://teddymills.myknet.org/d/smb.conf.txt

    It will work on newer Sambas 2.28..and should work even on Samba 3.x..

    I will post the newer one tommorow...

  9. #9
    Linux Newbie
    Join Date
    Dec 2003
    Location
    Netherlands
    Posts
    193
    allright i've seen your problem.

    password server = *

    you need the rule above.

    If i understand it well, you are running this one as fileserver. You don't need the add user/group/machine scripts, also you don't need the delete scripts.
    Computers Are Like Air Conditioners... They\'re both useless with Windows open!

Posting Permissions

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