Find the answer to your Linux question:
Results 1 to 4 of 4
i have been trying to use samba to connect to a local network, i used kde control center to set it up, and it once, by some miracle that i ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Dec 2006
    Posts
    85

    cant get windows machine to log onto samba server


    i have been trying to use samba to connect to a local network, i used kde control center to set it up, and it once, by some miracle that i am unaware of...worked..then i made a change to give write access...and the whole thing stopped working again. i changed it back to no avail.
    in a hopes to get better luck by simplifying i replaced the .conf with a simpler .conf (but kept the original just in case) though none of the changes i have done have been seen on the other machine.

    the network sees my server...but...cant connect. whats more the changes made are not seen, even after rebooting both computers.

    here is the current .conf:

    Code:
    [global]
    workgroup = workgroup
    netbios name = samba
    restrict anonymous = no
    domain master = no
    preferred master = no
    max protocol = NT
    acl compatibility = 
    ldap ssl = No
    server signing = Auto
    
    [homes]
    read only = no
    browseable = no
    
    [music]
    path = /mnt/hdb1/
    write list = austin,root
    
    [everyone]
    path = /
    read only = no
    
    [apps]
    path = /usr/bin/
    valid users = @admins,austin,root
    write list = @admins,austin,root
    simple, at this point i care more about functional than secure...i can secure it later..

    the old one looks like this

    Code:
    #
    # Sample configuration file for the Samba suite for Debian GNU/Linux.
    #
    #
    # This is the main Samba configuration file. You should read the
    # smb.conf(5) manual page in order to understand the options listed
    # here. Samba has a huge number of configurable options most of which
    # are not shown in this example
    #
    # Any line which starts with a ; (semi-colon) or a # (hash)
    # is a comment and is ignored. In this example we will use a #
    # for commentary and a ; for parts of the config file that you
    # may wish to enable
    #
    # NOTE: Whenever you modify this file you should run the command
    # "testparm" to check that you have not made any basic syntactic
    # errors.
    #
    
    #======================= Global Settings =======================
    
    [global]
    
    ## Browsing/Identification ###
    
    # Change this to the workgroup/NT-domain name your Samba server will part of
    
    
    # server string is the equivalent of the NT Description field
    
    
    # Windows Internet Name Serving Support Section:
    # WINS Support - Tells the NMBD component of Samba to enable its WINS Server
    ;   wins support = 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 = w.x.y.z
    
    # This will prevent nmbd to search for NetBIOS names through DNS.
    dns proxy = no
    
    # What naming service and in what order should we use to resolve host names
    # to IP addresses
    ;   name resolve order = lmhosts host wins bcast
    
    #### Networking ####
    
    # The specific set of interfaces / networks to bind to
    # This can be either the interface name or an IP address/netmask;
    # interface names are normally preferred
    ;   interfaces = 127.0.0.0/8 eth0
    
    # Only bind to the named interfaces and/or networks; you must use the
    # 'interfaces' option above to use this.
    # It is recommended that you enable this feature if your Samba machine is
    # not protected by a firewall or is a firewall itself.  However, this
    # option cannot handle dynamic or non-broadcast interfaces correctly.
    ;   bind interfaces only = true
    
    
    
    #### Debugging/Accounting ####
    
    # This tells Samba to use a separate log file for each machine
    # that connects
    log file = /var/log/samba/log.%m
    
    # Put a capping on the size of the log files (in Kb).
    max log size = 1000
    
    # If you want Samba to only log through syslog then set the following
    # parameter to 'yes'.
    ;   syslog only = no
    
    # We want Samba to log a minimum amount of information to syslog. Everything
    # should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
    # through syslog you should set the following parameter to something higher.
    syslog = 0
    
    # Do something sensible when Samba crashes: mail the admin a backtrace
    panic action = /usr/share/samba/panic-action %d
    
    
    ####### Authentication #######
    
    # "security = user" is always a good idea. This will require a Unix account
    # in this server for every user accessing the server. See
    # /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
    # in the samba-doc package for details.
    ;   security = user
    
    # You may wish to use password encryption.  See the section on
    # 'encrypt passwords' in the smb.conf(5) manpage before enabling.
    encrypt passwords = yes
    
    # If you are using encrypted passwords, Samba will need to know what
    # password database type you are using.
    passdb backend = tdbsam
    
    obey pam restrictions = no
    
    ;   guest account = nobody
    invalid users = root
    
    # This boolean parameter controls whether Samba attempts to sync the Unix
    # password with the SMB password when the encrypted SMB password in the
    # passdb is changed.
       unix password sync = yes
    
    # For Unix password sync to work on a Debian GNU/Linux system, the following
    # parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
    # sending the correct chat script for the passwd program in Debian Sarge).
    passwd program = /usr/bin/passwd %u
    passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n *password\supdated\ssuccessfully* .
    
    # This boolean controls whether PAM will be used for password changes
    # when requested by an SMB client instead of the program listed in
    # 'passwd program'. The default is 'no'.
    ;   pam password change = no
    
    ########## Domains ###########
    
    # Is this machine able to authenticate users. Both PDC and BDC
    # must have this setting enabled. If you are the BDC you must
    # change the 'domain master' setting to no
    #
    ;   domain logons = yes
    #
    # The following setting only takes effect if 'domain logons' is set
    # It specifies the location of the user's profile directory
    # from the client point of view)
    # The following required a [profiles] share to be setup on the
    # samba server (see below)
    ;   logon path = \\%N\profiles\%U
    # Another common choice is storing the profile in the user's home directory
    ;   logon path = \\%N\%U\profile
    
    # The following setting only takes effect if 'domain logons' is set
    # It specifies the location of a user's home directory (from the client
    # point of view)
    ;   logon drive = H:
    ;   logon home = \\%N\%U
    
    # The following setting only takes effect if 'domain logons' is set
    # It specifies the script to run during logon. The script must be stored
    # in the [netlogon] share
    # NOTE: Must be store in 'DOS' file format convention
    ;   logon script = logon.cmd
    
    # This allows Unix users to be created on the domain controller via the SAMR
    # RPC pipe.  The example command creates a user account with a disabled Unix
    # password; please adapt to your needs
    ; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u
    
    ########## Printing ##########
    
    # If you want to automatically load your printer list rather
    # than setting them up individually then you'll need this
    ;   load printers = yes
    
    # lpr(ng) printing. You may wish to override the location of the
    # printcap file
    ;   printing = bsd
    ;   printcap name = /etc/printcap
    
    # CUPS printing.  See also the cupsaddsmb(8) manpage in the
    # cupsys-client package.
    ;   printing = cups
    ;   printcap name = cups
    
    # When using [print$], root is implicitly a 'printer admin', but you can
    # also give this right to other users to add drivers and set printer
    # properties
    ;   printer admin = @ntadmin
    
    
    ############ Misc ############
    
    # 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
    ;   include = /home/samba/etc/smb.conf.%m
    
    # Most people will find that this option gives better performance.
    # See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
    # for details
    # You may want to add the following on a Linux system:
    #         SO_RCVBUF=8192 SO_SNDBUF=8192
    socket options = TCP_NODELAY 
    restrict anonymous = no
    domain master = no
    preferred master = no
    max protocol = NT
    acl compatibility = 
    ldap ssl = No
    server signing = Auto
    map to guest = Bad User
    guest account = austin
    guest ok = yes
    security = share
    paranoid server security = no
    debug uid = yes
    local master = no
    debug pid = yes
    syslog only = yes
    
    netbios name = funstuff
    null passwords = yes
    
    # The following parameter is useful only if you have the linpopup package
    # installed. The samba maintainer and the linpopup maintainer are
    # working to ease installation and configuration of linpopup and samba.
    ;   message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &
    
    # Domain Master specifies Samba to be the Domain Master Browser. If this
    # machine will be configured as a BDC (a secondary logon server), you
    # must set this to 'no'; otherwise, the default behavior is recommended.
    ;   domain master = auto
    
    # Some defaults for winbind (make sure you're not using the ranges
    # for something else.)
    ;   idmap uid = 10000-20000
    ;   idmap gid = 10000-20000
    ;   template shell = /bin/bash
    ;
    ; The following was the default behaviour in sarge
    ; but samba upstream reverted the default because it might induce
    ; performance issues in large organizations
    ; See #368251 for some of the consequences of *not* having
    ; this setting and smb.conf(5) for all details
    ;
    ;   winbind enum groups = yes
    ;   winbind enum users = yes
    
    #======================= Share Definitions =======================
    
    [homes]
    comment = Home Directories
    
    # File creation mask is set to 0700 for security reasons. If you want to
    # create files with group=rw permissions, set next parameter to 0775.
    create mask = 0775
    
    # Directory creation mask is set to 0700 for security reasons. If you want to
    # create dirs. with group=rw permissions, set next parameter to 0775.
    directory mask = 0775
    
    # Restrict access to home directories
    # to the one of the authenticated user
    # This might need tweaking when using external authentication schemes
    valid users = %S
    force user = austin
    force group = austin
    case sensitive = no
    strict locking = no
    msdfs proxy = no
    
    # Un-comment the following and create the netlogon directory for Domain Logons
    # (you need to configure Samba to act as a domain controller too.)
    ;[netlogon]
    ;   comment = Network Logon Service
    ;   path = /home/samba/netlogon
    ;   guest ok = yes
    ;   writable = yes
    ;   share modes = no
    
    # Un-comment the following and create the profiles directory to store
    # users profiles (see the "logon path" option above)
    # (you need to configure Samba to act as a domain controller too.)
    # The path below should be writable by all users so that their
    # profile directory may be created the first time they log on
    ;[profiles]
    ;   comment = Users profiles
    ;   path = /home/samba/profiles
    ;   guest ok = no
    ;   browseable = no
    ;   create mask = 0600
    ;   directory mask = 0700
    
    [printers]
    comment = All Printers
    browseable = no
    path = /var/spool/samba
    printable = yes
    create mask = 0700
    
    # Windows clients look for this share name as a source of downloadable
    # printer drivers
    [print$]
    comment = Printer Drivers
    path = /var/lib/samba/printers
    
    [linux2]
    path = /mnt/hdb1/
    hide files =
    veto files =
    case sensitive = no
    strict locking = no
    msdfs proxy = no
    read list = root
    invalid users = 
    
    [anything]
    case sensitive = no
    strict locking = no
    msdfs proxy = no
    hosts allow = The-gfhsopf946c
    path = /home/austin/
    read only = no
    admin users = root
    invalid users = 
    
    [linux]
    path = /
    case sensitive = no
    strict locking = no
    msdfs proxy = no
    now the old one had netbios name "funstuff" while the current one has netbios name "samba" but "funstuff" is whats showing up...
    though it does prompt for a password now rather than just saying it cant get access...it may be that i have no smbusers in /etc/samba...though i do have a pass in /etc/samba/smbpasswd along with a username, which matches the username and pass of the logging on machine...is that enough?

    add to that, before i was able to connect to files on the other computers server, now i cant even do that.

    does this make sense? can someone please help?

    --edit--
    ok, i can log in as guest (once i told it that was fine) but my computer still cant get out to the network to get files from them. i can transmit my files, they can recieve (though...it isnt secure..big security risk..) but i cant get on the other network places...the server times out. so now...hopefully...the problem is small.
    also...i dont want these people who log on to see my hiden files...they show as being hidden...but i dont even want them to SEE them as hidden or even existant...can i do that?
    Last edited by the_ultimate_samurai; 09-06-2007 at 11:30 PM. Reason: fixed it a bit...

  2. #2
    Just Joined!
    Join Date
    Sep 2006
    Location
    Rochester
    Posts
    17

    samba configurations

    The thing that jumps out at first glance is the missing value after "acl compatibility". I don't know if that will make any difference, but try it.

    When I set up my samba machine, I started out with simple a set up as possible. Set up a directory for samba to share and leave out as much as you can. restart samba with "/sbin/service smb restart" afer every change you make to the smb.conf file.

    Some things I have found:
    1) always backup the file BEFORE you change it
    2) only change 1 thing at a time.
    3) when you get a "working" smb.conf, save it as smb.conf.works

    I don't know how many times I have made a couple of simple, minor changes and found that I had just screwed up.... usually big time.

    I can tell you how I have my samba setup if you want.

    Hope you get it working!

  3. #3
    Linux Newbie jnike's Avatar
    Join Date
    Sep 2006
    Location
    UK
    Posts
    120

    cant get windows machine to log onto samba server

    the_ultimate_samurai,

    I have just seen your thread and wondered the following ;

    a. The netbios name is this the name of the server or is this meant to be the name of the samba share?

    b. The following entry:
    [homes]
    read only = no
    browseable = no


    may have to be:
    [homes]
    read only = Yes (Yes, only read access, with No write)
    browseable = yes (Yes, to browseable to be seen by all)



    c. The following:

    [everyone]
    path = /
    read only = no (means read access with write)

    should maybe read:

    [everyone]
    path = /<Path of samba directory being shared> HERE!!
    read only = yes (Yes, only read access, with No write)

    I would also check the permissions on the samba shares, ie the directories being shared from your Linux server.

    I hope this is helpful...

    Jnike

  4. $spacer_open
    $spacer_close
  5. #4
    Just Joined!
    Join Date
    Sep 2007
    Location
    Philadelphia, PA
    Posts
    16
    Here's a blog entry I wrote about some of my experiences setting up a Samba server:

    Something GNU: Samba Server

    Maybe it will be useful to you. By the way, is there a reason you're sharing your root directory? That seems dangerous, both from a security standpoint and in the interest of preventing catastrophic accidents.

Posting Permissions

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