find_response_record: response packet id 176 received with no matching record.

[MCCALL,DON (HP-USA,ex1)]

Hi Francesco,
I am not too familiar with this part of the code, but it APPEARS that this
is 
telling you that nmbd received a packet marked as a response packet, but
when nmbd
searched its known subnet db's for a record, in order to route this
response, there
was no match... A couple of things that would help nail this down a bit
better would be 
your smb.conf file (just the [global] part), with ipaddresses and subnets
NOT xxx'ed out,
and the ipaddress and subnet mask being used by one or more of the clients
that are generating these messages; as a wild guess, I would suspect a
network configuration issue with subnet masks,multiple nics, or something
like this...  You might also want to bump your log level up to 10 in the
smb.conf file (BRIEFLY) in order to catch what type of packet is comming in
that is generating this error.  It would help narrow down what might be
wrong.
Good luck,
Don

-----Original Message-----
From: Francesco [mailto:malvezzi at unimo.it]
Sent: Friday, April 27, 2001 4:30 AM
To: samba-ntdom at lists.samba.org
Subject: find_response_record: response packet id 176 received with no
matching record. 


I have a couple of problems about samba as PDC.
I run version 2.2.0 on a linux RedHat 6.2 machine. Everything works
fine, but my /var/log/samba/log.nmdb receives the following warning:

[2001/04/27 10:25:41, 0]
nmbd/nmbd_responserecordsdb.c:find_response_record(239)
  find_response_record: response packet id 176 received with no matching
record.

I have such a warning each half an hour from win98 clients, and much
more often from win200 clients. What is wrong? Any hint?

I have also a easier question. Everytime I logout from my win2000
clients, it warns me that it cannot update the common profile. What is
about?

Thank you for your help. If you need more details, just ask.

Francesco