All network services in WinGate need to be able to listen for, and respond to client requests. This is achieved by making each service use an appropriate network adapter on the WinGate server to listen for each request. Configuring a service to listen on a particular network interface is known as binding the interface to the service.
As part of its security, WinGate will automatically try to identify what type of network each of its network interfaces are connected to, based on the IP address details of the adapter.
If the interface has a private IP address, then WinGate will deem that it is connected to a local network and so is trusted by WinGate.
If the interface has a public IP address, then WinGate will deem that the interface is connected to the Internet or an external untrusted network.
You can manually set how WinGate will classify the usage of each network connection in the WinGate specific properties for each network interface. These can be accessed by double clicking on a network connection in the Network Connections panel, located at Control Panel > Network Connections in the WinGate Management console.
Most network services in WinGate will automatically bind any network adapters classified as Internal to their service by default. This allows the network services to be able to listen and respond to client requests from the local network with very little configuration after they are installed.
Read more about interface security in WinGate
Bindings for a network service can be set manually on the Bindings tab for each particular service.
If you wish to have all connections to the service use SSL, then you can enable the SSL check box, and select a suitable preconfigured certificate from the drop down menu. Certificates can be generated on the Certificates panel located at Control Panel > Certificates in the WinGate Management console.
WinGate network services can be bound to any network interface that exists on the WinGate server, including Internet connections. For this reason we recommend being extremely careful when binding network connections marked as External by WinGate (Internet connections) to network services, since this will allow remote Internet users to make requests to the particular WinGate service.
Sometimes you may be required to do this. For example when WinGate Mail is accepting mail for delivery for remote users on the Internet, then the SMTP Server in WinGate needs to be bound to the external network connection so it can listen for SMTP connections from remote WinGate Mail clients.
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:
