Looking for help with a Windows Firewal problem

[OTAjunkie]

This thread concearns nDroid and Windows Firewall but I have a thread in on this problem in nDroid but very little response
I'm hoping that posting here may get more attention and someone can help me with this.

NEWA works as it should and can pass my firewall to LAN and WAN.
But I'm trying out nDroid and it only works to my LAN or WAN if Windows Firewall is "off".

"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 LAN or WAN with Win firewall off.
Windows Firewall Exceptions include NDroid Service
Windows Advanced Firewall has an inbound rule for NDroid Service set to 8790, 8791 for UDT and TCP."

This is not a streaming issue, I simply can't connect unless WF is off.

Any Ideas?

[Graham]

Does this help ...

http://forums.nextpvr.com/showthread.php...-firewalls

[mvallevand]

nDroid is its own service .exe etc so this really should be moved back to the nDroid sub-forum. It uses NextPVR for streaming playback and I think it does connects to the Recording service but that is not impacting remote connections.

Martin

[bgowland]

Agreed with Martin, you probably should have just bumped your thread in the nDroid forum or posted in General discussion as this isn't related to npvr support.

As I said in my response to your post in the nDroid forum, you need to specify an outbound rule for the nDroid Service on all ports. The protocols involved are TCP and HTTP (not UDP) and the reasoning behind allowing "all ports" outbound on any TCP service is that the port used by a TCP service to make an outbound connection isn't the same as the one as the incoming connection.

Basically, it's possible to have multiple clients connect in to a single port but the service then uses unique ports to respond back. The chances are you're connecting inbound without a problem, it's just the nDroid Service isn't allowed to reply because the firewall is blocking its outbound responses.