vistafirewallcontrol.freeforums.org

[nilstk]

Hello,

I recently bought the Pro version as it was not possible with the free version to get my UPnP application to work.
Unfortunately it's also not possible with the Pro version - at least I don't know how.

The application is waiting on Port 1900 UDP ... but it's always blocked and this ballon said it always after I searched for UPnP devices (the application is a UPnP example program to simulate these devices).
How can I allow incoming traffic for this java application ? The zone is set to EnableAll !!! ... well ... looks like enableAll is not working ... or is Java using some other application for incoming traffic ?

Thanks for help.

regards, nils

[VistaFirewallControl]

> The application is waiting on Port 1900 UDP ... but it's always blocked and this ballon said it

The balloon shows all the blocked notifications regardless of the origin. The balloon shows the events from WindowsFirewall (for instance) as well.
The balloon text (and the log file) specifies the blocked application/reason usually precisely.
The text could clarify the problem in full.

>How can I allow incoming traffic for this java application?

As java applications are actually executed by Java Runtime (java applications are not native executables anyway), W7FC will list JavaRuntime only. You should just set a correct permission for the Runtime.

>The zone is set to EnableAll !!! ... well ... looks like enableAll is not working ... or is Java using some other application for incoming traffic ?

You could try to temporarily set TrayIcon/RightClick/Mode:EnableAll to switch the firewall entirely off. If the problem still exists W7FC is not involved at all. Otherwise the problem is the incorrect settings.

If we might consider the situation typical, the problem is WindowsFirewall blocks the application, W7FC shows the balloon mistakenly treated as “blocked by W7FC”

[nilstk]

Well, it looks like a bug in your firewall.

As long as the firewall is running it's not working. If I uninstall it, it's working.
I added the screenshot ... there is NO user interaction as mentioned in the balloon ... the incoming traffic is just blocked ...

any idea? Thank you !

[VistaFirewallControl]

W7FC shows all the blocking events regardless of the origin
“Prompt the user….” is the rule from WindowsFirewall. (actually WindowsFilteringPlatform (WFP) WindowsFirewall is based on). Anyway the rule is not set by W7FC, W7FC names the rules differently.

We have no idea why the rule exists (is triggered) when W7FC runs only; WFP internals are not documented. Anyway the rule is not of W7FC. Please check WindowsFirewall (probably with extended security) settings and check whether the incoming traffic is enabled in general.

[tebitan]

Hi,

I have a similar problem.

My multifunctional printer / scanner is on the network. Even if I EnableAll the MFC scan app, it need UDP Incoming, and VFC blocks it.

At the moment the only way to make it work is to disable firewall by righclick according to method above, then it works.

Any ideas how to make it work with firewall active?

[VistaFirewallControl]

The blocked.log and/or the blocking notifications specify the blocking reason (i.e app/zone caused the block) precisely.

As uPnP (UDP:1900?) in typical circumstances is processed in the name of System (meta) application and/or “host services…” application (not the MFC scan app only), most probably you have to give more permissions to the applications.
Anyway the log would be helpful.

[tebitan]

I think relevant would be the 2 items:
26.05.2010|13:31:10|IPv4 UDP 192.168.1.151:6000(59404)|C:\windows\twain_32\samsung\clx3170\scan2pc.exe|Detection Outgoing
26.05.2010|13:31:40|IPv4 UDP 192.168.1.151:9401(59403)|ScanToPc MFC Application| Incoming

I hope I already wrote that scan2pc.exe is set to EnableAll.

[VistaFirewallControl]

>26.05.2010|13:31:10|IPv4 UDP 192.168.1.151:6000(59404)|C:\windows\twain_32\samsung\clx3170\scan2pc.exe|Detection Outgoing

Confirms the application has been detected. The initial access attempt has been blocked on the detection.
Most probably you have set EnableAll to the application at this point.
Note:
As the initial access has been blocked the application has to retry to re-connect.
Usually (not always) applications do the re-try automatically, sometimes have to be forced manually (or restarted)


>26.05.2010|13:31:40|IPv4 UDP 192.168.1.151:9401(59403)|ScanToPc MFC Application| Incoming

Looks like the application was blocked by a third party (WindowsFirewall for instance).
W7FC specifies the blocking zone exactly, So if the app is blocked by W7FC the log entry would look as “|ScanToPc MFC Application| a-zone-set-to-application Incoming”.
There is another reason to check/configure WindowsFirewall (WF). WF usually blocks almost any incoming by default. Is WF enabled? Is there a scan2PC related entry in WF?

[tebitan]

WF was active, maybe this is why.

Anyway, now it works.

Thanks for Your support.