User`s guide

113
Troubleshooting Guidelines
Troubleshooting LAN Interfaces
A typical display follows where ping was not successful.
Using the route add
Command
“If you are having difficulty with a private LAN (using a hub, switch, or even a
simple crossover cable), a possible cause for no communication between
the PC and connected instruments is that the PC has not recognized that
it is connected to two different subnets. (See Local and Remote Networks
for
details.)
One way to put the PC and the instrument on the same subnet is to use
route add <Instrument IP Address> <PC IP Address> from the Command
Prompt
. If this action does not correct the problem, go to Web Browser
Checks.)
Example: Using the route add Command
For example, on Windows 2000 to send a use the route add command,
click
Start | Programs | Accessories | Command Prompt. When the
Command Prompt window opens, type route add <Instrument IP Address>
<
PC IP Address>, where <Instrument IP_address> is the IP address of the
instrument and
<PC IP Address> is the IP address of the instrument, and
then press the
Enter key.
NOTE
If your devices are connected to site LAN, do not use the
route add
command.