NMBD Error Messages

Support
1

NethServer Version: NethServer release 7.7.1908 (final)
Module: nmbd

Cheers Community,
i had a great start with NethServer and everything is working as intended except for 2 errors i get in the log. I think those messages are samba related and i wasnt able to find anything about them.

First one is the following

…/source3/nmbd/nmbd_namequery.c:245(query_name)

Second one is

send_netbios_packet: send_packet() to IP 172.24.255.255 port 137 failed

They show up multiple times a minute and im not quite sure what the actual problem is. :smiley:
Does anyone has a clue what the actual problem is?

Thanks in advance
Patrick

2

Hi @Sl0th, and welcome to NethServer community!

I searched those strings in /var/log/messages* but no matches were found. I don’t know what they mean. Maybe nmbd sends a netbios-ns broadcast query but there’s no peer available… What are your clients? Do they have netbios ports enabled? Are you sure there’s somebody listening?

I’m not a windows expert but netbios name resolution could be disabled in newer clients.

1 Like
3

Hi,
thanks for the quick reply. There are 6 Windows 10 Clients and a NAS.

Is there a possibility to disable that netbios query?

4

I don’t know, but if you can make a quick experiment… :slight_smile:

  1. stop nmb: systemctl stop nmb
  2. check everything still works with name resolution
  3. start nmbdagain: systemctl start nmb

You can do the same from the Cockpit Server Manager under System > Services > nmb

5

Hi,
I will check that when im back in the Office this evening.

6

Cheers,
yesterday was quite a busy day :smiley:

I did that experiment you told me yesterday and that worked as soon as i stopped NMB i got the following Log Message

Got SIGTERM: going down…

Which is what i told that daemon to do and after that no more errors as soon as i enable nmb again the errors are comming back.

7

Ok did you run some tests from your clients while nmb was stopped? A quick stop/start by itself cannot prove nmb is useless :slight_smile:

In any case tcpdump can give us more information

8

What tests would you suggest while it is down?

From what I understand is NMB used for mixed networks with Win Clients from 95 up to XP, is that correct? In that case NMB might not be necessary.

I might actually tracked down the problem which might be caused by an old Win 2002 SBS. I will check this evening when the staff is out of the office :smiley:

EDIT:
While NMB was stopped i was still able to access the server shares & mail.

1 Like