Problem seeing Samba shares from Windows client

English Network/Internet
1

My home network has several windows machines and an openSUSE 12.2 machine connected together. I have Samba installed and working (sort of) on the Linux box. Here is the smb.conf file:

# 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-08-08
[global]
      workgroup = HOME
      passdb backend = tdbsam
      printing = cups
      printcap name = cups
      printcap cache time = 750
      cups options = raw
      map to guest = Bad User
      include = /etc/samba/dhcp.conf
      logon path = \\%L\profiles\.msprofile
      logon home = \\%L\%U\.9xprofile
      logon drive = P:
      usershare allow guests = No
      add machine script = /usr/sbin/useradd  -c Machine -d /var/lib/nobody -s /bin/false %m$
      domain logons = No
      domain master = No
      security = user
      wins support = No
[homes]
      comment = Home Directories
      valid users = %S, %D%w%S
      browseable = No
      read only = No
      inherit acls = Yes
[profiles]
      comment = Network Profiles Service
      path = %H
      read only = No
      store dos attributes = Yes
      create mask = 0600
      directory mask = 0700
[users]
      comment = All users
      path = /home
      read only = No
      inherit acls = Yes
      veto files = /aquota.user/groups/shares/
[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

## Share disabled by YaST
# [netlogon]

My problem is that shares from the Linux machine appear in Windows Network for about 5-15 minutes, but then, curiously, a Windows dialog box appears, asking for a username and password. From that point I cannot access any shares on the Linux box.

I have users added via smbpasswd -a …, and username/passwords are identical across all machines. Windows machines can see and access each other just fine.

Can anyone help me with this?

Thank you,

Steve

2

Always place data such as the smb.conf file into a code # block as I did with your post. May I suggest you have a look at my blogs on the subject:

Samba S.W.A.T. - Samba Web Administration Tool Setup for openSUSE: https://forums.opensuse.org/blogs/jdmcdaniel3/samba-swat-samba-web-administration-tool-setup-opensuse-76/

AND

SWAT - Samba Web Administration Tool - Setup & Creation Script - 1.04: https://forums.opensuse.org/blogs/jdmcdaniel3/swat-samba-web-administration-tool-setup-creation-script-1-03-105/

AND to edit any system file including smb.conf manually:

SYSEdit - System File Editor - Version 1.50: https://forums.opensuse.org/blogs/jdmcdaniel3/sysedit-system-file-editor-version-1-00-60/

And for all things Samba, have a look here: openSUSE SuSE Linux HOWTOs and Tutorials by Swerdna

Thank You,

3

The default sages you get are just examples, they’re not supposed to be “the solution”, just “food for thought”.
You’ve got a bunch of shares there that require a username/password to enter. And you’ve got a share there that’s simply invalid, doesn’t really exist. So those things probably throwing the spanner at you. Tell me what it is that you really want to share and I’ll (try to) explain what you need to do.

4

Thank you both for your help. I went to Samba and Suse: HowTo Set up an openSUSE-Windows Home Office LAN/Network. Versions 11.x as well as the other links and updated smb.conf:

# 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-08-08
[global]
       workgroup = HOME
      passdb backend = tdbsam
      printing = cups
      printcap name = cups
      printcap cache time = 750
      cups options = raw
      map to guest = Bad User
      include = /etc/samba/dhcp.conf
      usershare allow guests = No
      add machine script = /usr/sbin/useradd  -c Machine -d /var/lib/nobody -s /bin/false %m$
      domain logons = No
      domain master = No
      security = user
      wins support = No
      netbios name = Linuxgateway
      wins server =
      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
[users]
      comment = All users
      path = /home
      read only = No
      inherit acls = Yes
      veto files = /aquota.user/groups/shares/
[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

## Share disabled by YaST
# [netlogon]

I would like to have shares available for the users on the Linux machine, as well as the HP printer connected to it, across my home network.

On smb.conf, I disabled [profiles] and deleted the “logon” lines. I also added the “netbios name = Linuxgateway” and re-entered usernames/passwords using smbpasswd -a … Also, I added local master and os level lines.

After waiting for a while and restarting nmb and smb, my problem continues.

Thank you again for any help,

Steve

5

Let me say that user rights and file permissions must be satisfied in order to share a folder that belongs to one user on PC1 to another but different user on PC2. In my examples using SWAT, I decided to setup shares for folders outside the user area. The main folder has permissions set to 777, since the shares are with Windows PC’s, I prefer to share NTFS partitions and on the Linux machine that shares the NTFS partition, I setup the partition in the fstab file using “defaults” mount option. So, if ANY user on PC1 can use the shared folder, then any user on PC2 could also look at and use the share. For local permissions on files and folders, have a look at this blog:

S.A.F.P. - SUSE Automated File Permissions - Version 1.0.4: https://forums.opensuse.org/blogs/jdmcdaniel3/s-f-p-suse-automated-file-permissions-version-1-0-4-113/

So to recap you must consider:

  1. Who owns the folder you are sharing?
  2. Can everyone locally get to the files and folder?
  3. What is the file and folder permissions set to?
  4. What is the fstab setting for the partition that contains your folder you are sharing?
  5. Who is the user and do they exist on both PC if you are trying to share a user owned area?
  6. To share user owned areas, the same user should exist on both PC’s and have a password for the share.
  7. To share with any user and no passwords, you got to look back at my original suggestions on what to share.

Thank You,

6

jdmcdaniel3: Yes, users and passwords are identical on all machines. While the shares are visible, I can read and write from any windows machine to the linux machine shares. But as I said, these shares appear for a while, then windows prompts for a username/password, and never accepts valid user names. The error returned is “bad user or password”.

Thanks,

Steve

7

I would request you have a look at this default smb.conf file suggested to me by swerdna. What it does is allow you to look at any share on another PC, such as a Windows machine, but nothing is setup per user on the computer with the default smb.conf file unless you do more. In my examples I talk about setting up SWAT, which among other things, provides very good info on each Samba config command when used. In fact, you can save your smb.conf file and run my setup bash script to see what you get and you can restore your config file at any time. Using SWAT does help or hurt your sharing issue, just provides another way to administer the local PC, but the script does make sure that the Firewall settings are right and lets you see that smbd and nmbd are running from a web page. Here is the smb.conf file created by my bash script:


# 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.
# Samba config file created using SWAT 
# from $netbios_name (127.0.0.1)
# Date: $(date)

[global]
  workgroup = $Workgroup
#  netbios name = $netbios_name
  passdb backend = tdbsam
  name resolve order = bcast host lmhosts wins
  server string = ""
  printing = cups
  printcap name = cups
  printcap cache time = 750
  cups options = raw
  use client driver = yes
  map to guest = Bad User
  local master = yes
  os level = 33
  usershare allow guests = Yes
  usershare max shares = 100
  usershare owner only = False

[homes]
  comment = Home Directories
  valid users = %S, %D%w%S
  browseable = No
  read only = No
  inherit acls = Yes

[printers]
  comment = All Printers
  path = /var/tmp
  printable = Yes
  create mask = 0700
  browseable = No
  guest OK = Yes

[print$]
  comment = Printer Drivers
  path = /var/lib/samba/drivers
  write list = @ntadmin root
  force group = ntadmin
  create mask = 0664
  directory mask = 0775

When the setting** netbios name, **is remarked out in the smb config file, you will use the PC Host name assigned it during the installation of openSUSE.

Thank You,

8

IMO it might be helpful to describe and understand some basics…

If you have more than three machines in your network, it becomes advisable to implement network security instead of local security only so that some User Accounts are valid on any and all machines… why?

Although you may set up accounts with the same username and password on different machines, each account will work only on that one machine because machines don’t actually use the human legible letters and numbers you see, the machine uses the corresponding crypt keys associated with those names and words which are randomly generated each and every time they’re created(so would be different on different machines).

The only exception is the Guest or Anonymous account which is defined as the absence of security restrictions so can be common to all machines running that OS.

So,
Aside from the opening recommendation to implement Network Security, it should become obvious that logging into shares on different machines should not be possible using the same username/password unless the both your local and the remote machines truly understand which account is being used(recommend clearly state machine). The alternative is to do something like script mounting each share individually.

HTH,
TSU

9

On 1/20/2013 1:56 PM, tsu2 wrote:
<snip>
>
> So,
> Aside from the opening recommendation to implement Network Security, it
> should become obvious that logging into shares on different machines
> should not be possible using the same username/password unless the both
> your local and the remote machines truly understand which account is
> being used(recommend clearly state machine). The alternative is to do
> something like script mounting each share individually.
>
> HTH,
> TSU
>
>
This is Samba/Windows networking the name and password are sent to the server.
Samba maps the username it receives to the appropriate UID in /etc/passwd.
Likewise, between Windows Machines the name is mapped to the appropriate SID on
the server.

owkmann;

As your Windows networking for 5-15 minutes, I think that very likely the Master
Browser role is being hijacked by another machine that enters the network and
Samba assumes it is the Master Browser as does the Windows(?) machine. To test
this check, while the shares are visible, the contents of:
/var/lib/samba/browse.dat.
When your network sharing fails check the contents again. Are the same machines
listed?

P.V.
“We’re all in this together, I’m pulling for you” Red Green

10

owkmann;

I should have commented on the contents of your /etc/samba/smb.conf in my
previous post. Consider adding the following parameters to your smb.conf.


name resolve order = bcast host lmhosts
os level = 35

Then make sure nmb(d) is started as well as smbd. This allows you to resolve
netbios names by broadcasts (the method used by windows). And should improve
the chances of becoming the local master browser. Also make sure that the Samba
Server, Netbios Server and Samba Client are all allowed services through your
firewall.

If your windows Network still fails after a few minutes, try setting “local
master” to no. This would prevent the Samba machine from ever becoming the
local master browser and one of your windows machines or another Samba machine
will pickup the role of local master.
– n
P.V.
“We’re all in this together, I’m pulling for you” Red Green

11

I edited smb.conf as suggested. First I added

name resolve order = bcast host lmhosts
os level = 35

with the same results.

Then I set local master = no, and that did not work either. After each change I restarted samba. I did check, and confirmed, that the firewall is set to allow samba server, netbios, and samba client.

So my problem continues.

Thanks for your help,

Steve

12

On 1/25/2013 4:36 PM, owkmann wrote:
>
> I edited smb.conf as suggested. First I added
>
>
> Code:
> --------------------
> name resolve order = bcast host lmhosts
> os level = 35
> --------------------
>
>
> with the same results.
>
> Then I set local master = no, and that did not work either. After each
> change I restarted samba. I did check, and confirmed, that the firewall
> is set to allow samba server, netbios, and samba client.
>
> So my problem continues.
>
> Thanks for your help,
>
> Steve
>
>
Steve;

Did you check the contents of /var/lib/samba/browse.dat as I suggested earlier.
Is their any difference in the contents?

Try these before the shares vanish and again afterward:


nmblookup -B <yourSmbMachineName> <yourWorkgroup>
nmblookup -B <yourWindowsMachineName> '*'
smbtree

smbtree will prompt for a password, use the Samba password for your user (i.e.
the password set by smbpasswd -a <name>)

Post the results. The first two commands should return just an IP the third a
list of all machines and their shares.

–
P.V.
“We’re all in this together, I’m pulling for you” Red Green

13

venzkep,

Yes, I checked browse.dat before and after the shares-connection failed. There was no difference in the file contents.

nmblookup -B Linuxgateway HOME

gives me (after the shares vanish):

querying HOME on 127.0.0.1

192.168.1.76 HOME<00>

nmblookup -B Hank HOME

gives me

querying HOME on 192.168.1.67

192.168.1.67 HOME<00>

nmblookup -B Pearl HOME

gives me

querying HOME on 192.168.1.70

name_query failed to find name HOME

smbtree

gives me

smbtree
Enter steve's password: 
HOME\\PEARL                
        \\PEARL\Users              
        \\PEARL\Public             
        \\PEARL\IPC$               Remote IPC
        \\PEARL\E$                 Default share
        \\PEARL\D$                 Default share
        \\PEARL\C$                 Default share
        \\PEARL\ADMIN$             Remote Admin
\\LINUXGATEWAY           Samba 3.6.7-48.12.1-2831-SUSE-SL12.2-i386
[INDENT=2]\\LINUXGATEWAY\steve              Home Directories[/INDENT]
[INDENT=2]\\LINUXGATEWAY\HPLaserJet5P       HP LaserJet 5P Foomatic/ljet4 (recommended)[/INDENT]
        \\LINUXGATEWAY\IPC$               IPC Service (Samba 3.6.7-48.12.1-2831-SUSE-SL12.2-i386)
        \\LINUXGATEWAY\print$             Printer Drivers
        \\LINUXGATEWAY\groups             All groups
[INDENT=2] \\LINUXGATEWAY\users              All users[/INDENT]
\\HANK
[INDENT=2]\\HANK\Users    [/INDENT]
[INDENT=2]\\HANK\print$             Printer Drivers
[/INDENT]
        \\HANK\IPC$               Remote IPC
        \\HANK\C$                 Default share
        \\HANK\ADMIN$             Remote Admin

Currently no shares are available on any Windows machines connected to my HOME network.

Thanks,

Steve

14

On 1/26/2013 11:46 AM, owkmann wrote:
>
> venzkep,
>
> Yes, I checked browse.dat before and after the shares-connection
> failed. There was no difference in the file contents.
<snip>
>
>
> Code:
> --------------------
> smbtree
> Enter steve’s password:
> HOME
<snip>
> Currently no shares are available on any Windows machines connected to
> my HOME network.
>
> Thanks,
>
> Steve
>
>
Steve;

Was smbtree run before or after the shares vanish?

Both before and after the shares vanish run:


ps -A | grep [n,s]mbd

This should give the process numbers for one (or more) copies of nmbd and smbd.
Any change before and after?

Again do this before and after the shares vanish. Run from a Windows machine
command line:


nbtstat -a <machinename>

Use the machinename for each of your machines, one of the machines should list
“…MSBROWSE.” Does this change?

To get to the Windows Command Line, <start> > (All)Programs > Accessories >
Command Prompt.

Note: in nbtstat the “a” is case sensitive.

When the Linux shares vanish, does anything occur on the network, say a machine
is turned on or maybe off?

P.V.
“We’re all in this together, I’m pulling for you” Red Green

15

Thank you for your help. Here are the answers to your code queries:

Before I lose my Samba shares:


Linuxgateway:/home/steve # ps -A | grep nmbd
 8868 ?        00:00:00 nmbd
Linuxgateway:/home/steve # ps -A | grep smbd
 8893 ?        00:00:00 smbd
 8895 ?        00:00:00 smbd
10506 ?        00:00:00 smbd
Linuxgateway:/home/steve # smbtree
Enter steve's password: 
MAGOON
    \\MASIWEI                
    \\LINUXGATEWAY           Samba 3.6.7-48.12.1-2831-SUSE-SL12.2-i386
        \\LINUXGATEWAY\steve              Home Directories
        \\LINUXGATEWAY\HPLaserJet5P       HP LaserJet 5P Foomatic/ljet4 (recommended)
        \\LINUXGATEWAY\IPC$               IPC Service (Samba 3.6.7-48.12.1-2831-SUSE-SL12.2-i386)
        \\LINUXGATEWAY\print$             Printer Drivers
        \\LINUXGATEWAY\groups             All groups
        \\LINUXGATEWAY\users              All users
    \\HANK                   
        \\HANK\Users              
        \\HANK\print$             Printer Drivers
        \\HANK\IPC$               Remote IPC
        \\HANK\C$                 Default share
        \\HANK\ADMIN$             Remote Admin

And after I lose Samba shares:


Linuxgateway:/home/steve # ps -A | grep nmbd
 8868 ?        00:00:01 nmbd
Linuxgateway:/home/steve # ps -A | grep smbd
 8893 ?        00:00:00 smbd
 8895 ?        00:00:00 smbd
Linuxgateway:/home/steve # smbtree
Enter steve's password: 
MAGOON
    \\MASIWEI                
    \\LINUXGATEWAY           Samba 3.6.7-48.12.1-2831-SUSE-SL12.2-i386
        \\LINUXGATEWAY\steve              Home Directories
        \\LINUXGATEWAY\HPLaserJet5P       HP LaserJet 5P Foomatic/ljet4 (recommended)
        \\LINUXGATEWAY\IPC$               IPC Service (Samba 3.6.7-48.12.1-2831-SUSE-SL12.2-i386)
        \\LINUXGATEWAY\print$             Printer Drivers
        \\LINUXGATEWAY\groups             All groups
        \\LINUXGATEWAY\users              All users
    \\HANK                   
        \\HANK\Users              
        \\HANK\print$             Printer Drivers
        \\HANK\IPC$               Remote IPC
        \\HANK\C$                 Default share
        \\HANK\ADMIN$             Remote Admin
Linuxgateway:/home/steve #

“MAGOON” is the name of my Windows Workgroup.

Also, you asked if share visibility changes with machines logging on or being turned off. The answer is a definite “Yes”. This morning I booted my Windows Vista laptop first. Samba shares on the Linux machine were available to the Laptop. But as soon as I turned on my Windows 7 desktop, the shares on the laptop disappeared, and became visible on the desktop - for a while. Then even those shares became unavailable. But then they reappeared!

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Steve>nbtstat -a Linuxgateway

Local Area Connection:
Node IpAddress: [192.168.1.67] Scope Id: ]

           NetBIOS Remote Machine Name Table

       Name               Type         Status
    ---------------------------------------------
    LINUXGATEWAY   <00>  UNIQUE      Registered
    LINUXGATEWAY   <03>  UNIQUE      Registered
    LINUXGATEWAY   <20>  UNIQUE      Registered
    ..__MSBROWSE__.<01>  GROUP       Registered
    MAGOON         <1D>  UNIQUE      Registered
    MAGOON         <1E>  GROUP       Registered
    MAGOON         <00>  GROUP       Registered

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


Local Area Connection* 9:
Node IpAddress: [0.0.0.0] Scope Id: ]

    Host not found.

