Server IP showing in client…

[Colincam]

I have been trying to figure this out for a long time.  Server is Windows 10.  Clients are iOS and/or Android.  The server stops advertising its existence after a while.  A few hours after service start.  Server IP has to be entered manually.  If I restart the Windows service, its existence shows back up on the clients for a few hours and then disappears again.  I have gone to great lengths to make sure the server PC does not go to sleep in any fashion. Does anyone know why this might happen?

[mvallevand]

Perhaps your server is not using a true fixed IP and DHCP is not configured properly and check the network logs for duplicate IP messages. Also if you use a VPN or firewall make sure they are configured to allow TCP 8866 and UDP 16891

Otherwise, I don't know how sub's app use manual IP's but discovery shouldn't be impacting a manual setup. For discovery other things to consider would be if you have v4 installed on the same machine.

Maybe try uidroid and see if has the same problem on Android.

Next time it happens send the zipped logs.

Martin

[Colincam]

Static IP. Not in DHCP range. No VPN. Windows firewall is disabled. I completely reinstalled Windows at one point to no avail. Using external public IP for access works. Port 8866 is open. I will gather logs next time it occurs. What could block the NextPVR service form advertising itself locally until the service is restarted?

[mvallevand]

NextPVR is not advertising it is responding to requests from the client. A co-resident v4 server could cause this issue. I asked for you to check uidroid, to confirm there is not issue in the manual setup or client networking too.

Martin

[sub]

The logs should show a "Received broadcast from" message any time a client has down a broadcast looking for a server.

[Colincam]

The logs should show a "Received broadcast from" message any time a client has down a broadcast looking for a server.

Thank you for the information and clues above.  I don't want to go through the arduous process of side loading uidroid again, having dismissed it previously finding it wonky.

Since I've learned that NextPVR is simply responding to a UDP query; the problem must be with the client device (iPhone) or the networking between.  However, a mystery remains.  I have two NextPVR servers.  Both are running the latest version and no... there is no v4 lurking at all.  All fresh.  One of the servers responds to the UDP request just fine to show its existence.  The other server on the same network, same switch even, stops responding to the UDP search after a while and restarting the NextPVR service on that server fixes it for a time.  After a while it again stops showing up on the iOS client automatically.  I am quite schooled in networking and Windows OS's so I only relate my issue here due its mysterious behavior and in hopes of getting to the bottom of it.  The mystery is that restarting the NextPVR service fixes the problem for a time.  Why is that?  I'm assuming something on the Windows PC server is causing the issue.  The PC is dedicated to serving NextPVR and I have uninstalled many unneeded services and software from it.  I've also updated the network driver (Intel NIC.)  As is often the case with Windows, it's more an art than a science.

[sub]

We could go through lots of steps to try working out what's happening, but why not just manually add the server in the NextPVR iOS app, and then not have to worry about it again? This server will be remembered, and always in your server list.