Common LAN Problems

Before SICL over LAN can function, the client must be able to talk to the server over the LAN. You can use the following techniques to determine if the problem is a general network problem or is specific to the LAN software provided with SICL.

See also:

• LAN Client Problems
• LAN Server Problems

Note: In Windows, both the LAN client and LAN server may log messages to the Event Viewer under certain conditions, whether or not an error handler has been registered.

Using the ping Utility

If the application cannot open a session to the LAN server for SICL, the first diagnostic to try is the ping utility. This utility allows you to test general network connectivity between client and server machines.

Using ping looks something like the following, where each line after the Pinging line is an example of a packet successfully reaching the server.

>ping instserv.keysight.com

Pinging instserv.keysight.com[128.10.0.3] with 32 bytes of data: Reply from 128.10.0.3:bytes=32
time=10ms TTL=255
Reply from 128.10.0.3:bytes=32 time=10ms
TTL=255
Reply from 128.10.0.3:bytes=32 time=10ms
TTL=255
Reply from 128.10.0.3:bytes=32 time=10ms
TTL=225

However, if ping cannot reach the host, a message similar to the following is displayed that indicates the client was unable to contact the server. In this case, you should contact your network administrator to determine if there is a LAN problem. When the LAN problem has been corrected, you can retry your SICL application over LAN.

Pinging instserv.keysight.com[128.10.0.3] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.