C:\Users\Steve>

I’m sure there’s a setting somewhere I have messed up.

Steve

16

On 2/9/2013 9:36 AM, owkmann wrote:
>
> Thank you for your help. Here are the answers to your code queries:
>
<snip>
>
> Also, you asked if share visibility changes with machines logging on or
> being turned off. The answer is a definite “Yes”. This morning I booted
> my Windows Vista laptop first. Samba shares on the Linux machine were
> available to the Laptop. But as soon as I turned on my Windows 7
> desktop, the shares on the laptop disappeared, and became visible on the
> desktop - for a while. Then even those shares became unavailable. But
> then they reappeared!
>
>
>
> Code:
> --------------------
> Microsoft Windows [Version 6.1.7601]
> Copyright (c) 2009 Microsoft Corporation. All rights reserved.
>
> C:\Users\Steve>nbtstat -a Linuxgateway
>
> Local Area Connection:
> Node IpAddress: [192.168.1.67] Scope Id: ]
>
> NetBIOS Remote Machine Name Table
>
> Name Type Status
> ---------------------------------------------
> LINUXGATEWAY <00> UNIQUE Registered
> LINUXGATEWAY <03> UNIQUE Registered
> LINUXGATEWAY <20> UNIQUE Registered
> …MSBROWSE.<01> GROUP Registered
> MAGOON <1D> UNIQUE Registered
> MAGOON <1E> GROUP Registered
> MAGOON <00> GROUP Registered
>
> MAC Address = 00-00-00-00-00-00
>
>
> Local Area Connection* 9:
> Node IpAddress: [0.0.0.0] Scope Id: ]
>
> Host not found.
>
> C:\Users\Steve>
> --------------------
>
>
> I’m sure there’s a setting somewhere I have messed up.
>
> Steve
>
>
Steve;

