summaryrefslogtreecommitdiff
path: root/source4
diff options
context:
space:
mode:
authorStefan Metzmacher <metze@samba.org>2007-02-13 15:17:29 +0000
committerGerald (Jerry) Carter <jerry@samba.org>2007-10-10 14:48:09 -0500
commitaa5677040cd675dbf650f1f8acdfdb687f989978 (patch)
tree9f1473afcdb697fba897b740f811e80ec2a80504 /source4
parent43a0c615a3f2b8da0baa99090ed0049d13212085 (diff)
downloadsamba-aa5677040cd675dbf650f1f8acdfdb687f989978.tar.gz
samba-aa5677040cd675dbf650f1f8acdfdb687f989978.tar.bz2
samba-aa5677040cd675dbf650f1f8acdfdb687f989978.zip
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)
Diffstat (limited to 'source4')
-rw-r--r--source4/libcli/nbt/nbtsocket.c2
1 files changed, 1 insertions, 1 deletions
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);