It is not even for internal network. When you allow act as a server for an application, without an explicit network control rule, that application can only accept loopback connections i.e from the same PC it is running.
I see. Now I understand my computer a little better. Oh yes, I would like to contribute a program that is included in the safelist for outward bound connections. The program name is DKService.exe and it belongs to Diskeeper. It tries to create a loopback connection for itself once Diskeeper is installed.
Am I correct in my thinking that the “Act as a server” message simply means that an application is going to act as a server in the traditional sense - accept input from another application or provide services to another application?
Thanks for the response egeman. The Network Monitor is set by default to block everything coming in. So you are saying that only interactions initiated by my pc will allow a response back with that setting.
I think the term server is very misleading in the dialog that appears. Server means something quite different to most people than what is intended. On the applicaton monitor In/Out are used which is even more confusing, not Server/Out. If one dialog appears asking “xxxx is trying to connect to the internet”, the second one should not refer to server, it should ask “do you want to allow communication back to xxxx”. Hopefully that is addressed in upcoming revs.
I ignored the Network Monitor section because I assumed it referred to local networks, which I don’t have enabled.
With new users in mind, wouldn’t it make it easier to display an “allow/deny incoming connection” or “allow/deny outgoing connection” dialog prompt. If you look at how SKPF4 handles network security, I think they’ve hit it spot on. Plus having a simple mode and advanced mode caters for both new and advanced users. Just my thoughts.