Can you verify that turning on the Windows 7 machine corresponds to losing your
shares?

If you are manually setting IPs, make sure that Windows7 and the Linux machine
have distinct IP numbers. This should not be a problem if both machines use
dhcp. To check:
On Windows 7 command line enter


ipconfig /all

and on Linux,


/sbin/ifconfig -a

Assuming you have different IPs try restarting just nmbd.


su -
systemctl restart nmb.service

After restarting nmb do the shares become accessible?

P.V.
“We’re all in this together, I’m pulling for you” Red Green

17

“Can you verify that turning on the Windows 7 machine corresponds to losing your
shares?”

It does not appear to be Windows OS specific, but whoever logs into their Windows machine last gets the shares.

I am not manually setting IP addresses for these machines. I have an AT&T modem/router that has DHCP running on it, and have confirmed that all machines have assigned IP addresses within the 192.168… space.

I have tried restarting nmbd and smbd numerous times, without success.

Appreciate your help,

Steve

18

On 2/9/2013 4:46 PM, owkmann wrote:
>
> “Can you verify that turning on the Windows 7 machine corresponds to
> losing your
> shares?”
>
> It does not appear to be Windows OS specific, but whoever logs into
> their Windows machine last gets the shares.
>
> I am not manually setting IP addresses for these machines. I have an
> AT&T modem/router that has DHCP running on it, and have confirmed that
> all machines have assigned IP addresses within the 192.168… space.

