Page 1 of 2 12 LastLast
Results 1 to 10 of 15

Thread: Samba running but workgroup not visible on LAN (timeout on ...)

  1. #1

    Default Samba running but workgroup not visible on LAN (timeout on ...)

    Not sure why, but now my samba shares are not visible over my LAN, but they are running at boot.

    The firewall is configured, runlevels have been set...

    I can't pinpoint when this started, but sometime early this week.

    The output from
    Code:
    service nmb status && service smb status
    is:
    Code:
    redirecting to systemctl                                                                                                                
    nmb.service - LSB: Samba NetBIOS naming service over IP                                                                                 
              Loaded: loaded (/etc/init.d/nmb)                                                                                              
              Active: active (running) since Tue, 21 Feb 2012 08:01:19 -0700; 1h 20min ago                                                  
             Process: 1666 ExecReload=/etc/init.d/nmb reload (code=exited, status=3/NOTIMPLEMENTED)                                         
             Process: 1648 ExecStart=/etc/init.d/nmb start (code=exited, status=0/SUCCESS)                                                  
              CGroup: name=systemd:/system/nmb.service                                                                                      
                      └ 1657 /usr/sbin/nmbd -D -s /etc/samba/smb.conf
    Code:
    smb.service - LSB: Samba SMB/CIFS file and print server
              Loaded: loaded (/etc/init.d/smb)
              Active: active (running) since Tue, 21 Feb 2012 08:01:14 -0700; 1h 20min ago
             Process: 1676 ExecReload=/etc/init.d/smb reload (code=exited, status=0/SUCCESS)
             Process: 1481 ExecStart=/etc/init.d/smb start (code=exited, status=0/SUCCESS)
              CGroup: name=systemd:/system/smb.service
                      ├ 1507 /usr/sbin/smbd -D -s /etc/samba/smb.conf
                      └ 1514 /usr/sbin/smbd -D -s /etc/samba/smb.conf
    If I navigate to smb://192.168.0.1 it says "Timeout on server 192.168.0.1" and doesn't load anything.

    Here is my smb.conf file contents:
    Code:
    # smb.conf is the main Samba configuration file. You find a full commented# version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE if the
    # samba-doc package is installed.
    # Date: 2012-02-02
    [global]
        workgroup = CAMERONECT
        netbios name = alien
        name resolve order = bcast host lmhosts wins
        passdb backend = tdbsam
        printing = cups
        printcap name = cups
        printcap cache time = 750
        cups options = raw
        use client driver = yes
        server string = ""
        map to guest = Bad User
        include = /etc/samba/dhcp.conf
        usershare allow guests = Yes
        usershare max shares = 100
        usershare owner only = False
        local master = yes
        os level = 33
    [homes]
        comment = Home Directories
        valid users = %S, %D%w%S
        browseable = No
        read only = No
        inherit acls = Yes
    
    
    ## Share disabled by YaST
    # [profiles]
    #    comment = Network Profiles Service
    #    path = %H
    #    read only = No
    #    store dos attributes = Yes
    #    create mask = 0600
    #    directory mask = 0700
    
    
    ## Share disabled by YaST
    # [users]
    #    comment = All users
    #    path = /home
    #    read only = No
    #    inherit acls = Yes
    #    veto files = /aquota.user/groups/shares/
    
    
    ## Share disabled by YaST
    # [groups]
    #    comment = All groups
    #    path = /home/groups
    #    read only = No
    #    inherit acls = Yes
    [printers]
        comment = All Printers
        path = /var/tmp
        printable = Yes
        create mask = 0600
        browseable = No
    [print$]
        comment = Printer Drivers
        path = /var/lib/samba/drivers
        write list = @ntadmin root
        force group = ntadmin
        create mask = 0664
        directory mask = 0775
    [smb]
        comment = smb public folder for alien
        path = /home/saultdon/smb
        guest ok = yes
    It's not until I run
    Code:
    rcnmb restart && rcsmb restart
    that I can navigate the shares and they show up.

    System info:
    openSUSE 12.1 x64, KDE 4.8.00, Linux 3.1.9-1.4
    Samba 3.6.3-89.1-2761

  2. #2
    Join Date
    Nov 2009
    Location
    ND, USA
    Posts
    1,069

    Default Re: Samba running but workgroup not visible on LAN (timeout on ...)

    On Tue February 21 2012 11:06 pm, saultdon wrote:

    >
    > Not sure why, but now my samba shares are not visible over my LAN, but
    > they are running at boot.
    >
    > The firewall is configured, runlevels have been set...
    >
    > I can't pinpoint when this started, but sometime early this week.
    >
    > The output from
    > Code:
    > --------------------
    > service nmb status && service smb status
    > --------------------
    > is:
    >
    > Code:
    > --------------------
    > redirecting to systemctl
    > nmb.service - LSB: Samba NetBIOS naming service over IP
    > Loaded: loaded (/etc/init.d/nmb)
    > Active: active (running) since Tue, 21 Feb 2012 08:01:19 -0700; 1h 20min

    ago
    > Process: 1666 ExecReload=/etc/init.d/nmb reload (code=exited,

    status=3/NOTIMPLEMENTED)
    > Process: 1648 ExecStart=/etc/init.d/nmb start (code=exited,

    status=0/SUCCESS)
    > CGroup: name=systemd:/system/nmb.service
    > └ 1657 /usr/sbin/nmbd -D -s /etc/samba/smb.conf
    >
    > --------------------
    >
    >
    > Code:
    > --------------------
    > smb.service - LSB: Samba SMB/CIFS file and print server
    > Loaded: loaded (/etc/init.d/smb)
    > Active: active (running) since Tue, 21 Feb 2012 08:01:14 -0700; 1h 20min

    ago
    > Process: 1676 ExecReload=/etc/init.d/smb reload (code=exited,

    status=0/SUCCESS)
    > Process: 1481 ExecStart=/etc/init.d/smb start (code=exited,

    status=0/SUCCESS)
    > CGroup: name=systemd:/system/smb.service
    > ├ 1507 /usr/sbin/smbd -D -s /etc/samba/smb.conf
    > └ 1514 /usr/sbin/smbd -D -s /etc/samba/smb.conf
    >
    > --------------------
    >
    >
    > If I navigate to smb://192.168.0.1 it says "Timeout on server
    > 192.168.0.1" and doesn't load anything.
    >
    > Here is my smb.conf file contents:

    <snip>
    >
    >
    > It's not until I run
    > Code:
    > --------------------
    > rcnmb restart && rcsmb restart
    > --------------------
    > that I can navigate the shares and they show up.
    >
    > System info:
    > openSUSE 12.1 x64, KDE 4.8.00, Linux 3.1.9-1.4
    > Samba 3.6.3-89.1-2761
    >

    saultdon;

    Do you get the same results booting with systemV? (F5 at boot).

    --
    P. V.
    "We're all in this together, I'm pulling for you." Red Green

  3. #3
    Join Date
    Mar 2008
    Location
    Oz
    Posts
    10,960
    Blog Entries
    2

    Default Re: Samba running but workgroup not visible on LAN (timeout on ...)

    Venzkep is probably on the right track. For more on that see the sticky at the top of the networking forum:
    Problem with Samba in openSUSE 12.1 re systemd

  4. #4

    Default Re: Samba running but workgroup not visible on LAN (timeout on ...)

    I installed
    sysvinit-init but still can't see my samba shares. Get the timeout error until I restart the nmb/smb daemons.

    Thanks for the sticky.

  5. #5
    Join Date
    Jun 2008
    Location
    Charmoille, Switzerland
    Posts
    26

    Default Re: Samba running but workgroup not visible on LAN (timeout on ...)

    If apparmor is installed and started, perhaps this module block access to some folders & files

    To check systemctl status apparmor.service
    and have a look at /var/log/audit/audit.log

    You can adjust the configuration of it in Yast security apparmor

  6. #6

    Default Re: Samba running but workgroup not visible on LAN (timeout on ...)

    Is apparmor installed and running by default? I will check this evening when I get to my home PC.

    I will check those logs as suggested and report outcome here.

    Akonadi and Nepomuk were disabled when I first installed opensuse so those aren't running either.

  7. #7
    Join Date
    Nov 2009
    Location
    ND, USA
    Posts
    1,069

    Default Re: Samba running but workgroup not visible on LAN (timeout on ...)

    On Wed February 22 2012 11:06 am, saultdon wrote:

    >
    > Is apparmor installed and running by default? I will check this evening
    > when I get to my home PC.
    >
    > I will check those logs as suggested and report outcome here.
    >
    > Akonadi and Nepomuk were disabled when I first installed opensuse so
    > those aren't running either.
    >

    saultdon;

    When you check the logs also look at
    /var/log/samba/log.nmbd, /var/log/samba/log.smbd and /var/log/messages. You
    can increase the details in the samba logs by adding the parameter "log level
    = 3" to the global section of /etc/samba/smb.conf. (The level can be raised
    as high as 10 but that is likely way more detail than you want without the
    Samba code at hand.)

    Upon occasion a Windows machine will grab the role of master browser away from
    the Samba machine and destroy network browsing. This happens in spite of
    settings in your smb.conf. When you can not browse the network, look
    at /var/lib/samba/browse.dat. This is a text file and should contain a list
    of all the machines in your workgroup. Should this file only contain the name
    of your OpenSuse machine, browsing has been hijacked. If you do have a rogue
    Windows machine in your workgroup, there is a reg edit that can be done to the
    offending machine to prevent this behavior. (or drop it off the roof) I might
    also note that restarting nmbd almost always solves the problem until the
    rogue machine is removed and then reconnected to your network.

    The above does not explain the failure of Samba client to see shares via IP.
    Are you certain that 192.168.0.1 is the actual address of a workgroup machine
    and not just your router?

    --
    P. V.
    "We're all in this together, I'm pulling for you." Red Green

  8. #8

    Default Re: Samba running but workgroup not visible on LAN (timeout on ...)

    Quote Originally Posted by venzkep View Post
    When you check the logs also look at [both] /var/log/samba/log.{nmbd,smbd} and /var/log/messages. Youcan increase the details in the samba logs by adding the parameter "log level= 3" to the global section of /etc/samba/smb.conf
    I will check these out, looks like they will definitely have some useful information. Thanks!


    Quote Originally Posted by venzkep View Post
    Upon occasion a Windows machine will grab the role of master browser away fromthe Samba machine and destroy network browsing.
    I should of mentioned - there are only openSUSE PCs accessing the samba share [smb].I have a similar setup on a laptop and it displays the same behaviour.
    It was working before, everything loaded fine on boot.
    There may of been a specific update that caused this?
    The primary purpose of samba for me is to share zyppers cached packages to multiple PCs on the LAN to reduce bandwidth and dload/install times.
    My windows discs have been collecting dust.


    Quote Originally Posted by venzkep View Post
    Are you certain that 192.168.0.1 is the actual address of a workgroup machineand not just your router?
    You're right, it is the router, but I just provided as an example ip

  9. #9

    Default Re: Samba running but workgroup not visible on LAN (timeout on ...)

    less /var/log/messages | grep samba

    cat /var/log/samba/log.nmbd

    cat /var/log/samba/log.smbd

    There are a few warnings and errors. Not sure what to do from here, but thanks for all the help so far everyone.

  10. #10

    Default Re: Samba running but workgroup not visible on LAN (timeout on ...)

    I tried @venzkep's original suggestion after having installed sysinit-init and restarted the rcnmb and rcsmb services while booting into console mode (recovery with networking) and now everything seems to be working fine.

Page 1 of 2 12 LastLast

Tags for this Thread

Posting Permissions

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