WinGate offers a range of network proxy services to provide for the handling of client application requests to the Internet. These network services can be configured to listen on an appropriate interface and application port for client proxy connections. Each service is designed to handle proxy requests based on a particular protocol.
With WinGate it is possible to have clients whose applications are not set to make proxy requests (NAT and WinGate Internet Clients) intercepted by the appropriate network proxy service, and subjected to all of the controls and processing offered by that service. This alleviates the need for each application on those clients machines to be configured to use a proxy server. These applications can make their connection directly to the Internet on the usual application protocol port via WinGate, and the appropriate proxy service can be made to intercept the connection.
When you install a WinGate network service, it will register all the events that can take place in its operation with the WinGate Events system. You can then use an appropriate WinGate event processor to control the service operation, and user activity through these services, by specifying how they should respond whenever these service events take place.
Almost all network services in WinGate are now optional. This means that you only need to install the services you require to support client applications and Internet requirements.
When installing WinGate to designated machine on a network, you need to be aware of other services that may be running on the machine that might conflict with WinGate operations and the WinGate services you install.
WinGate offers a host of network services that will listen for and respond to client requests on a selected network interface. These are usually application proxy services for clients, that will listen for client proxy requests on a specific interface. You can configure which interface a WinGate network service should use on the Bindings tab in the properties for that particular service.
In TCP/IP networking, there can never be more then one application using a specific port at anytime on a particular network connection. So you need to ensure that WinGate network services are able to use their service port to listen on a particular interface.
Conflicts can often arise if there are other server applications that listen for application requests on a particular port and network interface, running on the WinGate server. For example, if there is a Intranet web server running on the WinGate server that is listening on port 80 (TCP) on the LAN network connection, then this will conflict with any WinGate WWW Proxy service that uses that LAN adapter to listen on port 80 (TCP) by default.
These conflicts will cause one of the applications to show errors, and not be able to provide functionality. Usually the network application/service that starts first will grab control of the adapter and the competing network application/service will show an error.
When a WinGate network service has an error due to a port conflict, it will display an error on its Bindings tab of its service properties. It will also display the conflict beside its entry on the Services panel located in the Control Panel of the WinGate Management console.
To avoid potential conflicts with these other server applications, nearly all network services in WinGate are now optional and not installed by default. The exception is WWW Proxy server which is installed to provide web connectivity for clients after installation. Be aware that it will bind any adapter configured with private IP address details (marked as Internal) which it thinks is connected to a local network, using service port 80 (TCP) to listen for client requests. It can be set to listen on another application port if there is already an application listening.
Often you can install multiple instances of a particular network service in WinGate (e.g. Multiple WWW Proxy services). If each of these services are set to listen on the same network connection, then they each must be configured to use a distinct service port to listen with.
When there are administrative server applications running on the WinGate server or the local network, such as DNS and DHCP, then you should avoid installing the corresponding WinGate services, as they are not required.
In the case of DNS, the in-built WinGate DNS client will probe any DNS servers it has on its network interfaces to see what type of records they are capable of returning. In this case it will discover the DNS Server listening at the local host address and be able to use that without any further configuration. In this scenario WinGate clients on the LAN can simply use the DNS server on the WinGate server machine for Internet lookups. There will be no need to install the optional WinGate DNS service.
If there is a DHCP Service providing IP addressing to clients on the network, then the optional WinGate DHCP Service is not needed.
You can install each proxy service you require for clients from the Services panel, located at Control Panel > Services in the WinGate Management console. Installation is an easy process, however there are several important things to note.
When you are installing services that listen for, and respond to requests from the network (such as proxy services):
To listen for requests, the service must be configured to use the appropriate network adapter on the WinGate server that clients will make requests to (This referred to as a Binding).
Each network interface can only support listening for one instance of any service port at any time. If the network interface is bound to more then one service, each service must use a unique service port to listen for client requests. See the Conflicting Services section above.
Some services can be installed more then once, and run side by side at the same time if required. This is common amongst network services where you may need to install several instances of service, each for a different purpose.
e.g.
Installing two different WWW Proxy Services to serve two different groups of users. Or configuring one WWW Proxy Service to serve proxy requests, while the other is used to act like a Web server and respond to server requests.
When you are installing more then one instance of a network service to listen for client requests on the same network adapter, then each instance must use a unique service port that users will connect to.
©2012 Qbik New Zealand Limited
no comments yet...
You can use basic Full-Text Searches against the page title and body to find matching articles. Use the following search modifiers to refine your query:
You can create a new account or reset your password at forum.wingate.com.