Secure Multi-Port Gateway

Overview

A WebGateway is a type of security solution that prevents unsecured traffic from entering an internal network of an organization. It is used by enterprises to protect their employees/users from accessing and being infected by malicious Web traffic, websites and virus/malware.

The TWebGatewayService is an executable file that works in association with IIS (Internet Information Services). In the list below you will find more detailed information regarding the installation process and some setting parameters.

Installation

To install the “WebGateway”, run the “InstallTWebGatewayService.exe” application. All the used information for the WebGateway is in the TWebGatewayService.exe.config.  It will create a window services and all output will be sent to windows event viewer. After any modification in the .config file the windows service must be stopped and started.

Using Additional Ports

When using additional ports (ExtraCount parameter), you need pre-configure the TWebGatewayService.exe.config, and then execute the WebGateway installation. The executable “InstallTWebGatewayService.exe” will verify the TWebGatewayService.exe.config and install the additional ports on Windows routing table. Then, after any modification related to the additional port you must follow the steps below:

1. Run in Command Prompt the application: InstallWebGateway /uninstall
2. Modify the file: TWebGatewayService.exe.config
3. Run in Command Prompt the application: InstallWebGateway

Available Parameters

The available WebGateway parameters can be found in the list below:

LocalPort : WebGateway listening port. If you are using ONLY “Windows Authentication” set it to zero (0) and the port won’t be opened.

LocalPortWA: WebGateway listening port using “Windows Authentication”. If you are not using “Windows Authentication” set it to zero (0) and the port won’t be opened.

RemoteIP : Computer IP where is running the runtime server (TServer.exe).

RemotePort : “TServer.exe” listening port without “Windows Authentication”.

RemotePortWA: “TServer.exe” listening port using “Windows Authentication”.

WA:  Force to use RemotePort or RemotePortWA. Do not matters which port the data arrive (LocalPort or LocalPortWA).

     True = Use only Remote Port WA.

     False = Use only Remote Port.

RuntimeUsersProject: [optional] Set which project (tproj) that has the RuntimeUsers data table to validate the users from SmartClient/RichClient.

CheckRunTimeUsersWA: [optional] Set to validate the users from SmartClient / RichClient using “Windows Authentication”.

True = Enabled (Runtime Using Project parameter cannot be used when True).

             False = Disabled.

TargetCF : [optional] Set if the project is being deployed in a Compact Framework environment (WindowsCE) or not.

     True = Enabled

     False = Disabled.

ExtraCount: [optional] Number of additional ports (extra ports). These ports will only route the incoming data in the LocalPort<#> to the RemoteIP<#> and RemotePort<#>.

LocalPort2: WebGateway listening port. It must start in #2.

RemoteIP2:  Computer IP where is running the runtime service.

RemotePort2: “TServer.exe” listening port.

LocalPort3: WebGateway listening port.

RemoteIP3: Computer IP where is running the runtime service.

RemotePort3: “TServer.exe” listening port.

.....

RemoteIP<n>: Computer IP where is running the runtime service.

RemotePort<n>: “TServer.exe” listening port.

Starting the Service

When the WebGateway service is started, log messages can be found in Windows EventViewer.

You should be able to find among the messages one as in the example.

First redirect :: LocalPort: 3101, RemoteIP: localhost, RemotePort: 3101,RemotePortWA: 3102 
Extra Redirection Table:
Listen on ipv4:	Connect to ipv4:

Address	Port	Address	Port
---------------    ----------	--------------- ---------- 0.0.0.0	3100	192.168.80.129	3100
0.0.0.0	3102	192.168.80.129	3101