VncViewer - Inbound Policy Violation (Access Denied ...)

I am using Comodo Firewall Pro. Version: 2.4.18.184

I am running VncViewer and it is listening on port 5500.

When I “Adjust Security Level” to “Allow All”, then VncViewer gets the inbound connection and I can control the remote PC.

When I “Adjust Security Level” to “Custom”, then VncViewer does not get ANY inbound connections.

So I created an Application Control Rule:
Application “C:\Program Files.…\VncViewer.exe”
Parent C:\WINDOWS\explorer.exe
Selected “Allow all activities for this application”

Now in the Application Control Rules list, it shows:
Application VncViewer.exe
Destination RANGE : 0.0.0.0 - 255.255.255.255
Port 0 - 65535
Protocol TCP/UDP In/Out
Permission Allow

So I thought this rule looks broad enough, and yet:
When I “Adjust Security Level” to “Custom”, then VncViewer does not get ANY inbound connections.
When I “Adjust Security Level” to “Allow All”, then VncViewer gets the inbound connection and I can control the remote PC.

The Activity Logs show:
Medium | Network Monitor | Inbound Policy Violation (Access Denied, IP = a.b.c.d, Port = 5500) | …

Where a.b.c.d is the ip address of the remote PC.

What am I doing wrong?

How can I do this in Comodo?

I need VncViewer to:
a. Receive inbound connections on port 5500
b. From the outside world AND
c. From my LAN (192.168.n.n)

So that I can control the remote PC, regardless of it location.

Hallo,

The log is pointing that out…
Medium | risk score
Network Monitor | what component of the firewall is taking action
Inbound Policy Violation (Access Denied, IP = a.b.c.d, Port = 5500) | details

You need to create a Network rule to allow inbound tcp connection on destination port 5500.
Please remember that network rules are parsed from top to bottom in the network montor list so a specific allow rule should be put before a more generic bloc rule.

Look at my signature, there is a link to a tutorial list. It is a good starting point.