Le 16/03/2015 10:18, Earl A Ramirez a écrit :
I replicated your settings on a CentOS 7 on a KVM, I did not see the
samba server when I click on "Browse Network", however when I enter
smb://<server_IP_address>/ I was able to see the shares.

If Im not mistaken the 'nmb' service is responsible for browsing,
therefore I stopped it and I was not longer able to see the shares from
a windows or samba client.

What is the output of:
$ smbclient -L <samba_server_host-or-IP> -U <samba_user>
from one of the samba clients?

Here's what I got. My Samba test server is amandine.microlinux.lan, my two test client machines are bernadette.microlinux.lan and raymonde.microlinux.lan. From either of these client machines, I can't browse the network, but I can do what you suggested, e. g. :

Ctrl + L ==> smb://amandine

This shows the shares, and I can access them correctly.

Here's what the suggested smbclient command from one of the client machines looks like:

[kikinovak@bernadette ~]$ smbclient -L amandine -U kikinovak
Enter kikinovak's password:
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 4.1.1]

        Sharename       Type      Comment
        ---------       ----      -------
        Public          Disk      Partage Public
        Confidentiel    Disk      Partage Confidentiel
        IPC$            IPC       IPC Service (Serveur de fichiers AMANDINE)
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 4.1.1]

        Server               Comment
        ---------            -------
        AMANDINE             Serveur de fichiers AMANDINE
        NAS

        Workgroup            Master
        ---------            -------
        WORKGROUP            AMANDINE

So it looks like browsing does not work. What now?


--
Microlinux - Solutions informatiques 100% Linux et logiciels libres
7, place de l'église - 30730 Montpezat
Web  : http://www.microlinux.fr
Mail : i...@microlinux.fr
Tél. : 04 66 63 10 32
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Reply via email to