Networking Details

OmniRush is designed to operate on a TCPIP network, that can be homogeneous (e.g. %100 Windows PC's) or heterogeneous (e.g. a mix of Windows, Netware, Unix, Linux, etc. systems).

In either event, OmniRush does make some assumptions about your network.  In most all cases, this will already be true of your network without any additional configuration required.  However, for problem sites, or thorough planning, here are the network requirements.

Name to Address Resolution

OmniRush assumes that all PC's involved can resolve each other's PC name to a reachable IP address.  The PC's involved include the OmniRush Server PC, Client PC's that run the OmniRush Administrator, or any of the OmniRush client applications.

This can be done via any name resolution mechanism (e.g. WINS, DNS, hosts file, etc.).  The 'grunt' test is using the command line ping utility.  The OmniRush Server PC and all the client PC's should be able to ping each other by name, e.g. from all client stations you should be able to successfully:

ping <OmniRush Server PC name>

IP Address Allocation

The OmniRush Server PC should have a static IP address.  This can be managed either via the PC local configuration, or by assigning a permanent lease in DHCP to the OmniRush Server PC for a specific address.  This should be set up before any OmniRush software is installed.

Client PC's can use DHCP or static IP addresses.