Samba problem after ugrade to 12.3

Got a problem with Samba after upgrading to Open SuSE 12.3. The network was working prior to the upgrade. I can get out to the Internet with linux, so it is not a network problem. I looked at swerdna’s instructions for clues as to what may be the problem. Even tried turning off the firewall no no avail. Konquerer on the same machine does not even show any shares. When I restart nmb and smb no errors are given.

The following is the smb.conf file:

Samba config file created using SWAT # from UNKNOWN (127.0.0.1) # Date: 2012/11/01 21:05:46 [global] map to guest = Bad User name resolve order = bcast host lmhosts wins printcap name = cups add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$ #logon path = \%L\profiles.msprofile #logon drive = P: #logon home = \%L%U.9xprofile preferred master = Auto domain master = No cups options = raw usershare allow guests = Yes wins support = No workgroup = WORKGROUP netbios name = scott1 wins server = passdb backend = tdbsam printing = cups printcap cache time = 750 include = /etc/samba/dhcp.conf usershare allow guests = Yes [homes] comment = Home Directories valid users = %S, %D%w%S browseable = No read only = No inherit acls = Yes [profiles] comment = Network Profile 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 create mask = 0600 printable = Yes browseable = No [print$] comment = Printer Drivers path = /var/lib/samba/drivers write list = @ntadmin root force group = ntadmin create mask = 0664 directory mask = 0775

Any ideas on why the Samba connections are not showing?

Sorry for having line wraps…

Did you also check https://forums.opensuse.org/blogs/jdmcdaniel3/s-c-t-samba-automated-configuration-tool-version-1-07-124/

I have seen that script but didn’t try it till now. I did run the option to create/replace the smb configuration file and it now says the services are now running (nmb and smb). When I open Konqurer and select Network folders and then samba shares I get a blank window where the shares. And just for jollies, I tried to see what Windows XP would say is out there. That gives me “Workgroup is not accessible”.

Also ran the option to create a desktop icon which didn’t work. While the Icon is on the desktop when I try to run it I get a terminal window and the message in it states: Warning: Could not find ‘/home/scott/bin/sact’, starting ‘/bin/bash’ instead. Please check your profile settings.

So, still problems…

On 4/23/2013 1:36 PM, svetter88 wrote:
>
> I have seen that script but didn’t try it till now. I did run the
> option to create/replace the smb configuration file and it now says the
> services are now running (nmb and smb). When I open Konqurer and select
> Network folders and then samba shares I get a blank window where the
> shares. And just for jollies, I tried to see what Windows XP would say
> is out there. That gives me “Workgroup is not accessible”.
>
> Also ran the option to create a desktop icon which didn’t work. While
> the Icon is on the desktop when I try to run it I get a terminal window
> and the message in it states: Warning: Could not find
> ‘/home/scott/bin/sact’, starting ‘/bin/bash’ instead. Please check your
> profile settings.
>
> So, still problems…
>
svetter88;

Please repost the contents of /etc/samba/smb.conf but this time use code tags so it dosn’t wrap. Have you checked the following?

  1. All machines are in the same workgroup.
  2. Samba Server, Netbios Server, and Samba Client are all allowed services through the firewall.
  3. Users have been created with:

smbpasswd -a <username>


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

You can use code tags to make it more readable next time. I think it should help :slight_smile: Thank you in advance.

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 scott1 (127.0.0.1)

Date: Tue Apr 23 14:20:03 EDT 2013

[global]
workgroup = WORKGROUP
netbios name = scott1
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

For the purposes of this test I have the firewall disabled.

And just added a user.

From a Windows 7 computer the Linux/Samba machine is not even shown. This is using Windows Explorer and choosing to display the network.

In your smb.conf post, I see no basic operational problem. The following code in your Global section is redundant, the default and can be removed.

usershare allow guests = Yes
usershare max shares = 100
usershare owner only = False

I would wonder if the nmb and smb services are even activated and running? I suggest you open up a terminal session and run these two command and post the result in a code # tagged post:

/bin/systemctl status nmb.service
/bin/systemctl status smb.service

Here is an example of what to see from a working system:

Terminal Command:** /bin/systemctl status nmb.service**

