Wits end

[jd1940]

I've been using NPVR for several years with generally good results. However, after updating both my server and client to Win 10, I've had nothing but problems. I've read through several posts about these but haven't seen any solutions. Everything worked fairly well for four days, although I've never been able to get NPVR to load as it used to after a reboot and I've had multiple occasions with the recording stopping for no apparent reason. But tonight, after a reboot of my client, I can no longer connect with the server, getting "can't connect with db3" message. I went through this once before with Win 7 and finally got it to connect by using the ip address, but that's not working this time. My server name is Jim-pc so I've tried both that and the ip address with no luck. This is my client database share entry: \\192.168.1.4\C:\Users\Public\NPVR\. It's hard for me to think this is a network problem since I can use the client File Explorer to connect to the recorded and downloaded files on the server and have no problem watching them that way. The weather and internet radio add ons work but they obviously don't need the npvr.db3.

My son keeps trying to get me to move to Kodi and I'm beginning to wonder if I should try that, although I think you have to use NPVR for recording TV so I might have the same problem. I'm open to any suggestions as this is taking way more time than it should.

[Graham]

This is my client database share entry: \\192.168.1.4\C:\Users\Public\NPVR\.

The database share entry should not have the "C;\" in it ... so "\\jim-pc\users\public\npvr ..." should do it ... but you might also need to check that Windows 10 settings are correct ... Control Panel ---> Network and Internet --> Network and Sharing Center --> Advanced sharing settings in "All Networks" you might need "Public Folder Sharing" enabled and you might need to enable "Turn off password protected sharing".

[jd1940]

Thanks. That got me 90% there. I'm still getting the "can't connect to server" when I first start NPVR, but once that goes away, NPVR seems to work fine, although it takes longer to start a recorded program than it used to. I already had all those settings in Windows. Should the database share entry in the server be exactly the same as the client?

[Graham]

Should the database share entry in the server be exactly the same as the client?

On the server ... the "Act as Client" should not be ticked. The values in "server name" and "database share" will be ignored on the server.

[donschjr]

The "can't connect to server" started a couple versions ago and I just ignore it. There was a thread about it some time ago but nothing ever came of it but there was multiple people experiencing this issue.

[johnsonx42]

after upgrading my own system to windows 10, I found windows had screwed with the permissions in the \users\public\npvr folder. I now can't open the .db3 from my client, and until I went and reset the permissions, I couldn't access about half of the folders under the npvr folders (including Logs which I access pretty routinely). This surely has to do with the migration process, where it constructs a new \users\ folder structure and then migrates the files and folders from the old \users\ structure.

[jd1940]

After using it today it seems to me the "can't connect to server" problem seems to be caused by a delay in the client findng the server. That same delay occurs when I first start a recorded program after restarting NPVR. Once the first program has started, however, all subsequent programs open promptly. I don't know what's causing the delay.

[HarryH3]

Why do you have the entire folder tree listed here?

>> This is my client database share entry: \\192.168.1.4\C:\Users\Public\NPVR\

Mine is just listed as \\192.168.1.4\ShareName, where ShareName is the actual share-name of the shared NPVR folder on the server.

[jd1940]

Because that's what I was told to do. I'll give yours a try and see how it works.

[JEF]

\\192.168.1.4\C:\Users\Public\NPVR\ ---- on my client there is no Colon after the C

I had the same "can't connect to server" problem since upgrading to windows 10.
I cured it by changing the server name in settings to the i.p. address of the server
i.e. in my case the server name was PVR-PC it is now 192.168.0.2
if I change it back to PVR-PC the problem returns.