Well, I have one working in that config, from that kind of device. A few items:
Run the console (not web, but local console from the start menu). Send a local test message (you did not say if you had tried this) by going to files->setup, go to a rule and you should see a "test" button at the bottom of the window... just click it).. That can tell you a lot. This will work even if the firewall is not properly configured.
Also, from debug tab (not in setup, but in the console) Stop and restart the service. Then go to "view->logs". It will tell you if KIWI is really binding to the network port. Well, if there is no error message, it should be binding.
I had one problem with Win2008R2 64bit VM and KIWI: It had set my network type to "public" (see the windows network and sharing center in control panel, and in the middle it says what kind of network it thinks it is (home, work, or public, usually). This defines how the firewall treats the traffic to the application. I found if it was set to public, I had a heck of a time getting the firewall to pass the traffic. If the settings are right, you can click the "public" word (it is a link) and set it to Home.
Alternately (or probably in combination), go into the administrative tools-> firewall and turn off ALL 3 inbound rule sets and see if that helps. Note that wireshark is using its own firewall rules. I have had an issue that even though I set a rule allowing Kiwi/514 traffic in under all 3 network types, I still had to disable the firewall to see anything. I believe I was able to get the rules to work for private (home) networks at least.
I do know it can work: I have it running... Good luck!
-Mike