Have you confirmed the IPs are all different?
>
> I have tried restarting nmbd and smbd numerous times, without success.
>
> Appreciate your help,
>
> Steve
>
owkmann;

I’m quite sure your problem is just with nmbd, but I’m running out of ideas.

In your first post you indicated that your workgroup was “HOME” and later you
said it was “MAGOON”. Both can not be right. What type of machines are
MASIWEI, PEARL and HANK?

When your shares vanish, use just one Windows machine but get the results of
nbtstat for all three of your machines, including the machine which you use to
run the command.

–
P.V.
“We’re all in this together, I’m pulling for you” Red Green

19

Yes, all machines are getting separate IPs.

The correct Workgroup name is MAGOON. HOME was just a name I used in the early posts of this thread.

Hank is a Windows 7 desktop; Pearl is a Windows 7 64-bit laptop; Masiwei is a Windows Vista laptop.

Here are the results from nbtstat -a … for all machines, with the commands issued from Hank:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Steve>nbtstat -a Hank

Local Area Connection:
Node IpAddress: [192.168.1.67] Scope Id: ]

           NetBIOS Remote Machine Name Table

       Name               Type         Status
    ---------------------------------------------
    HANK           <00>  UNIQUE      Registered
    MAGOON         <00>  GROUP       Registered
    HANK           <20>  UNIQUE      Registered
    MAGOON         <1E>  GROUP       Registered

    MAC Address = 00-19-DB-F4-F6-04


