LanScaper
TM
NIC init err -
NIC Rx overrun -
NIC Tx timeout
No IP address -
Packet Rcv Err -
PING Test Detailed Status Messages -
IP add = DNS add
IP add = Rtr add
No ARP Response -
No PING Response -
No Rtr Response
No Router IP
Rtr must be on MyIP LAN segment
Voltage Found, SEL Jack ID
.
Enet Pwr source Found = xV
The Ethernet interface chip used in the LanScaper™ reported a problem to the CPU
during internal initialization. May be caused by a hardware problem inside the tester.
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 flag. The tester detects and reports this
error. May be caused by excessive broadcast traffic on the LAN, or by externally generated packets
addressed to the tester's IP address.
- 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 traffic or
collisions on the LAN.
The DHCP server responded to the tester DHCP request, but did not provide an IP
address for MyIP.
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.
these messages may be displayed when the SEL button is
used to access the status details during active PINGing.
- The active Target IP address is the same as the DNS Server IP address, so
the Target PING is automatically disabled.
- The active Target IP address is the same as the Router IP address, so the
Target PING is automatically disabled.
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.
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.
- 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.
- The DHCP server did not provide an IP address for the Router
- Displayed in Setup while setting the Manual Router IP
address. The LanScaper™ requires that the Router be at an IP address on the LAN segment as
defined by the Netmask and MyIP addresses. Setup will not allow the Router IP address to be set to
an off-LAN address.
- The tester does not operate in Network modes when voltage, and
possibly destructive power, is found. Voltages found will terminate the test in progress and the only
option is to run the Jack ID test (by pressing SEL). The only exception to this is the possibility of
an Ethernet power source providing power between the 1-2 and 3-6 pairs. In that case, the
following message will be displayed
- Some devices provide power for IP-phones or wireless
transceivers on the same wires that carry the Ethernet data signals. They do this by connecting a
voltage to the center-taps of each transformer in their Ethernet interface. The LanScaper™ reports
this and allows the Network testing to continue.
Summary of Contents for LanScaper NT700
Page 1: ...LanScaper TM OPERATING INSTRUCTIONS...
Page 4: ......
