Help with Client setup

[troutseth]

Hello all, I need a bit of help.

I have had NPVR running on my HTPC for several months. Everything works out great; set up was simple and maintenance has been low. Recently, I added a second machine to act as a client in another part of the house. The documentation on the wiki is limited, but the setup seemed fairly simple. However, I cannot get the client to see/find the shared database file. I have confirmed the client machine can see and browse to the share location of the DB through windows explorer. Neither the use of the server machine name nor the IP address in "Server name" nor in the file path seem to work. Am I missing a setting somewhere else on the client machine? Possible on the server side? Both machines are up to date Win. 10 machines in the same Homegroup.

\\IP ADDRESS\Users\Public\NPVR
\\Machine Name\Users\Public\NPVR

[ACTCMS]

Try setting an explicit share on your server's \Users\Pubic\NPVR folder and using

\\MachineName\NPVRShareName or
\\IPAddress\NPVRShareName

Alex

[troutseth]

Thank you for the reply! I think I stated above, I have tried both and neither are working. I continually get "unable to connect to server database"

Try setting an explicit share on your server's \Users\Pubic\NPVR folder and using

\\MachineName\NPVRShareName or
\\IPAddress\NPVRShareName

Alex

[ACTCMS]

Thank you for the reply! I think I stated above, I have tried both and neither are working. I continually get "unable to connect to server database"

On your server, define a share on the NPVR folder itself and use that rather than referring to the folder structure based on the main Public share.

Alex

[Graham]

Thank you for the reply! I think I stated above, I have tried both and neither are working. I continually get "unable to connect to server database"

Alex is suggesting that you create a share that points to the NextPVR Data folder directly so that the client points to \\Server\Share and not \\Server\Share\Folder\Subfolder.

[troutseth]

Ahh got it, and that did not resolve the issue.

HOWEVER, I did resolve the issue and it is an odd one. So, I had the text size set at 175% on the windows display. It caused some issues rendering the control panel so I moved it down to 150% and the control panel magically begin to come back. I had a thought. Tested the client set up - still did not work although the share was accessible. Changed the view to 100%; and it started working. And it has been working without issue since.

Windows 10 is driving me insane, but it appears when they give you the warning that not all applications can handle increased font size through the system parameter, they mean almost nothing can handle it including their own stuff.

Thanks for the help guys!!!