Local Area Connection* 9:
Node IpAddress: [10.65.4.20] Scope Id: ]

           NetBIOS Remote Machine Name Table

       Name               Type         Status
    ---------------------------------------------
    HANK           <00>  UNIQUE      Registered
    MAGOON         <00>  GROUP       Registered
    HANK           <20>  UNIQUE      Registered
    MAGOON         <1E>  GROUP       Registered
    MAGOON         <1D>  UNIQUE      Registered
    ..__MSBROWSE__.<01>  GROUP       Registered

    MAC Address = 00-FF-08-D0-60-86


C:\Users\Steve>nbtstat -a Linuxgateway

Local Area Connection:
Node IpAddress: [192.168.1.67] Scope Id: ]

           NetBIOS Remote Machine Name Table

       Name               Type         Status
    ---------------------------------------------
    LINUXGATEWAY   <00>  UNIQUE      Registered
    LINUXGATEWAY   <03>  UNIQUE      Registered
    LINUXGATEWAY   <20>  UNIQUE      Registered
    ..__MSBROWSE__.<01>  GROUP       Registered
    MAGOON         <1D>  UNIQUE      Registered
    MAGOON         <1E>  GROUP       Registered
    MAGOON         <00>  GROUP       Registered

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


Local Area Connection* 9:
Node IpAddress: [10.65.4.20] Scope Id: ]

    Host not found.

