W7 Firewall issue

[OTAjunkie]

I decided to revisit ndroid after jumping on the initial release.

Very happy to see transcode settings and smooth transition to MPlayer but my problem remains the same:

Despite allowing the "ndroid service" through Windows7 Firewall as well as setting "specific ports" in "advanced settings" the ONLY way nDroid works is with Windows firewall "OFF" (for both LAN and WAN).
Brian, you've done great work with this app and I know you are not a "Windows Firewall" expert. I'd love to put this to use but there must be away to correct my configuration so that the firewall can be "ON".
There is a D-Link modem in the mix but I believe it to be set right.
I can be watching a stream, then turn on firewall, and after the appropriate delay the client hangs.
btw:NEWA runs like charm(with firewall ON).
Is there a DNLA setting or rule that I'm missing?
Can anybody help me out?

one other bug:
my designsted "Music" folder(very large) won't load even after waiting hours but if I create a single album folder, that loads (populates).

[bgowland]

Despite allowing the "ndroid service" through Windows7 Firewall as well as setting "specific ports" in "advanced settings" the ONLY way nDroid works is with Windows firewall "OFF" (for both LAN and WAN).
Brian, you've done great work with this app and I know you are not a "Windows Firewall" expert. I'd love to put this to use but there must be away to correct my configuration so that the firewall can be "ON".

Delete the rule for the nDroidService and just make sure you have an inbound rule for ports 8790 & 8791 (or whatever you've set the nDroid Service ports to be) then try again. I assume Windows Firewall has logging ability and if you can find the log then post it here and I'll look further.

EDIT: Don't open 8790 & 8791 as specific outbound ports (if that's what you've done) - that's not how it works. The service "listens" on those ports so they must be opened as inbound. Replies are on random ports - that's how IP comms work.

Is there a DNLA setting or rule that I'm missing?

No. DLNA doesn't apply to nDroid - it's a very dumb beast. All it needs is HTTP traffic from ANY port to 8790 & 8791 and for the nDroid Service to have HTTP response ability from ANY port back to the originating port. If you've opened ports for 8790 & 8791 specifically the nDroid Service logs will show attempted connections even if the service can't respond due to being blocked.

one other bug:
my designsted "Music" folder(very large) won't load even after waiting hours but if I create a single album folder, that loads (populates).

If your music collection isn't on the same machine, e.g., it's on a separate server or NAS box then it won't work without setting up relevant connections etc. Unless every music track is in one folder causing a huge delay in getting the file names, the number of tracks shouldn't matter - it just walks the folder tree like using Windows Explorer. Again, logs would be useful.

Cheers,
Brian