nmb.service - LSB: Samba NetBIOS naming service over IP
          Loaded: loaded (/etc/init.d/nmb)
          Active:** active (running) **since Sun, 2013-04-21 21:00:22 CDT; 2 days ago
         Process: 1212 ExecStart=/etc/init.d/nmb start (code=exited, status=0/SUCCESS)
          CGroup: name=systemd:/system/nmb.service
                  └ 1361 /usr/sbin/nmbd -D -s /etc/samba/smb.conf


Terminal Command: **/bin/systemctl status smb.service**

smb.service - LSB: Samba SMB/CIFS file and print server
          Loaded: loaded (/etc/init.d/smb)
          Active: **active (running)** since Sun, 2013-04-21 21:00:22 CDT; 2 days ago
         Process: 1370 ExecStart=/etc/init.d/smb start (code=exited, status=0/SUCCESS)
          CGroup: name=systemd:/system/smb.service
                  ├ 1464 /usr/sbin/smbd -D -s /etc/samba/smb.conf
                  └ 1499 /usr/sbin/smbd -D -s /etc/samba/smb.conf

I have a bash script called sact that can even setup your Firewall properly and start and see the service status. Open up a terminal session, copy the text below, paste it into terminal and execute this command by pressing enter:

rm ~/bin/sact ; wget -nc http://paste.opensuse.org/view/download/32414090 -O ~/bin/sact ; chmod +x ~/bin/sact

To run, just type in:

sact

You can read about the bash script here: S.A.C.T. - Samba Automated Configuration Tool - Version 1.06 - Blogs - openSUSE Forums

Thank You,

I commented out the three defaulted options as you mentioned.

And ran the teo commands to see if the nmb and smb services are running which from looking at it, they are. The results of the output from each are as follows:
nmb:
nmb.service - LSB: Samba NetBIOS naming service over IP
Loaded: loaded (/etc/init.d/nmb)
Active: active (running) since Tue, 2013-04-23 14:10:38 EDT; 1 day and 4h ago
CGroup: name=systemd:/system/nmb.service
└ 32710 /usr/sbin/nmbd -D -s /etc/samba/smb.conf

Apr 23 14:10:38 scott1.site systemd[1]: Starting LSB: Samba NetBIOS naming service over IP…
Apr 23 14:10:38 scott1.site nmb[32700]: Starting Samba NMB daemon …done
Apr 23 14:10:38 scott1.site systemd[1]: Started LSB: Samba NetBIOS naming service over IP.
Apr 23 14:20:14 scott1.site systemd[1]: Started LSB: Samba NetBIOS naming service over IP.

smb:
smb.service - LSB: Samba SMB/CIFS file and print server
Loaded: loaded (/etc/init.d/smb)
Active: active (running) since Tue, 2013-04-23 12:00:08 EDT; 1 day and 6h ago
CGroup: name=systemd:/system/smb.service
├ 18772 /usr/sbin/smbd -D -s /etc/samba/smb.conf
└ 18776 /usr/sbin/smbd -D -s /etc/samba/smb.conf

Apr 23 12:00:07 scott1.site systemd[1]: Starting LSB: Samba SMB/CIFS file and print server…
Apr 23 12:00:08 scott1.site smbd[18770]: [2013/04/23 12:00:08.093272, 0] param/loadparm.c:7209(se…_ok)
Apr 23 12:00:08 scott1.site smb[18761]: Starting Samba SMB daemon …done
Apr 23 12:00:08 scott1.site systemd[1]: Started LSB: Samba SMB/CIFS file and print server.
Apr 23 14:10:38 scott1.site systemd[1]: Started LSB: Samba SMB/CIFS file and print server.
Apr 23 14:20:14 scott1.site systemd[1]: Started LSB: Samba SMB/CIFS file and print server.

And yes, I have the script and used it yesterday to setup the smb.conf file.

Add when you open up Dolphin with this, what do you see?

smb://WORKGROUP/

In the Dolphin menu bar (use Ctrl-M to see it if not there) go to View / Location Bar / Editable Location and place a check there. You can also just press F6 I think to get the edit bar. And paste in your smb workgroup command and show me what you get. This is what I see using this for my workgroup:

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

You should see your own share, even if there is nothing else out there. Also, did you read and understand the issue about your Hostname? You decided to set it in your smb.conf file as in “netbios name = scott1”. You can open up a terminal session and type in

hostname

