Setting Sygate to run servers in LAN machines

Sygate allows one ISP connection to be shared with other PCs in the same LAN:

Sygate is based on NAT (Network Address Translation).
The advantage of NAT is its application transparency, which means there’s no need set special settings for each program, unlike proxies which require that the programs behind the firewall/proxy be proxy-aware and redirect all requests to the proxy instead of going directly to the Net.
The basic Sygate setup is done by the software itself when is installed. It checks the TCP/IP setup of the machine that will be the NAT server and install files accordingly, including setting Sygate as a service in a NT machine.
You can set up servers in the NAT server machine to be seen in the Net without any other Sygate configuration or setup.
If you want to set up other machines in the LAN as servers accessible from the Net you have to do as follows:
- Open the file Apprule.cfg located in the same directory you installed Sygate,
- create a rule in the following format:
  
  :INIT "Rule Name"
  
  Triggering transaction
  
  :SUB
  
  :END
Triggering transaction format:
{IN or OUT} {TCP or UDP} port port server-IP port.
Lets see an example of making a Real Server (media streaming) accessible to the NET:

:INIT "Real server"

IN TCP 7070 7070 192.168.0.2 7070 0 -

:SUB

:END
In the above example we chose IN as the direction of the connection allowing the server to be accessible from the Net. We chose TCP as the connection protocol. Port 7070 is the standard RealServer port connection. 192.168.0.2 is the IP number of the server in the LAN, which houses or will house the RealServer.
In the example below we create a rule to run a Web server (port 80) in the 192.168.0.7 machine:

:INIT "WEB Server"

IN TCP 80 80 192.168.0.7 80 0 -

:SUB

:END

You can obtain more information on application rules by reading the Apprule.cfg file in a text editor (Notepad, etc).

This page is maintained by Al Bento who can be reached at abento@ubmail.ubalt.edu. This page was last updated on June 12, 1999. Although we will attempt to keep this information accurate, we can not guarantee the accuracy of the information provided.