Page 4 of 4 FirstFirst ... 234
Results 31 to 37 of 37

Thread: Unable to access Windows shares on an all Lucid network

  1. #31
    Join Date
    Dec 2009
    Beans
    5,736

    Re: Unable to access Windows shares on an all Lucid network

    Post your entire smb.conf file please:

    Code:
    cat /etc/samba/smb.conf

  2. #32
    Join Date
    Feb 2008
    Location
    Cornwall, UK
    Beans
    124
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Unable to access Windows shares on an all Lucid network

    smb.conf as requested:

    roy@HPdc7700:~$ cat /etc/samba/smb.conf
    #
    # 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
    #
    # Some options that are often worth tuning have been included as
    # commented-out examples in this file.
    # - When such options are commented with ";", the proposed setting
    # differs from the default Samba behaviour
    # - When commented with "#", the proposed setting is the default
    # behaviour of Samba but the option is considered important
    # enough to be mentioned here
    #
    # NOTE: Whenever you modify this file you should run the command
    # "testparm" to check that you have not made any basic syntactic
    # errors.
    # A well-established practice is to name the original file
    # "smb.conf.master" and create the "real" config file with
    # testparm -s smb.conf.master >smb.conf
    # This minimizes the size of the really used smb.conf file
    # which, according to the Samba Team, impacts performance
    # However, use this with caution if your smb.conf file contains nested
    # "include" statements. See Debian bug #483187 for a case
    # where using a master file is not a good idea.
    #

    #======================= Global Settings =======================


    ## Browsing/Identification ###

    # Change this to the workgroup/NT-domain name your Samba server will part of
    workgroup = WORKGROUP

    # server string is the equivalent of the NT Description field
    server string = %h server (Samba, Ubuntu)

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



    #### Debugging/Accounting ####

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

    # Cap the size of the individual log files (in KiB).
    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 = true

    # If you are using encrypted passwords, Samba will need to know what
    # password database type you are using.
    passdb backend = tdbsam

    obey pam restrictions = yes

    # 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\s*\spassword:* %n\n *Retype\snew\s*\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 = yes

    # This option controls how unsuccessful authentication attempts are mapped
    # to anonymous connections
    map to guest = bad user

    ########## 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
    # (this is Samba's default)
    # 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

    # This allows machine accounts to be created on the domain controller via the
    # SAMR RPC pipe.
    # The following assumes a "machines" group exists on the system
    ; add machine script = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

    # This allows Unix groups to be created on the domain controller via the SAMR
    # RPC pipe.
    ; add group script = /usr/sbin/addgroup --force-badname %g

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

    [ printers]

    comment = All Printers
    browseable = no
    path = /var/spool/samba
    printable = yes
    guest ok = yes
    read only = yes
    create mask = 0700

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

    # 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 Debian bug #368251 for some of the consequences of *not*
    # having this setting and smb.conf(5) for details.
    ; winbind enum groups = yes
    ; winbind enum users = yes

    # Setup usershare options to enable non-root users to share folders
    # with the net usershare command.

    # Maximum number of usershare. 0 (default) means that usershare is disabled.
    ; usershare max shares = 100

    # Allow users who've been granted usershare privileges to create
    # public shares, not just authenticated ones
    usershare allow guests = yes
    force user = roy
    usershare owner only = false


    #======================= Share Definitions =======================

    # Un-comment the following (and tweak the other settings below to suit)
    # to enable the default home directory shares. This will share each
    # user's home directory as \\server\username
    ;[homes]
    ; comment = Home Directories
    ; browseable = no

    # By default, the home directories are exported read-only. Change the
    # next parameter to 'no' if you want to be able to write to them.
    ; read only = yes

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

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

    # By default, \\server\username shares can be connected to by anyone
    # with access to the samba server. Un-comment the following parameter
    # to make sure that only "username" can connect to \\server\username
    # This might need tweaking when using external authentication schemes
    ; valid users = %S

    # 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
    ; read only = 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
    guest ok = no
    read only = 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
    browseable = yes
    read only = yes
    guest ok = no
    # Uncomment to allow remote administration of Windows print drivers.
    # You may need to replace 'lpadmin' with the name of the group your
    # admin users are members of.
    # Please note that you also need to set appropriate Unix permissions
    # to the drivers directory for these users to have write rights in it
    ; write list = root, @lpadmin

    # A sample share for sharing your CD-ROM with others.
    ;[cdrom]
    ; comment = Samba server's CD-ROM
    ; read only = yes
    ; locking = no
    ; path = /cdrom
    ; guest ok = yes

    # The next two parameters show how to auto-mount a CD-ROM when the
    # cdrom share is accesed. For this to work /etc/fstab must contain
    # an entry like this:
    #
    # /dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 0 0
    #
    # The CD-ROM gets unmounted automatically after the connection to the
    #
    # If you don't want to use auto-mounting/unmounting make sure the CD
    # is mounted on /cdrom
    #
    ; preexec = /bin/mount /cdrom
    ; postexec = /bin/umount /cdrom

    roy@HPdc7700:~$


    It's been a very long day Morbius. Take your time, I'll be back online tomorrow. Thanks

  3. #33
    Join Date
    Dec 2009
    Beans
    5,736

    Re: Unable to access Windows shares on an all Lucid network

    I ran a testparm on your smb.conf posting and once again i get these errors which just made no sense:
    Global parameter usershare allow guests found in service section!
    Global parameter usershare owner only found in service section!
    But I think I finally figured it out. Samba has a quirk in how it constructs and reads a share definition in smb.conf . It starts every share definition with a [sharename] but doesn't consider the share definition completed until it reads another [sharename].

    You have a [printers] share in the wrong place in smb.conf and samba is reading all the usershare parameters as being part of that share instead of reading it as part of the [global] settings.

    Go into smb.conf, find the following section, and put a # sign in front of the the [printers] share so that it looks like this:
    ########## 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( manpage in the
    # cupsys-client package.
    ; printing = cups
    ; printcap name = cups

    #[ printers]

    #comment = All Printers
    #browseable = no
    #path = /var/spool/samba
    #printable = yes
    #guest ok = yes
    #read only = yes
    #create mask = 0700
    While you're in smb.conf go down further until you reach the real [printers] share and change guest ok to yes:
    # 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
    guest ok = yes
    read only = yes
    create mask = 0700
    Save smb.conf and restart samba:
    Code:
    sudo service smbd restart

  4. #34
    Join Date
    Feb 2008
    Location
    Cornwall, UK
    Beans
    124
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Unable to access Windows shares on an all Lucid network

    Apologies Morbius but my wife's new netbook arrived and she wanted it setup to triple boot Win7, Lucid and Maverick. Done now so I'm back.

    Ok I did that before the netbook arrived but only now got to test it. Much the same I'm afraid. On the HP I can see the other machines when I go to Places, Network but when I click on them I get a window saying 'Opening "Dell-Laptop"' then after about 20 seconds an error message, 'Unable to Mount Location', 'Failed to retrieve share list from server'.

    On the Dell or on the new netbook booted into Maverick, when I go to Places, Network i see 'Windows Network', double-click that and I see 'Workgroup. Double-clicking that I see an 'Opening "Workgroup"' window then after about 20 seconds an error message, 'Unable to Mount Location', 'Failed to retrieve share list from server'.

    When trying to set up a printer from the Dell or the Samsung netbook I go to System, Admin, Printing, Select Device, Network Printer, Windows Printer via Samba, the SMB browser shows the Workgroup share but double-clicking on to doesn't do anything.
    Last edited by Mylorharbour; November 6th, 2010 at 01:45 AM. Reason: Added printer comment

  5. #35
    Join Date
    Feb 2008
    Location
    Cornwall, UK
    Beans
    124
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Unable to access Windows shares on an all Lucid network

    Well, yesterday I lost my sanity.

    Nearly eight hours following very useful networking threads and at each turn the situation got a little better. Then, when I was almost there........nothing! Nothing at all. Suddenly, when I was reconfiguring smb.conf on one machine not a single PC could see could see any other. How could that be? I went to bed depressed.

    Then today, Victory! Something that I didn't find on any networking thread popped into my head. Sometimes we get so engrossed with setting up Ubuntu we fail to check what else could be happening. Only 4 days ago I asked if it could be hardware related then promptly forgot about it but today I proved conclusively it was the router. I just swapped it for a different make and all the networking just burst into life.

    Suffice to say if anyone's having issues seeing other computers or printers on the network, especially if their router's a Netgear, they should have a good look at that as part of the diagnosis.

    Thanks all for your help. At least I now KNOW my network's set up correctly.

  6. #36
    Join Date
    Dec 2009
    Beans
    5,736

    Re: Unable to access Windows shares on an all Lucid network

    You know it would be very helpful if you could post the make and model of the netgear that didn't work and the make and model of the router that did work.

    I'm getting more convinced that a lot of problems people attribute to Samba are really networking problems and I have seen this "swapped out the routers and everything worked" phenomenon before.

  7. #37
    Join Date
    Feb 2008
    Location
    Cornwall, UK
    Beans
    124
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Unable to access Windows shares on an all Lucid network

    No probs Morbius.

    The failed router was a Netgear DG834PN about 3 years old but permanently left on of course. I came across a thread on the internet which mentioned these routers not showing all 'attached devices'. Devices, usually wireless, seem to go missing although they can still access the internet, other machines can't see them. Sure enough, when I looked at the attached devices some were missing from the list.

    The replacement was sent by my ISP when I signed up to a 12 month contract some months ago. It's a BT HomeHub 2.0. I'm not sure whether it's marketed outside the UK as but it must now be the most common router here as BT seem to give 'em away to anybody signing up whether they already have one or not. Wikipedia says 'This model is electronically identical to the Thomson Speedtouch TG797n.' BT are still the biggest phone line provider here.

    Thanks again.

Page 4 of 4 FirstFirst ... 234

Tags for this Thread

Bookmarks

Posting Permissions

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