Samba not visable

English Network/Internet
#1

I have two OpenSuSE 12.2 machines running samba and one Windows 7 machine. The Linux machines run samba. None of the machines can see each other. Prior to 12.2 I could see all the other machines from any machine. Now, nothing is seen.

How do I correct this?

Thanks!

#2

On 11/1/2012 7:46 PM, svetter88 wrote:
>
> I have two OpenSuSE 12.2 machines running samba and one Windows 7
> machine. The Linux machines run samba. None of the machines can see
> each other. Prior to 12.2 I could see all the other machines from any
> machine. Now, nothing is seen.
>
> How do I correct this?
>
> Thanks!
>
>
svetter88;

Here are a few things to check:

  1. Make sure the workgroup is the same on all of your machines.
  2. Make sure that smbd and nmbd are both running.
  3. Make sure the firewall on Opensuse allows these three processes, Samba Server, Netbios
    Server and Samba Client and that any firewall on Windows allows file and print sharing.
    It is often best to disable the firewalls for testing. (Remember to turn them on again
    when you are finished)

You might want to review these two HowTos:
http://opensuse.swerdna.org/suselanprimer.html
and
http://opensuse.swerdna.org/susesambawin7.html

The above should give details on configuring Samba and Windows 7. If you still cannot get
Samba to work, please post the contents of /etc/samba/smb.conf.

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

#3

In addition I have some good examples you can see here. Most likely just requires a change in your /etc/samba/smb.conf file to get everything working just fine.

Samba S.W.A.T. - Samba Web Administration Tool Setup for openSUSE - Blogs - openSUSE Forums

AND

SWAT - Samba Web Administration Tool - Setup & Creation Script - 1.04 - Blogs - openSUSE Forums

And to edit system files look here:

SYSEdit - System File Editor - Version 1.00 - Blogs - openSUSE Forums

Thank You,

#4

Just an update: I have turned off the firewalls on all the machines. Verified that the workgroup name is the same on all the machines. And have with one machine turned off then back on the smbd as well as the nmbd. No joy… Tomorrow I will take a look at the examples you have.

Thanks!

#5

Install samba-winbind.
Add wins to your /etc/nsswitch.conf:

hosts:          files wins mdns_minimal [NOTFOUND=return] dns
#6

You do not need to load samba-windbind unless you have a Windows domain. To use wins with samba, you just need to do two things. On your Linux PC’s running Samba, add the following in the Global section:

[global]
    wins support = yes
    name resolve order = wins lmhosts hosts bcast

And see if that works.

Thank You,

#7

When I setup samba on my 12.2 system, I had the same problem.

It turned out that, when changing the configuration, the Yast module was stopping and restarting smbd, but was only stopping but not restarting nmbd.


# /etc/init.d/nmb restart

fixed the problem (though I might have actually used “start” rather than “restart”).

#8

On 11/3/2012 8:26 AM, jdmcdaniel3 wrote:
>
> PiElle;2501009 Wrote:
>> Install samba-winbind.
>> Add -wins- to your /etc/nsswitch.conf:
>>
>>>
> Code:
> --------------------
> > > hosts: files wins mdns_minimal [NOTFOUND=return] dns
> --------------------
>>>
>
> You do not need to load samba-windbind unless you have a Windows
> domain. To use wins with samba, you just need to do two things. On
> your Linux PC’s running Samba, add the following in the Global section:
>
>
> Code:
> --------------------
> [global]
> wins support = yes
> name resolve order = wins lmhosts hosts bcast
> --------------------
>
>
> And see if that works.
>
> Thank You,
svetter88;

winbind is indeed not needed for a simple home workgroup situation. Moreover setting up
a wins server is generally unnecessary unless you have machines on different subnets,
where broadcasting does not work, or a very large network where multiple broadcasts can
slow the network.

If you do setup a wins server then the server needs a fixed IP and all the other machines
need to be set to use that wins server. On linux machines this is done in smb.conf (wins
server parameter) and on windows machines in the network card configuration.

It is best to just set the name resolve order to have broadcasts first and be done with
it. i.e. in the global section of /etc/samba/smb.conf set the parameter:


name resolve order = bcast host lmhosts wins

The default name resolve order is not very friendly, putting bcast in last place and
lmhosts first. Unless you have fixed IPs and wish to setup lmhosts files on all your
machines name resolution dies before trying bcast(broadcasts).

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