WinGate 2.1 features

Remote Administration

WinGate 2.1 is controlled and configured using a remote administration tool called GateKeeper. GateKeeper communicates with WinGate over an encrypted TCP/IP link, for all configuration, monitoring, and control. Gatekeeper can be used from any machine with a TCP/IP connection to the WinGate machine . The service that provides this access in WinGate is the Remote Control Service. GateKeeper is used for configuration but is not essential for Internet access itself. You do not have use GateKeeper access the Internet.

User Database

The User database allows logging and auditing per individual user. Groups of users can be defined, and access rights can be assigned on a user or group basis.

Security Policies

Rights can be assigned to users for each service or on a global basis. Rights can be defined according to user/group, location, time of day, or advanced parameters of each particular request.

Client authentication

WinGate’s WWW Proxy incorporates a Java authentication tool. This allows administrators to require authentication without the client needing to run GateKeeper. When a non-authenticated user attempts to access a web page, a ‘Sorry’ page and a logon applet are displayed.

Multiple interface capability

WinGate can make use of multiple Internet connections to give you wider bandwidth and faster access. Combinations of modems, ISDN and direct connections are configurable on a ‘per service’ level to give you full control and the best throughput.

DHCP

DHCP automates the client network configuration for your entire LAN. With full-auto mode or manual mode, the WinGate DHCP will configure IP numbers and DNS for all your client machines.

WinGate dialer

The WinGate dialer takes the chore out of maintaining the Internet connection. Different ISP accounts can be configured, and access can be restricted by users groups and other parameters.

Logging

All Services can be configured to log events. These are stored in a log file or ‘servicename.log’ in the WinGate logs directory.

Scheduler

The scheduler allows the administrator to control many WinGate and system operations on a regular basis. Many operations can be automated, including Log file rollover, WinGate shutdown and command line execution.

WWW Proxy

The WinGate 2.1 WWW proxy is a CERN-compliant caching HTTP proxy server. It supports HTTP requests, FTP requests, and SSL tunneling. The WinGate WWW proxy is also a partial web server. Features include the ability to handle normal (non-proxy) requests in a variety of ways, which makes it a good front-end to your existing WWW server, or even an automatic site mirroring tool. It also allows cascading through another proxy or SOCKS4 server.

SOCKS Server

The WinGate 2.1 SOCKS server is SOCKS 4 and SOCKS 5 (RFC 1928) compliant. It supports RFC1929 authentication using the WinGate User Database. The WinGate SOCKS server is HTTP-aware. It can recognise HTTP requests, and handle them with the built-in WinGate WWW proxy. This means that even your SOCKS users will enjoy the benefits of the WWW proxy (e.g. caching), and can be subject to the same security policies.

FTP Proxy

The FTP Proxy provides access to FTP servers. It uses the username@hostname method of firewall traversal. The FTP Proxy supports non-proxy requests. This allows the proxy to act as a front end to an FTP server, or to cascade through other proxies.

POP3 Proxy

The WinGate POP3 proxy allows access to POP3 servers on the Internet for retrieving email. As with the WWW and FTP proxies, the POP3 Proxy can act as a front end to your POP3 server, giving you a seamlessly integrated mail system. It can also be cascaded through other proxies.

Telnet Proxy

The WinGate Telnet proxy provides access to telnet servers. The Telnet proxy in WinGate 2.1 supports many telnet clients including Unix. Telnet also supports cascading.

DNS Server

The DNS server is a partial implementation. It provides sufficient functionality to use the SOCKS server for SOCKS4 requests. The WinGate DNS server integrates with the DHCP server to allow DNS resolution for computer names on your network. If more functionality is required, Mapping proxies may be used to forward all DNS requests to a full implementation DNS server. Alternatively, you can run a stand-alone DNS server on the WinGate machine.

VDOLive Proxy

This proxy enables all users on the LAN to enjoy live video using the streaming video player from VDONet Corporation. You need to ensure you have the proxy-capable version of the VDOLive player for this. Non-proxy handling also allows you to run your own VDO server, which WinGate can be the front end to.

RealAudio Proxy

The RealAudio proxy allows users on the LAN to access RealAudio servers for streaming audio and video. The proxy-aware version of the RealAudio player (version 2 or later) is required. Non-proxy handling also allows you to run your own RealServer, for which WinGate can be the front end.

Xing Streamworks Proxy

The XDMA proxy allows Xing Streamworks clients to operate on your network.

Mapping Proxies

The Mapping proxies in WinGate provide generic connectivity for both TCP and UDP applications that do not support proxy protocols. Enhanced mapping allows mapped links based on user location or dialer profile. Mapping proxies for TCP support end-to-end encryption. This allows secure WinGate-to-WinGate connections over the Internet or LAN.

Non proxy capability

The non-proxy request (NPR) capability of WinGate allows proxies and servers to run side by side, without the need to access different port numbers. Any non-proxy request to a WinGate proxy can be piped to another server for seamless integration.