Multiple Issues

[bisonfan]

tracert shows a response under 1ms for all connected network items. 

it tried 192.168.50.85:8867 it responded unable to resolve target system, going to guess that is because of the :8867

A side note, this same setup works with v4.2.5 on port 8866 internally. Externally it turns a bit flaky. That is why I believe it is an issue with V5, whatever the issue is...

Would it have anything to do with local vs domain account?

[bisonfan]

I think I figured out my issue...

per my routers manual "A network makes use of ports in order to exchange data, with each port assigned a port number and a specific task. For example, port 80 is used for HTTP. A specific port can only be used by one application or service at a time. Hence, two PCs attempting to access data through the same port at the same time would fail. For example, you cannot set up Port Forwarding for port 100 for two PCs at the same time."

It appears that my router is blocking my second attempt (KODI is first)…  So the question is can NPVR handle multiple ports in the setup? I attempted to put 8866:8870 in the config file but it didn't seem like it worked... I have a second router I was using as an access point that I am going to try to see if it does not have the same issues as this router... it will most likely be late sunday or Monday before I can switch them around.

[mvallevand]

I don't think you are reading that correctly basically the router can only route 8867 etc to one server on the local lan. If you have a local lan with access points it sounds like you subnetting might be issue. Check the IP of your server, you can look at the IP that NextPVRServer shows it starts up from the command line not as a service.

Martin

[bisonfan]

I don't think you are reading that correctly  basically the router can only route 8867 etc to one server on the local lan.  If you have a local lan with access points it sounds like you subnetting might be issue.  Check the IP of your server, you can look at the IP that NextPVRServer shows it starts up from the command line not as a service.

Martin

Do you have instructions on how to complete  this?

[mvallevand]

You need to make sure all the devices on your local lan are on the same subnet which I am guessing is your problem based on the symptoms. Make sure your access point is not NAT'ing from one subnet to another.

Martin

[bisonfan]

I don't believe the access point is the problem. I logged directly to the main router wifi to by pass any of the access points to eliminate that variable. I installed kodi on my android cellphone, I logged into kodi and setup the pvr, works perfect. Try to connect via web browser to the same access ip address kodi uses and I get an http 404 error. All subnets are the same.

The install service setup comes back with a 1073 error indicating a create service failure.

[mvallevand]

Don't worry about running as a service while you are trying to get this going, just run NPVRServer.exe. You get the bonus of seeing the IP that NextPVR is on plus output of any errors during startup.

Some browsers do require you to use http://ip:host/index.html

Martin

[bisonfan]

when I run install service as administrator, an ip does not show up on the cmd.exe screen.  Is that correct?  or are you talking about somewhere else that I should be able to see the IP address?

[mvallevand]

I am saying when you run NPVRServer.exe from the command line. Again, please don't install the service just let.

Martin

[bisonfan]

When I attempt to execture the Nextpvrservice.exe, I get an error.   Says I can't install the windows service without installutil.exe being installed first then started by command line... If I run the nvpr.exe in the client folder, it states unable to connect to the backend server, attempting to access the settings localhost:8867, the connection is refused...