Technical data

Connecting Instruments to LAN 5

Agilent Connectivity Guide 125

.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, to send a

route add command, open a Command Prompt

window. When the

Command Prompt window opens, type route add

, where <Instrument IP_address>

is the IP address of the instrument and

<PC IP Address> is the IP address

of the instrument. Then press the

Enter key.

For example, if the IP address of your PC is 155.139.103.152 and the

instrument address is 169.254.58.10, the two devices are probably on

different subnets. To add the instrument to the subnet for the PC, use

one of the following:

! route is lost when the PC is rebooted

route add 169.254.58.10 155.139.103.152

! route persists when the PC is rebooted

route -p add 169.254.58.10 155.139.103.152

NOTE

If your devices are connected to site LAN, do not use the route add

command.