Windows XP's firewall
The same concepts are embodied in any packet filter firewall, regardless of its implementation or interface. Imagine there were a version of server4 for Windows. Windows XP has a built-in firewall that prohibits contact from other computers to server programs running on it, but you could make exceptions. Here is how you would do it:
Start -> Control Panel -> Network Connections
Right-click on the entry for your machine's NIC card, click Properties on the
menu
Click the Advanced tab
Under Windows Firewall press the Settings button
Click the General tab
Click the Exceptions tab
Click the Add Port button
Enter "server4" for Name
Enter 2345 for Port number
Press OK
Examine the list and note the presence of server4 as an exception
Select server4 in the list
Press the Delete button

(in above graphic read "server4" for "server3" in the "Add a Port" dialog)
With the exception you made, other machines would be able now to contact your hypothetical Windows version of server4. What this Windows firewall exception setting did was equivalent in essential logic to what iptables would do as:
iptables -A INPUT -i eth0 -p tcp --sport 1024:65535 --dport 2345 -s <any> -d <Windows' IP> -j ACCEPT
Though that syntax plays no role in Windows (checkboxes and buttons take its place), the result in both environments is the same type of memory data structure representing the same logic against which to dynamically test incoming packets.