network-config-s-server.md— title: “Appendix: Network Configuration Issues for s-Server” date: “2017-11-19”

draft: false

This topic describes two potential network configuration issues for s-Server, related to hostnames and firewalls.

Server and Host Issues for Development and Test Machines

The most important consideration is the host name. s-Server needs to be able to resolve its own hostname. For dedicated servers, this is usually not a problem, as they will be listed in the network’s DNS.

However, for development and test systems that use DHCP to obtain their IP addresses, you may need to configure these for local name resolution. With many Linux systems, the system installation sets up the network and prompts the user for a host name for the host. However, sometimes the installation only writes this to the network configuration (usually /etc/sysconfig/network), but not to the hosts file (/etc/hosts*). As a result, s-Server can’t figure out what IP address to bind itself to, and will fail. The s-Server installer attempts to check for this condition, and will refuse to install on a system that canmot resolve its own name. If that happens, you can check for yourself at the command line by typing either

hostname -i

or

hostname -f

One or both of those will probably return an error, such as hostname: Unknown host If you check the /etc/hosts file, you will likely find something like this:

127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6

You will need to edit the /etc/hosts file to add the host name of your system. For example, if your system’s host name is myserver, you need to add that host name to the 127.0.0.1 line in /etc/hosts:

127.0.0.1   myserver localhost localhost.localdomain localhost4
localhost4.localdomain4

Note: You need administrative (root) privileges to change /etc/hosts, so you either need to log in as root or use sudo. You should now be able to get correct results from the hostname -i and hostname-f commands, and the s-Server installer should work correctly.

Firewall Issues

If you will be accessing your s-Server from another system, you need to make sure the server’s firewall permits access to the proper ports.

If your clients (s-Studio, sqllineClient, any agents) all run on the same system with s-Server, firewalls are not an issue. But if, for example, you want to run s-Studio on a Windows system to access s-Server, the firewall needs to allow access. Consult your system documentation for specific information on how to open ports.

Note: Only TCP ports need to be opened. UDP ports can be left alone.

The following describes the various ports you might need to open on your server. Keep in mind that these are the default ports. If you choose to run your server or utilities on non-default ports, you will need to open those ports for remote access.