From aa5677040cd675dbf650f1f8acdfdb687f989978 Mon Sep 17 00:00:00 2001 From: Stefan Metzmacher Date: Tue, 13 Feb 2007 15:17:29 +0000 Subject: r21316: if we got an unexpected nbt packet that most times mean we got a 2nd answer to a broadcast message and have already remove the packet id from out list while getting the first response metze (This used to be commit 8c26e04900da02bdf440f1d48b512e2550e89c34) --- source4/libcli/nbt/nbtsocket.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'source4/libcli/nbt/nbtsocket.c') diff --git a/source4/libcli/nbt/nbtsocket.c b/source4/libcli/nbt/nbtsocket.c index a48f9873c8..c1e30fc245 100644 --- a/source4/libcli/nbt/nbtsocket.c +++ b/source4/libcli/nbt/nbtsocket.c @@ -215,7 +215,7 @@ static void nbt_name_socket_recv(struct nbt_name_socket *nbtsock) if (nbtsock->unexpected.handler) { nbtsock->unexpected.handler(nbtsock, packet, src); } else { - DEBUG(2,("Failed to match request for incoming name packet id 0x%04x on %p\n", + DEBUG(10,("Failed to match request for incoming name packet id 0x%04x on %p\n", packet->name_trn_id, nbtsock)); } talloc_free(tmp_ctx); -- cgit