Page 1 of 4 123 ... LastLast
Results 1 to 10 of 37

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

  1. #1
    Join Date
    Feb 2008
    Location
    Cornwall, UK
    Beans
    140
    Distro
    Ubuntu 22.04 Jammy Jellyfish

    Unable to access Windows shares on an all Lucid network

    I marked this solved when I discovered, after much reconfiguring, I had a faulty Netgear router - I just thought I'd save you reading all this to find the answer. Cheers

    I have 3 machines at home all running Lucid. All have Samba and shared folders but I can't access files on any machine from any other. This worked ok when they were running Karmic. I'm also unable to set up printing across the network from the two machines without local printers. The main machine has 2 printers connected via USB, the others are using WiFi. I'm not using firewalls on any machine.

    Filesharing
    On any machine I go to Places, Network and Nautilus opens at network:/// and shows me 'Windows Network' I open that and see the Workgroup folder which I open and see the folder is empty. (I did see the 3 machines before I completely removed Samba and re-installed a few minutes ago)

    Printing
    On one of the remote machines I go to Add Printer, Select Device, Network Printer, Windows Printer via Samba, Browse but I can't see the machine with the printers attached in the Workgroup. Another clue is that when I look at the printer properties, policies on the main machine all 3 boxes are ticked, Enabled, Accepting jobs (but it says Not published) and Shared.

    Basically guys, the more things I try the worse it gets. Can someone put me right?
    Last edited by Mylorharbour; January 12th, 2011 at 01:42 AM.

  2. #2
    Join Date
    Dec 2009
    Beans
    6,767

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

    Pick one machine ... say the one with the printer ... and make sure the following services are running:
    Code:
    sudo service cups status
    sudo service nmbd status
    sudo service smbd status
    If any of them are not running start them:
    Code:
    sudo service cups start
    sudo service nmbd start
    sudo service smbd start
    Check to see if anything has changed and if not post the output of the following commands:
    Code:
    smbtree
    Code:
    net usershare info
    Code:
    testparm -s

  3. #3
    Join Date
    Dec 2009
    Beans
    Hidden!

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

    please post the output of the following commands:
    Code:
    cat /etc/samba/smb.conf
    
    
    nmblookup -A 192.168.1.0/24 # assuming your gateway is 192.168.1.1, adjust appropriately
    
    smbclient -L {one of the hostnames from previous command} -I {that machine's ip}

  4. #4
    Join Date
    Feb 2008
    Location
    Cornwall, UK
    Beans
    140
    Distro
    Ubuntu 22.04 Jammy Jellyfish

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

    Morbius1,
    Some output for you.....

    Status of Common Unix Printing System: cupsd is running.
    roy@HPdc7700:~$ sudo service nmbd status
    nmbd start/running, process 992
    roy@HPdc7700:~$ sudo service smbd status
    smbd start/running, process 866
    roy@HPdc7700:~$ smbtree
    Enter roy's password:
    WORKGROUP
    \\HPDC7700 HPdc7700 server (Samba, Ubuntu)
    \\HPDC7700\shared
    \\HPDC7700\IPC$ IPC Service (HPdc7700 server (Samba, Ubuntu))
    \\HPDC7700\print$ Printer Drivers
    \\DELL-INSPIRON-L Dell-Inspiron-Laptop server (Samba, Ubuntu)
    cli_start_connection: failed to connect to DELL-INSPIRON-L<20> (0.0.0.0). Error NT_STATUS_UNSUCCESSFUL
    roy@HPdc7700:~$
    roy@HPdc7700:~$ net usershare info
    roy@HPdc7700:~$
    roy@HPdc7700:~$ testparm -s
    Load smb config files from /etc/samba/smb.conf
    rlimit_max: rlimit_max (1024) below minimum Windows limit (16384)
    Processing section "[printers]"
    Global parameter usershare allow guests found in service section!
    Processing section "[printers]"
    Processing section "[print$]"
    Loaded services file OK.
    Server role: ROLE_STANDALONE
    [global]
    server string = %h server (Samba, Ubuntu)
    map to guest = Bad User
    obey pam restrictions = Yes
    pam password change = Yes
    passwd program = /usr/bin/passwd %u
    passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
    unix password sync = Yes
    syslog = 0
    log file = /var/log/samba/log.%m
    max log size = 1000
    dns proxy = No
    panic action = /usr/share/samba/panic-action %d

    [printers]
    comment = All Printers
    path = /var/spool/samba
    create mask = 0700
    printable = Yes
    browseable = No
    browsable = No

    [print$]
    comment = Printer Drivers
    path = /var/lib/samba/printers

  5. #5
    Join Date
    Feb 2008
    Location
    Cornwall, UK
    Beans
    140
    Distro
    Ubuntu 22.04 Jammy Jellyfish

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

    d3v1150m471c,
    Some for you too. How do I go about finding gateways and IPs?

    oy@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
    path = /var/spool/samba
    browseable = no
    printable = yes

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

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

  6. #6
    Join Date
    Dec 2009
    Beans
    6,767

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

    [1] Well, for one thing you have no shares defined.

    "net usershare info" would have told us how your usershares or nautilus-shares are defined and the output os null. And testparm -s would have told us if you have any classic shares and there aren't any of those either.

    [2] If you're going to use Samba as pass-through to cups you need to make a modification of your smb.conf:
    [printers]
    comment = All Printers
    browseable = no
    path = /var/spool/samba
    printable = yes
    guest ok = yes
    read only = yes
    create mask = 0700
    [3] Your machine name is too long
    \\DELL-INSPIRON-L Dell-Inspiron-Laptop server (Samba, Ubuntu)
    cli_start_connection: failed to connect to DELL-INSPIRON-L<20> (0.0.0.0). Error NT_STATUS_UNSUCCESSFUL
    By default samba will use the hostname to anounce itself to the network but it has to be less than or equal to 15 characters in length.

    The fastest way to fix this is to add a line to the [global] section of smb.conf:
    Code:
    netbios name = Dell-Laptop
    It doesn't have to be that exact name but make it <= 15 characters in length.
    EDIT: Sorry, I should have been clearer about where to make that change. It should be none on Dell-Inspiron-Laptop's smb.conf not on HPdc7700.

    Then restart samba:
    Code:
    sudo service smbd restart
    Last edited by Morbius1; October 26th, 2010 at 09:38 PM.

  7. #7
    Join Date
    Dec 2009
    Beans
    6,767

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

    There are two things from your output that I just can't figure out:

    [1] "net usershare" and testparm show no shares yet smbtree show this:
    \\HPDC7700\shared
    Is that by any chance the printer? Or did you create a nautilus-share as root. If you do the following command do you get an output:
    Code:
    sudo net usershare info
    [2] testparm error:
    Global parameter usershare allow guests found in service section!
    For the life of me the only reference to it in your smb.conf is where it should be.

  8. #8
    Join Date
    Dec 2009
    Beans
    Hidden!

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

    Code:
    ifconfig # will tell you your ip
    your router's ip address is your gateway. don't mistake this for your modem. if you don't know your router's ip you can right-click your network tray icon and go into connection information (while connected) and it will be your "default route". it'll probably be something like 192.168.1.1

    please see my responses on this thread as it may tell you what you need to know.

    http://ubuntuforums.org/showthread.php?p=10022515#post10022515


    it contains my additions to smb.conf (that file is otherwise not modified) and I touched on nautilus-share as well. i use my firewall to manage my samba security because it's easier especially with the dhcp on my network and sometimes the windows machines i share with have a myocardial infarction when they've encountered my samba security in the past.

  9. #9
    Join Date
    Feb 2008
    Location
    Cornwall, UK
    Beans
    140
    Distro
    Ubuntu 22.04 Jammy Jellyfish

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

    Quote Originally Posted by d3v1150m471c View Post
    please post the output of the following commands:
    Code:
    cat /etc/samba/smb.conf
    
    
    nmblookup -A 192.168.1.0/24 # assuming your gateway is 192.168.1.1, adjust appropriately
    
    smbclient -L {one of the hostnames from previous command} -I {that machine's ip}
    Hmmm.... My router's address is 192.168.0.1. Is that the gateway you refer to? I have a couple of listing but I don't think they're what you're after:

    roy@HPdc7700:~$ nmblookup -A 192.168.0.0/24
    Looking up status of 0.0.0.0
    HPDC7700 <00> - B <ACTIVE>
    HPDC7700 <03> - B <ACTIVE>
    HPDC7700 <20> - B <ACTIVE>
    ..__MSBROWSE__. <01> - <GROUP> B <ACTIVE>
    WORKGROUP <1d> - B <ACTIVE>
    WORKGROUP <1e> - <GROUP> B <ACTIVE>
    WORKGROUP <00> - <GROUP> B <ACTIVE>

    MAC Address = 00-00-00-00-00-00

    roy@HPdc7700:~$ nmblookup -A 192.168.1.0/24
    Looking up status of 0.0.0.0
    HPDC7700 <00> - B <ACTIVE>
    HPDC7700 <03> - B <ACTIVE>
    HPDC7700 <20> - B <ACTIVE>
    ..__MSBROWSE__. <01> - <GROUP> B <ACTIVE>
    WORKGROUP <1d> - B <ACTIVE>
    WORKGROUP <1e> - <GROUP> B <ACTIVE>
    WORKGROUP <00> - <GROUP> B <ACTIVE>

    MAC Address = 00-00-00-00-00-00

  10. #10
    Join Date
    Feb 2008
    Location
    Cornwall, UK
    Beans
    140
    Distro
    Ubuntu 22.04 Jammy Jellyfish

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

    Sorry guys I'm about to lose access this machine. The shift worker's arrived home and it's in her bedroom. I'll pick this up again in the morning. Cheers.

Page 1 of 4 123 ... LastLast

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
  •