no nextpvr servers found on the network

[SteveCos]

You cracked it! - actually you identified a bug ... when I'm at home, home.rata.co.nz resolves to an internal address, so it not Internet, but clearly nlite was assuming it is on the Internet because I have a properly functioning internal DNS server! -server:192.168.80.xxx worked. Did some more testing - adding and using a PIN worked too (I thought I tested that earlier, but must have screwed the test).
Same thing streaming to VNC server.

Where do I report bugs?
I tried to access an internal NextPVR server using a FQDN. NextPVR interpreted this as a request from the Internet. Suggested solution is that NextPVR should resolve the supplied FQDN then determine whether that address is internal.
Example:
From the Internet, home.rata.co.nz resolves to 203.118.151.16. Internally it resolves to 192.168.80.xxx
Running nlite (or equivalent URL streaming to VNC server), -server:192.168.80.xxx works but -server:home.rata.co.nz does not.
Might this be related to the fact that discovery doesn't work on the current version of nlite, but does work on the older 'win-32' version?

[sub]

There isn't really a lot of scope for NLite to be doing any different. Microsoft is taking care of all the name resolution etc. NextPVR never even sees the IP address it resolved to. You'd probably have to report it to Microsoft if it's a real bug. This is the .NET code that is using the name to download some data:

WebClient client = new WebClient();
client.DownloadData("http://home.rata.co.nz:8866/control?key=x");

If you want to post your logs, I can see what IP address is reported for the arriving request.

[mvallevand]

Might this be related to the fact that discovery doesn't work on the current version of nlite, but does work on the older 'win-32' version?

Discovery does work on the current version of nlite dshow version.  I see 4 discovered in my nlite.log.  Discover on the internet doesn't work, which means it is the same problem.

Martin