C:\Users\Steve>nbtstat -a Pearl

Local Area Connection:
Node IpAddress: [192.168.1.67] Scope Id: ]

           NetBIOS Remote Machine Name Table

       Name               Type         Status
    ---------------------------------------------
    PEARL          <00>  UNIQUE      Registered
    MAGOON         <00>  GROUP       Registered
    PEARL          <20>  UNIQUE      Registered
    MAGOON         <1E>  GROUP       Registered

    MAC Address = 78-E4-00-22-F1-C1


Local Area Connection* 9:
Node IpAddress: [10.65.4.20] Scope Id: ]

    Host not found.

C:\Users\Steve>nbtstat -a Masiwei

Local Area Connection:
Node IpAddress: [192.168.1.67] Scope Id: ]

           NetBIOS Remote Machine Name Table

       Name               Type         Status
    ---------------------------------------------
    MASIWEI        <00>  UNIQUE      Registered
    MAGOON         <00>  GROUP       Registered
    MASIWEI        <20>  UNIQUE      Registered
    MAGOON         <1E>  GROUP       Registered

    MAC Address = 00-1E-4C-4B-85-6C


Local Area Connection* 9:
Node IpAddress: [10.65.4.20] Scope Id: ]

    Host not found.

C:\Users\Steve>

Would a hardware failure on the linux machine cause this problem?

What about a conflict with the AT&T modem/router? Is it possible it and Samba are colliding somehow?

Thanks,

Steve

20

Let me say that mainly the smb.conf file is to blame for the issues you can have. Second, is a potential problem a side effect that systemd can have and finally, your firewall operation is also important to its operation. I would like to add a sidenote to this about smbtree. For what ever reason, unless I am missing something here as I don’t normally use this application, running smbtree with no options produces a blank output on my properly working machine. But, I get the same output I see here with the -N option:

james@LinuxMaster:~> smbtree -N
WINDOWSNT
        \\OLDMASTER      
                \\OLDMASTER\Software       
                \\OLDMASTER\VirtualBox     
                \\OLDMASTER\Windows        
                \\OLDMASTER\IPC$                IPC Service ()
        \\MULTIMEDIA                    The Master of the Universe
                \\MULTIMEDIA\Software       
                \\MULTIMEDIA\Windows        
                \\MULTIMEDIA\IPC$               IPC Service (The Master of the Universe)
        \\MCTRONICS      
        \\LINUXUSER      
                \\LINUXUSER\IPC$                IPC Service ()
                \\LINUXUSER\Windows        
                \\LINUXUSER\DataSafe       
                \\LINUXUSER\Software       
        \\LINUXMASTER                   Samba 3.6.7-48.12.1-2831-SUSE-SL12.2-x86_64
                \\LINUXMASTER\Software       
                \\LINUXMASTER\Windows        
                \\LINUXMASTER\DataSafe       
                \\LINUXMASTER\Multimedia     
                \\LINUXMASTER\IPC$              IPC Service (Samba 3.6.7-48.12.1-2831-SUSE-SL12.2-x86_64)
        \\JAMIE-PC       


    \\MCTRONICS    is Windows 8 &        \\JAMIE-PC    is Windows 7.  Just in case anyone else following us also sees no output, add the -N option.  Next I would like to direct your attention to the firewall and make sure all is right there:

http://paste.opensuse.org/view/download/33134439

I have added the top 3 for Samba usage. If you can turn off your Firewall and everything works OK then you know it is a Firewall setting. Next, a problem can arise due to the way systemd works and may fail the nmb.service. Have a look at my suggested sysconfig editor setting:

http://paste.opensuse.org/view/download/73021754

Changing the default from 30 to 60 seconds can help prevent the nmb service from failing or at least appearing to fail to systemd. Another thing you want to look is your Host name and how are you setting it? In your /etc/samba/smb.conf file, you can set your hostname (mine are remarked out there):

[global]
    workgroup = WINDOWSNT
#    netbios name = LINUXMASTER
#    server string = The Master of the Universe

But, you can also set your hostname here:

http://paste.opensuse.org/view/download/66959882

There are three possibilities with the Host Name setup when you are using Samba. but only # one or # two should be used.

  1. Set your Hostname in YaST / Network Devices / Netwrk Settings and remark out the name in your /etc/samba/smb.conf file
  2. You can Set YaST Hostmname to one thing and set your Samba Hostname to a different Name. This works OK, but it does not make sense perhaps to have two different names for the same PC.
  3. Set Both Names to the Same Hostname in YaST and In your Samba /etc/samba/smb.conf file ← DO NOT DO THIS as it can create some very strange Samba Browsing problems and there is no need to do this. See step 1!

So, these are my suggestions you want to look in to.

Thank You,