Knowledgebase: LAN Clients
Client connection methods
Posted by Adrien de Croy (Import) on 18 August 2005 03:43 PM
After TCP/IP is installed on the client machines and IP addressing has been configured, the next step is to choose which connection method your clients will use to access the Internet.
WinGate offers the choice of three different methods that clients on the LAN can use when connecting through WinGate.
Follow the links below for instructions on configuring your LAN clients to connect to a WinGate server using:
NAT is the easiest of the client connection methods to configure and use.
Network Address Translation happens when clients send their Internet requests to the WinGate server.
The WinGate server keeps track of which client is making the request. The WinGate server then makes the request on behalf of the client, out to the location on the Internet using its public IP address (appearing to the outside world as though it is the computer that originated the request.)
When the Web or remote server sends back the information to the public IP address of the WinGate server, the WinGate server translates the address back to the private address of the relevant client on the LAN, and redirects the incoming data back to that client who originally requested the information.Pros
For many, NAT is an excellent choice. It's particularly well-suited to LANs that contain a mix of Windows platform and non-Windows machines. It is also ideal in situations where you dont want to have to install client software or configure individual applications on many different machines.
When the WGIC is installed, all network/Internet requests from WinSock based applications (most Windows programs) on the client computer will be intercepted
and serviced by the the WinGate Server. This allows administrators to have strong
control over what applications clients use to access the Internet, and how they
will access the Internet.
If you have a small to medium sized LAN of Windows clients or a domain scenario, where control of user Internet applications is required, we recommend using the WGIC.
The Proxy connection is one of the most direct client connection methods used by WinGate.
Rather then configuring the client machine to use WinGate for all Internet access, each application on the client machine such as web browser, mail program, chat program etc must be configured individually to connect through WinGate (proxy server) to the Internet.
Most TCP/IP based programs will have an option to use a Proxy server. This is where access through WinGate will need to be configured.WinGate's specific proxy services (such as HTTP,FTP,Telnet) etc have been specifically designed to handle these types of connections and as such handle the entire connection between the client application and the remote server/site on the Internet.
The WinGate Internet Client and NAT connection methods have decreased the importance of application proxies.
You may still choose to use proxies to exert per-service control over policies, however the advent of transparent redirection means that there is nothing you can do with proxies that you now cannot do with the other two client connection methods.