NPVR client not connecting/communidating with NPVR server

[snaitaz]

G'day..the NPVR server box is installed on "bar-room" machine with an IP of 192.168.10.38. NPVR is working like a champ on this machine as I can watch live TV or streams and record as well. The "act as client PC" is not checked. On my second machine I also installed NPVR and ticked the "act as client PC" so I could communicate with the NPVR server. The client is set with server name=
bar-room and database share=\\bar-room\users\public\NPVR. As a check for connectivity, on the client using Explorer and using \\bar-room\users\Public\NPVR I can get to the database. Also using \\bar-room\c\users\Public\NPVR gets me there as well.

Launching the client gets me this
[ATTACHMENT NOT FOUND]
However, clicking on TV Guide gets me this
[ATTACHMENT NOT FOUND]

But when I try to watch something I get the ...please wait... screen forever. So I am at a loss Any suggestions? TIA Cheers!

[snaitaz]

Here is the log from the client in case that will help.

[sub]

That tells use the share is working, but it can't get to the communication port. It'll be a firewall on server (or client) blocking request.

[snaitaz]

Will check that out thx

[snaitaz]

G'day...so this is what I have done thus far. This pic in Windows Defender shows that there are incoming ports open with no restrictions on the server. The second pic is the extension of the first pic. There are no outgoing connections set up on the server for NPVR.
[ATTACHMENT NOT FOUND][ATTACHMENT NOT FOUND]

On the client side these are the incoming setups. The client does have an outgoing rule set because I set that up thinking this may be the cause. There are no restrictions on any of these.
[ATTACHMENT NOT FOUND]
[ATTACHMENT NOT FOUND]
[ATTACHMENT NOT FOUND]

So then I shutdown the firewall on both the server and client and wholla the client was able to connect. Shutting down the public portion on the firewall of the client had no effect, it still connected. However, shutting down the private portion on the client did have an effect and I was not able to connect to the server. I turned of the firewall again on the client and connections was established. Turning on the private portion on the server killed the connection and turning on the public portion only on the server had no effect. So my conclusion is that yes, this is definitely a firewall issue blocking the connection from the client to the server.

Unfortunately, now how do I proceed since NPVR.exe has an open path to the server from the client yet it is not able to establish a connection. Am I missing something here? Thanks in advance.

[sub]

The other possibility is the "server name" is not able to be resolved. (The share name is a NetBIOS name, not IP hostname, so even though the share name is working, it doesn't mean the IP hostname is able to be resolved)

So, maybe try replacing "bar-room" with the IP address of that machine.

[snaitaz]

I actually tried that method earlier but failed to report that sorry. I just tried it again and no joy. This time I got a MS .Net Framework error saying...Unhandled exception has occurred in a component in your application. If you click continue the application will ignore this error and attempt to continue. A connection attempt failed because the connected party did not properly respond after a period of time or established connection failed because connected host has failed to respond 192.168.10.38:8968.

I used the IP address in the error to set up port 8968 but realized that it was already there on the server side. Gonna try some more troubleshooting. I feel we are close but must be something very simple I overlooked. On another note, would using NEWA bypass all of this and get connected? Thanks...Cheers!

[snaitaz]

G'day mates!!! I believe the issue is finally solved. I was banging my head trying to get this resolved so I went through many many many have I said many, pages of this forum trying to get a resolution. So back on 8/25/2015 (yup 2015!) I found this by jcharlesmith

https://forums.nextpvr.com/attachment.ph...1440472038
Here's what I just did.

I stopped the NPVR service and then restarted it. I then opened NextPVR and I can view Live TV and see the EPG. I opened KODI and NPVR connection lost shows again. To enable the web server I am running "C:\Program Files (x86)\NPVR\NPVRServiceControl.exe" start

Next I checked Windows Firewall and observed that NextPVR and NRecord are allowed through the firewall. I checked my AVG AntiVirius and there is no AVG Firewall enabled.



Name: firewall.jpg Views: 3949 Size: 20.1 KB
I browsed to http://127.0.0.1:8866/ and the browser says that the webpage is not available. So I disabled Windows Firewall and tried again. Still won't load.

I noticed in his pic that both NextPVR and Nrecord were being allowed. I went to my server and check in that setup but NRecord was missing so I put that in enabled the firewall on the server and went to the client PC. Fist I used a browser with URL of 192.168.10.38:8866 and boom it came up. So I launched NPVR from the client with the firewall on and no joy. So I looked at the firewall exceptions and found the incoming was okay but out going was missing the NRecord exception so I put that in and bam I was connected. Then I restarted both machines and made sure the firewall was up on both. I was ablt to connect to the server by using the browser and NPVR.exe. So its now time for a couple of tequila shot some martinis and get back to the next project of incorporating NEWA but I think I will just sit and use what I have for a bit. Thanks to all who helped and especially Mr Smith from 2015!!!

[snaitaz]

I forgot to mention that in the firewall settings, there were a few Nextpvr and Nrecord with a profile of Domain so I deleted those as well. This morning everything is working well except it that the client takes a while to connect and it still gives me that notice screen on startup that it cannot communicate with the server as indicated in post #1

[johnsonx42]

...the client takes a while to connect and it still gives me that notice screen on startup that it cannot communicate with the server as indicated in post #1

That's normal if IPv6 is enabled. I think Windows tries to use IPv6 first, and something doesn't work, then it falls back to IPv4. The client launches much faster and without the error if IPv6 is disabled.