You are not logged in.
Hello everyone,
I have a Raspberry-Pi host with Arch, where Samba is sharing files and, since last week, RPi also shares a printer (but with CUPS rather than Samba). Since printer sharing (which involved system update and installation of some extra packages) a Windows 7 host that's connected to the network along with RPi, started ignoring nmbd's NetBIOS name broadcasts. The issue is very strange, because only one machine is affected, two others (another Windows 7 and Vista) work properly, as they did before. I still can access Samba shares / SSH by typing the IP though... Also, I don't personally think that printer sharing and this issue are related... But who knows.
The nmbd log contains the following lines (repeated many times):
[2013/07/31 22:44:59, 0] ../source3/nmbd/nmbd_incomingdgrams.c:311(process_local_master_announce)
process_local_master_announce: Server PRZEM-7-L at IP 10.0.0.101 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election.
[2013/07/31 22:44:59, 0] ../source3/nmbd/nmbd_become_lmb.c:150(unbecome_local_master_success)
Samba name server PRZEM-R has stopped being a local master browser for workgroup WORKGROUP on subnet 10.0.0.2
[2013/07/31 22:45:17, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
Samba name server PRZEM-R is now a local master browser for workgroup WORKGROUP on subnet 10.0.0.2
PRZEM-R - Raspberry Pi Server
PRZEM-7-L - Windows 7 client
Also, there were issues with nmbd upon start-up, where the system clock was set incorrectly - this has been fixed before and is not the issue.
First, I would like to clarify whether this is the Samba issue or rather Windows. Next, if it's Samba's - I'd love to fix it with Your help of course
Last edited by madman_xxx (2013-10-15 06:25:34)
Offline
OK, I solved it. The application called "Check Point Endpoint Security VPN" installs the service under the same name. I disabled this service and that was the cause of the network's misbehaviour. Enabling it and starting solved the issue, which turned out to be a Windows 7 / Check Point VPN issue.
Offline