To see your host set network name. If you remark out this line in your smb.conf, you will then use the name set by hostname (not including the site name). I suggest you should use the PC host name, not setting it in your smb.conf file and to never set bo names to the same, in the smb.conf and in the openSUSE hostname. YOu could show us if you have any users in your local Samba database. Open up terminal and type in this command:

sudo pdbedit -L -v

You could then post the reults of that command. What on the WIndows side are you sharing? Did you enter the ect same user in Windows with the same user password by chance?

Thank You,

in dolphin, entering smb://workgroup/, I get "Timout on server - workgroup. On this is on the machine that runs opensuse 12.3.

For the hostname command the results I get is: scott1.site1 which the “.site1” comes from a setting in the network settings/hostname/dns/domain name. Should that be nothing is entered in that field?

The results of the pdbedit command is:

scott1:/etc/samba # pdbedit -L -v

Unix username: scott
NT username:
Account Flags:
User SID: S-1-5-21-3795931333-1542971109-2798605162-1000
Primary Group SID: S-1-5-21-3795931333-1542971109-2798605162-513
Full Name: Scott
Home Directory: \scott1\scott
HomeDir Drive:
Logon Script:
Profile Path: \scott1\scott\profile
Domain: SCOTT1
Account desc:
Workstations:
Munged dial:
Logon time: 0
Logoff time: Wed, 06 Feb 2036 10:06:39 EST
Kickoff time: Wed, 06 Feb 2036 10:06:39 EST
Password last set: Wed, 24 Apr 2013 17:57:35 EDT
Password can change: Wed, 24 Apr 2013 17:57:35 EDT
Password must change: never
Last bad password : 0
Bad password count : 0
Logon hours : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

Unix username: scott-lt
NT username:
Account Flags:
User SID: S-1-5-21-3795931333-1542971109-2798605162-1001
Primary Group SID: S-1-5-21-3795931333-1542971109-2798605162-513
Full Name: Scott Laptop
Home Directory: \scott1\scott-lt
HomeDir Drive:
Logon Script:
Profile Path: \scott1\scott-lt\profile
Domain: SCOTT1
Account desc:
Workstations:
Munged dial:
Logon time: 0
Logoff time: Wed, 06 Feb 2036 10:06:39 EST
Kickoff time: Wed, 06 Feb 2036 10:06:39 EST
Password last set: Mon, 28 Nov 2011 13:04:07 EST
Password can change: Mon, 28 Nov 2011 13:04:07 EST
Password must change: never
Last bad password : 0
Bad password count : 0
Logon hours : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
scott1:/etc/samba #

From the Windows side of things I have the c drive shared but only with authenticated users.

On 4/25/2013 1:16 PM, svetter88 wrote:
>
> in dolphin, entering smb://workgroup/, I get "Timout on server -
> workgroup. On this is on the machine that runs opensuse 12.3.
>
>
svetter88;

  1. What is the name of the workgroup on Windows 7?

  2. Can you ping Windows 7 from openSUSE and vice versa?
    From Linux use:


ping -c3 <IPofWin7>

From Windows in “command prompt” (in Accessories) enter:


ping <IPofLinux>

  1. Are file and print sharing allowed through the Windows 7 firewall?

  2. Is “network discovery” turned on on your Windows 7 machine.

  3. As you have set the netbios name in your smb.conf this should not matter. But, set your hostname to “scott1” and the domain to
    “site1”.

  4. Are all the machines in the same subnet e.g. 192.168.1.0/24?

  5. From a Linux terminal what do you get from:


nmblookup -B <win7name> '*'

You should get back the IP of the windows 7 machine.


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

So you have set the same hostname in openSUSE and Samba which is not needed and may cause problems. Please remark out this line in your smb.conf file and restart smb and nmb.

# netbios name = scott1

Thank You,

The netbios name line has been commented out in smb.conf. And both the nmb and smb services have been stopped and started.

Now for the others…

svetter88;

  1. What is the name of the workgroup on Windows 7?

WORKGROUP

  1. Can you ping Windows 7 from openSUSE and vice versa?
    From Linux use:
    Code:

ping -c3 <IPofWin7>

YES and the times are less than 0.4 ms

From Windows in “command prompt” (in Accessories) enter:
Code:

