W7 firewal woes

OTAjunkie · 2013-01-27, 01:23 AM

Hi Brian,
I've been anxiously waiting for your next release since nDroid's premiere.
All works well only if I drop Windows Firewall.
I had the same problem with the first release but I can't remember the fix.
No problem on my router, ports 8790, 8791 are forwarded and I can connect via WiFi or WAN with Win firewall off.
Windows Firewall Exections include NDroid Service
Windows Advanced Firewall has an inbound rule for NDroid Service set to 8790, 8791 for UDT and TCP.

What else can I do?

bgowland · (This post was last modified: 2013-01-27, 02:07 AM by bgowland.)

OTAjunkie Wrote:Hi Brian,
I've been anxiously waiting for your next release since nDroid's premiere.
All works well only if I drop Windows Firewall.
I had the same problem with the first release but I can't remember the fix.
No problem on my router, ports 8790, 8791 are forwarded and I can connect via WiFi or WAN with Win firewall off.
Windows Firewall Exections include NDroid Service
Windows Advanced Firewall has an inbound rule for NDroid Service set to 8790, 8791 for UDT and TCP.

What else can I do?

I'm not sure what to suggest. The current version doesn't use any other ports than the other versions. Whatever is set for the main port (default 8790), it also needs that port+1 and that's it. If you've got those open for incoming connections and "all ports" for nDroidService.exe for outgoing connections then it should work.

EDIT: You don't need to open any ports for UDP (it only uses TCP) but you might need to explicitly specify HTTP as the protocol (I haven't got a W7 machine immediately available and I can't remember how the rules work).