User`s guide

19
NIC Rx overrun - The Ethernet interface chip used in the LanScaper™
provides internal buffering for multiple packets. If new packets are
received faster than they can be processed, the Ethernet chip discards
the new packets and sets the Overrun error ag. The tester detects and
reports this error. May be caused by excessive broadcast trafc on the
LAN, or by externally generated packets addressed to the tester’s IP
address.
NIC Tx timeout - The Ethernet interface chip used in the LanScaper™
was not able to transmit a packet within the time allowed. May be
caused by a hardware problem inside the tester, a problem with the
attached cable, hardware problems with the connected device, excessive
LAN trafc or collisions on the LAN.
No IP address - The DHCP server responded to the tester DHCP
request, but did not provide an IP address for MyIP.
Packet Rcv Err - An Ethernet packet was received by the LanScaper™
with errors in the header or packet data. May be caused by excessive
signal noise on the Ethernet cable or a hardware problem with the device
transmitting to the tester.
PING Test Detailed Status Messages - these messages may be
displayed when the SEL button is used to access the status details
during active PINGing.
IP add = DNS add - The active Target IP address is the same as
the DNS Server IP address, so the Target PING is automatically
disabled.
IP add = Rtr add - The active Target IP address is the same as the
Router IP address, so the Target PING is automatically disabled.
No ARP Response - The IP address active for this conversation is
being ARP’ed but is not responding. The IP address may be unused,
the device may be powered off or not connected.
No PING Response - The IP address active for this conversation
is not responding to PING requests. If the addressed device is on
the LAN segment, it may be powered off or not connected. If the
addressed device is remote, it may be inaccessible due to WAN
problems, it may be powered off or the device at the Router IP
address may not be forwarding the PING packets.
No Rtr Response - The IP address is off the LAN, requiring the
PING to go through the Router, but the Router IP address is not
responding to ARP.
No Router IP - The DHCP server did not provide an IP address for
the Router