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)

diff --git a/source4/libcli/nbt/nbtsocket.c b/source4/libcli/nbt/nbtsocket.c
index a48f9873c85ef1e19924c11b22c6da2e4351cf10..c1e30fc2457c38f4424ae7a9d20b13c918b215bf 100644 (file)
--- 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);