ping <IPofLinux>
Done… And get time<1ms

  1. Are file and print sharing allowed through the Windows 7 firewall?
    For the purposes of getting the network going I have temporarily disabled the McAfee firewall. (When done trying this stuff out I turn it back on as I don’t want firewalls causing any more problems till after I get this going).

  2. Is “network discovery” turned on on your Windows 7 machine.
    Yes, I did check that.

  3. As you have set the netbios name in your smb.conf this should not matter. But, set your hostname to “scott1” and the domain to
    “site1”. Per a later message about this I commented out the netbios name line and restarted the smb and nmb services.

  4. Are all the machines in the same subnet e.g. 192.168.1.0/24?
    Yes, the Linux machine is .1 and the Windows 7 is .2

  5. From a Linux terminal what do you get from:
    Code:

nmblookup -B <win7name> ‘
You should get back the IP of the windows 7 machine.
What I get is:
scott1:/etc # nmblookup -B Scott-HP '

querying * on 192.168.1.255
192.168.1.1 *<00>

Which to me looks wrong.

So in your Windows PC, you indicated you were sharing (only?) a password protected user area. Do you have more than one driver letter in this copy of Windows? Can you create a drive letter or partition not in the user area you can share to all? Let me say that while I do and can get to Linux user areas by specifying smb://pcname/username, in Windows I typically share a drive letter like D: and keep the C: drive private. Having a share in Windows that all can use allows the PC name to also show up in all Linux systems. On Linux systems, I have one or more NTFS partitions which I share from Linux (they are dual boot) and which do not need a password. When you do try to remotely access a user area as in smb://pcname/username on the remote PC, that user must exist on the remote system and I must enter the user name and password to gain access. Because it is not browesable, it does not show up in a smb://workgroup look in Dolphin. By adding open shares on Windows and Linux, there is something to browse to with Dolphin. Consider that in your local setup.

Thank You,

On 4/25/2013 7:06 PM, svetter88 wrote:
>
> The netbios name line has been commented out in smb.conf. And both the
> nmb and smb services have been stopped and started.
>
> Now for the others…
>
>
> 5. As you have set the netbios name in your smb.conf this should not
> matter. But, set your hostname to “scott1” and the domain to
> “site1”. Per a later message about this I commented out the netbios
> name line and restarted the smb and nmb services.
>
> 6. Are all the machines in the same subnet e.g. 192.168.1.0/24?
> Yes, the Linux machine is .1 and the Windows 7 is .2
>
> 7. From a Linux terminal what do you get from:
> Code:
>
> nmblookup -B <win7name> ‘
> You should get back the IP of the windows 7 machine.
> What I get is:
> scott1:/etc # nmblookup -B Scott-HP '

> querying * on 192.168.1.255
> 192.168.1.1 *<00>
>
> Which to me looks wrong.
>
>
svetter88;
I suggest you make the hostname change in (5) above as well as commenting out the “netbios name” parameter.

As I read your reply to 6, your Windows 7 machine (scott-hp?) is suppose to be at 192.168.1.3 and your openSUSE machine (scott1?)
at 192.168.1.1. nmb is returning 192.168.1.1 for the Windows 7 machine. Do you have a router? These are typically at 192.168.1.1.
Check your IP numbers. On Windows use:

 ipconfig 

and on openSUSE

 /sbin/ifconfig 

If there is a router what is its IP? All three of these need to be distinct and all with the same mask 255.255.255.0.

Here is what I get with nmblookup on openSUSE 12.3. euler2 (192.168.0.189) is openSUSE, sal2 (192.168.0.100) is Windows Vista and
gauss (192.168.0.184) is Windows 7.


venzke@euler2:~> nmblookup -B  euler2 '*'
querying * on 192.168.0.189
192.168.0.189 *<00>
venzke@euler2:~> nmblookup -B sal2 '*'
querying * on 192.168.0.100
name_query failed to find name *
venzke@euler2:~> nmblookup -B gauss '*'
querying * on 192.168.0.184
name_query failed to find name *

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

All machines have a subnet mask of 255.255.255.0. The Windows 7 machine, verified by the ipconfig command is 192.168.1.2. And Linux is 192.168.1. Yes there is a router but before that is a hub that is connected to the both the Linux machine and the Windows machine. The router sits between the LAN and the DSL connection.