2022.2

Table Of Contents
l
127.0.0.1: The local computer. Typically this IP should have all the accesses checked.
l
255.255.255.255: Everyone on the same subnet. This is equivalent to hard-coding the cur-
rent subnet, such as 192.168.1.255 or 10.0.0.255.
l
192.168.0.42: A single IP address. This can be any valid address on the same subnet.
l
10.0.255.255: Any IP in the 10.0.X.X range.
Automatically detecting machines on the network and adding them
To detect machines on the network automatically, and give them access to the Messenger service:
1. Make sure the machine you want to detect is turned on and the Messenger service is started.
2. Click on the Refresh button under the list.
3. Add the necessary permissions to the detected machines.
4. Click OK.
5. Restart the Messenger service.
Removing an entry from the list
To remove an entry from the list:
1. Remove all checkmarks from the entry.
2. Click OK.
3. Restart the Messenger service.
Caution: The following considerations are to be understood when using the Access Manager to
configure IP limitations:
l
Each permission type (column) is evaluated from top to bottom (column per column) in the
order in which they are visible in the Access Manager window. This means that wide
ranges should always be at the top to increase performance. For example, if you accept
HTTP connections from any IP, the first entry should be 255.255.255.255 with the Allow
checkmark in the HTTP Input box. PlanetPress does not continue processing after it has
found an "Allow" checkmark. There is no concept of "Deny", meaning if any "Allow" per-
mission is given, there is no way to later remove it for certain IP addresses or IP ranges.
l
The configuration of the Access Manager is saved in a file on the hard drive which can be
edited manually. See "Access Manager hosts.allow File" on page707.
Page 704