eAutoClub, Inc.

            How to Check Network Connectivity


            Network activity between two machines within a network is blocked, throttled, or restricted.


            ServiceIntelligence designates a single machine as its' server machine. This machine is the one that processes the Management System data, synchronizes information between SI and the management data, contacts the SI remote servers for authorization to run, and controls the client machines on the network. The idea is to check network connectivity between the computer that is acting as a server and any given client computer on the network.

            If you are having connectivity problems, you can use the ping command to check the destination IP address you want to reach and record the results. The ping command displays whether the destination responded and how long it took to receive a reply. If there is an error in the delivery to the destination, the ping command displays an error message.

            You can use the ping command to:

              • Ping your computer (by address, not host name) to determine that TCP/IP is functioning. (Pinging your computer does not verify that your network adapter is functioning.)
              • Ping the local router to determine whether the router is running.
              • Ping beyond your local router.
            Here is a helpful video: http://youtu.be/ABO3af3CcX0


            If you call ipconfig /all and receive a response, there is no need to ping the loopback address and your own IP address — Ipconfig has already done so in order to generate the report.

            It is best to verify that a route exists between the local computer and a network host by first using ping and the IP address of the network host to which you want to connect. The command syntax is:

            ping < IP address>

            Perform the following steps when using Ping:

              1. Ping the client ip address from the server and from the client to verify that TCP/IP is installed and configured correctly on the local computer.
              2. ping <client ip address>
              3. ping <server ip address>

            If the loopback step fails, the IP stack is not responding. This might be because the TCP drivers are corrupted, the network adapter might not be working, or another service is interfering with IP. (network service = antivirus or firewall).


            SI Communicator is ONLY installed on the SI Server. Multiple instances of SI Communicator (across multiple machines) indicates that the setup contains multiple server installations. Normally firewalls like norton System security block network connectivity between server and client computers unless expressly set not to.

            Updated: 19 Jul 2018 03:12 AM
            Help us to make this article better
            0 0