Could not open NextPVR on 192.168.1.X

[jcjefferies]

Martin

Because of problems with Windows 8 on my NextPVR server I setup a temporary server while I did a clean install on the original server. This new server worked with X-NEWA clients almost immediately but for some unknown reason the X-NEWA clients wont work with either the new Vista or Windows 8.1 install disks in the original server. The original boot disk which was working ok last week now has the same problem.

If the server is sleeping WOL wakes it then the "Could not open NextPVR..." message is displayed. If the server is already up when the client starts the message appears immediately X-NEWA starts.

Using it with or without password protected sharing makes no difference. I assume that its npvr.db3 which is being accesses but the KODI file manager seems to have full Read and Write access to the NPVR directory on the new installs. On the working server "Everyone" has Read/Execute permissions on the database but on the other server installs "Everyone" has Full access.

Clutching at straws now but the only common factor with the three NextPVR install disks with this problem is that they have all been in my HP server which had a BIOS upgrade yesterday to cure a network interface problem which prevented upgrade from Windows 8 to 8.1 and no network connection in Windows 8.1 and 10!!!

Any suggestions Martin what else I can try?

Chris

[mvallevand]

@Chris sorry I missed the post, are you still having this problem?

Martin

[jcjefferies]

Yes and No!! The solution was to give up and go back to Windows 8! I also installed a Windows client and with Windows 8.1 on the server the Windows client gives a popup which says it cannot find the server but behind the recordings and menu populate. I know several people use the same HP Microserver so posted on the Hardware thread to see if any of them had similar problems after trying many more things. It has known problems with the network card running Windows 8.1 but a BIOS upgrade is supposed to cure the problem.

Chris

.

[mvallevand]

Yes and No!! The solution was to give up and go back to Windows 8! I also installed a Windows client and with Windows 8.1 on the server the Windows client gives a popup which says it cannot find the server but behind the recordings and menu populate. I know several people use the same HP Microserver so posted on the Hardware thread to see if any of them had similar problems after trying many more things. It has known problems with the network card running Windows 8.1 but a BIOS upgrade is supposed to cure the problem.

Chris

.

Thanks for getting back to me. There have been posts on Win 10 on having to make firewall and configuration changes based on what constitutes a private and public network. Potentially your problem was related to this.

Martin

[jcjefferies]

Thanks. I mentioned in the post on this subject in the "Hardware" area of this forum that the Windows 10 install on the server none of the shares were visible even when viewed from the server itself! I still have the Windows 10 disk so will investigate the firewall. However I do remember that one of the numerous Windows 8.1/10 installs I did to try solve the problem did default to Public network and took some time to get it back to Private.

Chris

[jcjefferies]

Martin

I plugged in the Windows 10 clean install disk again and as before the server is not visible on the network even from the server itself. I checked all the sharing settings which work with Windows 8. I then ran the Incoming Connections network troubleshooter and as it has several times with Windows 8.1 finds a 1 or more protocols are missing and "fixes" the problem but with Windows 8.1 nothing changed. However with Windows 10 server becomes visible on the network and X-NEWA client can now see the server and runs correctly. However re running the troubleshooter still reports a missing protocol!!

I upgraded a copy of current activated Windows 8 NPVR server to 8.1 to 10 and Windows 10 now behaves like Windows 8.1 does so the X-NEWA recognises the server is up so doesn't run WOL but immediately gives the error "Could not open NextPVR on.....". Could it be a problem Firewall setting in 8.1 being copied to Windows 10. The exceptions for NRecord, NextPVR & NDigitalHost are there but I assume X-NEWA connects via HTTP.

Having gone through the painful upgrade process to get Windows 10 activated on the HP server my clean install of Windows 10 disk which works with X-NEWA has now become activated! So although NextPVR on Windows 8.1 doesn't work correctly with this server I do have an upgrade option for the future but for now will stay with Windows 8!

Chris

[mvallevand]

I assume X-NEWA connects via HTTP.

Correct to both NEWA and sub's servers. If it fails on local host I will speculate that the NEWA web server isn't starting either and you need to follow JavaWiz's post to get .NET web stuff working correctly.

Martin

[jcjefferies]

I dug out my Windows 8.1 NextPVR server disk which X-NEWA does not like and is an upgrade of my current Windows 8 disk. In the logs the web server starts but on a remote PC it does not respond. However if I try to access NEWA from the server itself I get the "Temporary ASP.NET Files" access error message. Google finds lots of same error reports and there is a file to run to sort out the access problem but just creating the directory as JavaWiz did cures the problem!

It now looks as if most of the problems I was blaming on the HP BIOS upgrade may have been unrelated and were Windows problems happening at the same time!! It would have helped if I had remembered much earlier that X-NEWA used http and checked if NEWA was accessible from a web browser!!

Thanks for your help Martin

Chris