Table of Contents
Advertisement
NETBIOS:NBNS:C2S_AA_FLAG
NETBIOS:NBNS:C2S_RESPONSE
NETBIOS:NBNS:CLASS-UNKNOWN
NETBIOS:NBNS:INVALID:FIRST-ENC
NETBIOS:NBNS:INVALID:HDR-CNT
NETBIOS:NBNS:INVALID:HDR-OPCODE
NETBIOS:NBNS:INVALID:HDR-Z
NETBIOS:NBNS:INVALID:LABEL-LEN
NETBIOS:NBNS:INVALID:NAME-FLGS
NETBIOS:NBNS:INVALID:PTR
NETBIOS:NBNS:INVALID:RRNB-FLG
NETBIOS:NBNS:NAME_TOO_LONG
NETBIOS:NBNS:POINTER_LOOP
NETBIOS:NBNS:RESCODE:FORMAT_ERR
NETBIOS:NBNS:S2C_QUERY
Copyright © 2010, Juniper Networks, Inc.
This protocol anomaly is query message with an NM_FLAGS
field containing an authoritative answer flag that is set.
This protocol anomaly is query message with an OPCODE
field containing an response flag that is set.
This protocol anomaly is an invalid value in the
QUESTION_CLASS field of the question section or in the
RR_CLASS field of the resource record header.
This protocol anomaly is an invalid first level encoding of a
Netbios name.
This protocol anomaly is a 1) a query message with
ARCOUNT (answer count) or NSCOUNT (number of records
in the authority section of a name service packet) fields of
the header that are not zero, or 2) a response message with
a QDCOUNT (number of entries in the question section) that
is not zero.
This protocol anomaly is a header with an OPCODE field
value that is not 0, 5, 6, 7, or 8.
This protocol anomaly is a Netbios name header with a
NM_FLAGS field that contains nonzero values for bit 4 or bit
5.
This protocol anomaly is a label for the second level
encoding of a Netbios name that has a label length larger
than 63, or the label is the first label and the length is not
32.
This protocol anomaly is a Netbios name header with a
NM_FLAGS field that contains nonzero values for bits 3-15.
This protocol anomaly is a pointer offset in the second level
encoding of a Netbios name that exceeds the message
length (the pointer is pointing out of the message).
"This protocol anomaly is a type node status response
message
This protocol anomaly is a Netbios name that is longer than
255.
This protocol anomaly is a second level encoding of a
Netbios name that contains more nested pointers than the
user-defined maximum. Default setting for the
sc_nbname_pointer_loop_limit is 8.
This protocol anomaly is Netbios name response with an
RCODE that indicates the request has an invalid format.
This protocol anomaly is a Netbios name response header
with an OPCODE field that contains an unset response bit.
Appendix E: Log Entries
medium
sos5.1.0
medium
sos5.1.0
medium
sos5.1.0
high
sos5.1.0
medium
sos5.1.0
high
sos5.1.0
medium
sos5.1.0
high
sos5.1.0
medium
sos5.1.0
high
sos5.1.0
high
sos5.1.0
medium
sos5.1.0
high
sos5.1.0
medium
sos5.1.0
913
Advertisement
Table of Contents
Related Manuals for Juniper NETWORK AND SECURITY MANAGER 2010.4 - ADMININISTRATION GUIDE REV1
Related Products for Juniper NETWORK AND SECURITY MANAGER 2010.4 - ADMININISTRATION GUIDE REV1
- Juniper NETWORK AND SECURITY MANAGER 2010.3 - CONFIGURING INTRUSION DETECTION AND PREVENTION GUIDE REV1
- Juniper NETWORK AND SECURITY MANAGER 2010.4 - API GUIDE REV 1
- Juniper NETWORK AND SECURITY MANAGER 2010.3 - M-SERIES AND MX-SERIES DEVICES GUIDE REV1
- Juniper NETWORK AND SECURITY MANAGER 2010.2 - ADMINISTRATION GUIDE REV1
- Juniper NETWORK AND SECURITY MANAGER 2010.3 - ADMINISTRATION GUIDE REV1
- Juniper NETWORK AND SECURITY MANAGER 2010.4 - CONFIGURING J SERIES SERVICES ROUTERS AND SRX SERIES SERVICES GATEWAYS GUIDE REV
- Juniper NETWORK AND SECURITY MANAGER 2010.4 - NSMXPRESS SERIES II REV 1
- Juniper NETWORK AND SECURITY MANAGER 2010.4 - REV1
- Juniper NETWORK AND SECURITY MANAGER 2010.4 - M-SERIES AND MX-SERIES DEVICES GUIDE REV 1
- Juniper NETWORK AND SECURITY MANAGER 2010.3
- Juniper NETWORK AND SECURITY MANAGER 2010.2
- Juniper MEDIA FLOW CONTROLLER 2.0.4 -
- Juniper SECURITY THREAT RESPONSE MANAGER 2008.2 - AQL EVENT AND FLOW QUERY CLI GUIDE
- Juniper SECURITY THREAT RESPONSE MANAGER 2008.2 - EVENT CATEGORY CORRELATION REV 1
- Juniper SECURITY THREAT RESPONSE MANAGER 2008.2 - SNMP AGENT GUIDE REV 1
- Juniper STRM LOG MANAGEMENT 2008.2 - S 6-2008