ProCate Advanced Settings and Application Tips (1)

WinGate is a complete proxy/firewall solution from Qbik Software Inc., running under Windows 95 and Windows NT. By running the WinGate proxy server on a machine that has a connection to the Internet, multiple users on the LAN (even a wide area network with TCP/IP connectivity) can access the Internet through the proxy server. The connection can be dial-up or ISDN, etheric Network interface, etc. For SMEs or companies' internal networks and Internet bars, access to the Internet through WinGate agents is an economical and practical solution. The current popular version of WinGate is WinGate 4.3, which is divided into a short version and a professional version (the free trial version can be downloaded from the Internet site http://webnz.com/qbik/, etc.). This article uses the most extensive version of WinGate4.3forNT Professional to talk about some of the techniques in its configuration and use.

After WinGate 4.3 is installed, use GateKeeper for configuration and monitoring. GateKeeper is a powerful remote control and configuration program that communicates with the WinGate core engine by establishing an encrypted TCP/IP connection for remote operation of WinGate. There are two ways to install GateKeeper on the client. First, after WinGate2 is installed, copy the following files to the client that needs to perform remote operation of WinGate: GateKeeper.exe, .hlp, WinGate4.3.cnt, wg2util.exe, wg2auto .ini. Another easier way is to set the WinGate directory on the server to share (set shared properties according to your needs, such as setting read-only passwords), and use GateKeeper through file sharing.

WinGate itself manages and maintains a user database that stores user and user group information for targeted setup and logging and auditing of individual users. WinGate has the general function of firewall, security policy is complete and flexible, and each agent service can be managed separately. Authorization can be based on user/group, time or specified workstation address. This means that an administrator can specify not only who has certain permissions, but also when and where to access them. Through a combination of various access restrictions, administrators can effectively filter and limit the exchange of information between the intranet and the Internet.

The general user mainly uses the WWW proxy service. In fact, WinGate has a strong proxy function. For most common network applications on the Internet, WinGate can provide proxy support. Some applications can tell the gateway which server to connect to (such as IE, CuteFtp, etc.), but some do not (such as news, email, etc.). If the application can't tell, the user must pre-configure the mapping proxy (MappingProxy) in WinGate, in this way, tell WinGate which server to connect to. Although mapping agents may have some limitations compared to other agents, they are simply pipes of data. For this reason, you need to specify the target host to connect to when configuring the mapping proxy service. You can specify a default host and port number. But this approach is more versatile, it provides support for general network applications based on TCP or UDP connections.

Sometimes, I want a more flexible mapping. For example, some users may wish to use one news server, while others may wish to use another news server. WinGate2 allows a specific mapping link to be provided based on the user or workstation address, ie no default mapping is used for users or workstations that meet the mapping criteria.

WinGate_WWW_Proxy_ServerWinGate4.3WWW Proxy Server is a CERN-compliant HTTP proxy server with WinCate_WWW_Proxy_Server. It supports HTTP requests, FTP requests, and SSLTunneling. The SOCKS server WinGate_SOCKS5_Proxy_server is a proxy server that follows the SOCKS4 and SOCKS5 (RFC1928) standards. Support for RFC1929 certification (clear text authentication) by using the WinGate user database. The WinGateSOCKS server also recognizes HTTP requests and processes them with the built-in WinGate proxy server. Most of WinGate's proxy services can be cascaded, which is the front end of another proxy server of the same type. When used with a web server on an intranet, there are two ways to change the port of the WinGateWWW proxy server, or to change the web server port in a better way. When configuring the WWW proxy service for WinGate 4.3, in the Non-proxyrequest tab, select: Pipetopredeterminedserver (directed to a pre-configured server). In the Server item, enter the host name or IP address of the enterprise internal network WEB server, and enter the port number that the WEB server listens on.