nmb errors overflowing onto console

[J. Seth Henry]

Hello everyone,
I have a curious problem that seemingly came out of nowhere. After
searching through the archives, I see that I am not the first to discover
this problem, but so far, no solution has been found. In June 99, Mark
Drummond mentioned a similar problem.

Recently, I started seeing nmbd errors on the console. A little poking
around revealed a log file full of these errors. Below is a sample of a
previous /var/log/samba/log.nmb:

[1999/09/10 17:03:17, 0]
nmbd/nmbd_packets.c:find_subnet_for_nmb_packet(1412)
  find_subnet_for_nmb_packet: response record not found for response id
35986
[1999/09/10 17:15:21, 0]
nmbd/nmbd_responserecordsdb.c:find_response_record(240)
  find_response_record: response packet id 35996 received with no matching
recor
d.
[1999/09/10 17:15:21, 0]
nmbd/nmbd_packets.c:find_subnet_for_nmb_packet(1412)
  find_subnet_for_nmb_packet: response record not found for response id
35996
[1999/09/10 17:15:22, 0]
nmbd/nmbd_responserecordsdb.c:find_response_record(240)
  find_response_record: response packet id 35998 received with no matching
recor
d.

It repeats this every few seconds until the log file is full, then spills
to the console.

First, what is causing this? Samba appears to work, and so far no users
have complained about it. Were it not for this irritating problem, the
whole shebang would be perfect.

Second, is there a way to stop it. The debug level is already set to 0,
and I hate to set up a cron job to delete the file every so often - since
it may contain useful information from time to time.

OS Specifics;
We are running the latest version (2.0.5) on RedHat 6.0. We have a blend
of linux, WinNT4/95/98 (and one NT5 beta system) and Solaris (for Intel)
2.6. The problems didn't start until after we replaced our hubs with
switched ethernet. As far as I know, the switches were installed properly,
and nothing else has been affected by them. Personally, I suspect the NT5
(RC1) beta system is putting out something bad - but I can't verify that.

Thanks for any help, or workarounds,

Seth Henry
jshenry at net-noise.com