TCP/IP Protocol

Sage 100 uses the TCP/IP protocol for all communications between the workstation and server. TCP/IP must be properly configured on both the Windows server and all workstations.

Although this section discusses configuration settings and options available in configuring a TCP/IP network, it is not a guide for installing TCP/IP on your server or workstation. Contact your Windows systems consultant for specific information regarding the installation and configuration of TCP/IP on your network.

Warning! Do not make changes to the TCP/IP configuration without consulting your system administrator.

Basic Configuration

There are no specific requirements for your Sage 100 system with regard to the configuration of TCP/IP. To determine if a workstation is communicating with a server or vice versa, ping the server or workstation.

To ping a server or workstation

  1. In the Windows Search field, type CMD, and then open the Command Prompt window.
  2. In the Command Prompt window, type PING MACHINE_NAME, where MACHINE_NAME is the name of the server or workstation with which you are attempting to communicate.

  3. If you are successful in communicating with another machine, a response similar to the output below will appear.

    C:\WINDOWS>PING SERVER

    Pinging SERVER [128.0.153.253] with 32 bytes of data:

    Reply from 128.0.153.253: bytes=32 time=1ms TTL=32

    Reply from 128.0.153.253: bytes=32 time=1ms TTL=32

    Reply from 128.0.153.253: bytes=32 time=1ms TTL=32

    Reply from 128.0.153.253: bytes=32 time=1ms TTL=32

    C:\WINDOWS>

If you do not get a response and receive messages such as “unknown host MACHINE_NAME” or “timed_out,” then the computer with which you are attempting to communicate is not receiving or acknowledging information from the workstation. This indicates that either TCP/IP is not configured correctly on the server or workstation, or the server is unreachable.

If the workstation cannot find a server by its name, it is likely that a name resolution mechanism is not in place. If this is the case, go to the server to find its IP address or contact your system administrator. You will receive a Bad IP address message dialog box if your name resolution is not working.

If you receive an error message when running the Ping program, it is possible that the workstation itself is not configured properly for TCP/IP. Contact your system administrator or a Windows system consultant for assistance in configuring TCP/IP.

Important! If an Internet connection is used in your Sage 100 infrastructure, make sure adequate precautions are taken to secure the data traveling through those connections.

Testing the Configuration for Sage 100 Advanced and Premium

After installing Sage 100 Advanced or Premium, test the TCP/IP configuration.

To test the configuration

  1. At the server, use the built-in NETSTAT utility or equivalent software to verify that the Application Server is running on its configured port. The default port is 10000.
  2. From each workstation, ping the Application Server on its configured port. The TCP/IP built-in ping.exe utility does not provide a way for pinging a specific port. The network administrator should use port scanning software or equivalent to ping the specific port the Application Server is listening on.

Note: If you encounter problems pinging the server, see Pinging a Server or Workstation.