Here, you can manage the rules for the Windows Firewall. This local firewall is enabled by default and has preconfigured rules which allow the use of remote desktop clients and the management of the thin client via the UMS.
Do not remove any of the preconfigured rules! Otherwise, certain network services such as logging on to Active Directory, VNC and management of the thin client via UMS will not work.
Use IGEL setup for configuring Windows firewall settings:
The setup manages the firewall settings (default).
Deactivate Windows Firewall:
The firewall is switched off.
It is recommended that you leave the firewall switched on at all times!
Allow ICMP ping requests:
Allow ping requests to be sent to the thin client.
Do not allow firewall exceptions:
No exceptions for blocked programs can be added.
List of Program Rules:
These rules allow local programs to establish network connections.
You can edit the list of rules using the following icons:
hinzufügen
entfernen
ändern
kopieren
In the editing window for a program rule:
Enable firewall rule:
The rule will be used.
Rule name: A descriptive, recognizable name
Path to executable: The complete path to the executable file beginning with the drive letter and including the file name and extension. %windir% can be used as a placeholder for the Windows directory.
Scope: - Any: The rule applies to any connections. - Local: The rule applies to connections within the local subnet. - Custom. Define the area in Custom Scope.
Custom scope: Enter IP addresses or subnets, e.g.: 192.168.0.12 192.168.1.0/24 2002:9d3b:1a31:4:208:74ff.fe39:6c43 2002:9d3b:1a31:4:208:74ff.fe39:0/112
List of Port Rules:
These rules allow network communication via the ports entered.
In the editing window for a port rule:
Enable firewall rule:
The rule will be used.
Rule name: A descriptive, recognizable name
Port: The number of the local network port used
Protocol: TCP or UDP
Scope: - Any: The rule applies to any connections. - Local: The rule applies to connections within the local subnet. - Custom. Define the area in Custom Scope.
Custom scope: Enter IP addresses or subnets, e.g.: 192.168.0.12 192.168.1.0/24 2002:9d3b:1a31:4:208:74ff.fe39:6c43 2002:9d3b:1a31:4:208:74ff.fe39:0/112