| Bug ID |
12835
|
| Summary |
Bad description for NBSS error code 0x81
|
| Product |
Wireshark
|
| Version |
Git
|
| Hardware |
All
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Minor
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
commit 6febe27586426ac556b56b491a93fed4c852680a on GitHub
--
When the NBSS dissector sees error code 0x81 in a Negative session response
packet, it calls the error "Not listening for called name". See the table in
epan/dissectors/packet-nbt.c:
static const value_string nbss_error_codes[] = {
{ 0x80, "Not listening on called name" },
{ 0x81, "Not listening for called name" }, <=== HERE
{ 0x82, "Called name not present" },
{ 0x83, "Called name present, but insufficient resources" },
{ 0x8F, "Unspecified error" },
{ 0x0, NULL }
};
This is wrong (and confusing). 0x81 should be "Not listening for calling
name"--"calling" not "called". The error is supposed to indicate the server is
not willing to talk to a client having a certain name. In fact, Samba returns
it when the client is denied access by hosts allow/deny.
See:
<https://tools.ietf.org/html/rfc1002#section-4.3.4>
<http://ubiqx.org/cifs/NetBIOS.html#NBT.6.2>
You are receiving this mail because:
- You are watching all bug changes.
