Re: samba client in big workgroup

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Workgroup is set probably. But I'll check the hostname, because in nmbd.log.1 (the only log with any real output in it) it shouldn't be talking about localhost, should it?
Now that's /var/log/samba/nmbd.log.1:


[2004/04/20 13:46:29, 0] nmbd/nmbd.c:main(665)
Netbios nameserver version 3.0.2-7.FC1 started.
Copyright Andrew Tridgell and the Samba Team 1994-2004
[2004/04/20 13:47:00, 0] nmbd/nmbd.c:terminate(54)
Got SIGTERM: going down...
[2004/04/20 13:47:00, 0] nmbd/nmbd.c:main(665)
Netbios nameserver version 3.0.2-7.FC1 started.
Copyright Andrew Tridgell and the Samba Team 1994-2004
[2004/04/20 13:52:49, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396)
*****
Samba name server LOCALHOST is now a local master browser for workgroup HAUPTHAUS on subnet 192.168.8.109
*****
[2004/04/20 23:08:03, 0] nmbd/nmbd.c:terminate(54)
Got SIGTERM: going down...



Alexander Dalloz wrote:

Am Mi, den 28.04.2004 schrieb Florian Idelberger um 22:00:



here at school I'm located inside a private subnet which offers smb networking capabilities.
everytime I try to access them with konqi or nautilus it says "no master browser found" which simply is not possible, and I have already browsed the network succesfully with other linux distris.
smbclient is installed.


flo



I suspect different SMB machines (Samba and Windows[tm]) are fighting against each other to become master browser. So check your /var/log/samba/ logs and configuration of the Samba hosts.

Alexander







[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux