Integrating WinGate with other servers contents.gifprev1.gifnext1.gif

Integrating WinGate with other servers

wingate200000024.gif Back to Services

Some computers have servers other than WinGate running on the WinGate machine. Most (probably all) of these servers will run alongside WinGate very smoothly. The main point to remember is that you can only have one application listening on any one port at any one time. There are two common ways to achieve this.

Proxy option:

You can chance the port that the conflicting WinGate service is running on. You will have to enter the new proxy details into clients setup or make use of the PAC files

A company has an FTP server for staff to use. They have a full-time connection to the internet.

The administrator decides to install WinGate, to allow the whole network to access the Internet.

1. He installs WinGate on the machine that is connected to the Internet and runs GateKeeper.

2. In GateKeeper he sees that WinGate FTP service on port 21 failed to start.

3. He changes the WinGate FTP Service port to 8021.

4. Now in all the FTP client applications, 8021 is used for the firewall port.

5. The FTP server still runs on port 21.

Non-Proxy option:

The best solution is to change the port on which the server (not the WinGate service) runs. It is usual to add 8000 to the original port number, eg 8080 for WWW servers, or 8110 for POP3 servers. Then with a small alteration to the proxy, you will have seamless access to both the server and the proxy.

Example

A company has a WWW server for the company webpages. They have a full-time connection to the internet.

The administrator decides to install WinGate.

1. He installs WinGate on the machine that is connected to the Internet and runs GateKeeper.

2. In GateKeeper he sees that WinGate WWW service on port 80 failed to start.

3. He changes the WWW server to run on port 8080

4. He opens the WWW proxy properties and selects the Non-proxy request tab.

5. He selects Pipe request through to a predetermined server

6. He enters the IP of the WinGate machine, and port 8080

7. He saves this configuration and restarts the service.

8. Client configuration is the same as for normal proxy use and the Webpages can still be accessed normally.

Servers on different machines.

With WinGate, it is easy to run servers such as mail, FTP or WWW, on different machines. These machines connection to the Internet is via WinGate. This is simple, and can be more secure.

The two common ways to achieve this are these.

Use a mapped link from the appropriate port on the WinGate machine to the server on the workstation, or make use of the Non-proxy capability of the WinGate services to pipe to the server on the workstation.

The non-proxy approach is often convenient as it allows both proxy and non-proxy operations on the same port.