Network services

WinGate provides a range of services that will listen for, and respond to client requests from across the network. These types of services include application proxy servers, and client administration services such as DHCP and DNS.

Bindings

In order to listen for client requests, a network service must be configured to use the appropriate network interface that the client request will be received on. Configuring a service to listen on a particular interface is known as binding the interface to the service.

Service port

Each network service is also configured with a default service port that it will use to listen and receive application communication on (e.g. Port 21 for FTP, Port 80 for HTTP etc.). Client Internet applications will make their requests to these service ports. In most cases the default service port can be changed as required.

Note

The network interface that is bound to the service can only listen for one instance of a particular service port at any time.

In the case where you install a new service that uses the same service port and network interface as one already in use, you will be unable to bind the network interface to the second service.

In order to bind the adapter to the new service, you will have specify a different service port for it to use. Clients will then have to connect on the new port if they wish to use the second service.

Network service events

When you install a network service, it will register all the events that can occur during its operation with the WinGate Events system. As with all registered events, you can use any of the various WinGate event processors to configure how WinGate will respond when the particular service event takes place. This allows you to control how the service operates, and more importantly, allows you to use the power of the WinGate event processing systems to control user activity through the service.