Getting "No Content Found On Server" on PCH with Windows 10 Pro

[baj1]

I still can't get my PCH A110 to access the mvpmc shared folder on Windoze 10 Pro (build 1909).  I'm pulling my hair out on this one.  I have been using my NMTs for 9+ years on my Win7 NextPVR installation, although as I recall I had a battle getting that share to work originally as well.

Notes:
My NMTs can and do work with NextPVR on my dying Windohs 7 Pro PC. 
I have the latest v4.2.5 installed on both the dying Win7 and new Win10 machines.
I do have Kodi v18.6 and knewc add-on working with both the new and old PCs (Win7 and Win10 machines).

I've tried dozens of combinations of settings, I've lost track.

I have tried the procedures in these links:
https://www.howtogeek.com/126214/how-to-...windows-8/
https://answers.microsoft.com/en-us/wind...78f679e428
http://files.syabas.com/popcornhour/down...ssword.pdf

I tried with firewall turned off.  I tried using REGEDIT to create a DWORD value called 'AllowInsecureGuestAuth' in HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters and set this new value to 1.
I've tried the Guest account and with user/password.  40/56 and 128bit encryption.  Media sharing enabled and disabled.  Public network access on and off.

After running up and down the stairs enough times to make a fitness instructor jealous, I finally moved a PCH into my office next to the Win10 box.
Here's the results of NMTcheck on that PCH from the Win10 machine:


Checking for mvpmc share on BIVO-2020
mvpmc        C:\mvpmc                        Automatic caching of programs and documents

Checking GB-PVR.html links
C:\mvpmc                        Automatic caching of programs and documents\GB-PVR.html not found

NMT IP Address: 192.168.0.83  MAC 0006DC429B03

GB-PVR Not Installed

N-PVR Installed C:\Users\Public\NPVR
config.xml entry found Client Type PCH2
MVPClientType PCH2
MVPWidth 1256
MVPHeight 708
MVPOffsetX 24
MVPOffsetY 12
MVPSendIncrementalUpdates true

Enabled true
Port 8866

The remote server returned an error: (404) Not Found.

Checking NMT Version
01-17-110314-15-POP-403-000

Checking NMT Display
720p 60Hz

Calling NMT Source
HPP7-1080T-BIVO:mvpmc
smb://HPP7-1080T-BIVO/mvpmc Username:  Password Length: 0

HPP7-1080T-BIVO:Movies
smb://HPP7-1080T-BIVO/Movies Username:  Password Length: 0

BIVO-2020:mvpmc
smb://BIVO-2020/mvpmc Username:  Password Length: 0

[baj1]

As with my day job, describing an issue to others often helps me come up with ideas to find, I guess thinking about the issue enough to make a good post to a forum has the same effect.

My post above led me to do another search which led me to info on Win10 Server about the somewhat recent disabling of SMB1 (less secure) in favor of SMB2 (more secure) in *all* versions of Win10. Given the PCH is 10+yo tech, I figured out how to enable SMB1 and now it finds the share. I can pick "programs", select N-PVR.html, but then get a new message, "Request cannot be processed" on the PCH.

Any thoughts?

FYI, enabling SMB1:
https://www.tachytelic.net/2019/09/windo...able-smb1/

[mvallevand]

You need SMB1, a guest account, and no passwords on the share. If you are able to play files on the PCH not using mvpmc then you should be able to get mvpmc to connect. If not the the USB boot method will probably work.

Martin

[baj1]

Got it! I had mistakenly copied the /mvpmc folder over from the old Win7 computer and NMTinstall must not over-write all the config files in there. I had to edit N-PVR.html and startmeup to point at the new Win10 box.

But the hours I wasted figuring out MS disabled SMB1. Ugh.

[baj1]

You need SMB1,  a guest account, and no passwords on the share.  If you are able to play files on the PCH not using mvpmc then you should be able to get mvpmc to connect.  If not the the USB boot method will probably work.

Martin

Thanks for the reply Martin.  Yes, if only I knew SMB1 was disabled in recent builds of Windoze 10 products.  I wasted a huge part of my weekend searching, researching, and trying a zillion different things/combinations to get the NMT to see that share.  I can only assume that either existing installations of Win10 did not disable SMB1 on Windows Updates or I'm the dolt in the crowd who didn't know about MS disabling SMB1.

At least it's solved.  Still, what a huge time-suck.

Thanks for your continued support!
-Brad

[mvallevand]

I think this started in 2017 so it is not new.

Martin

[baj1]

Interesting that it's ~3 years old. I couldn't find anything on the internet with regard to the change (disabling of SMB1) and NMT/PCH folder sharing.

[baj1]

Although now that I know SMB1 was the problem, a search does yield results on MS's site. My post here is the only result in this forum though. I guess I'm truly a dinosaur and one of the few still clinging to their PCHs. Okay, actually it's my wife, but it's me by the transitive property of technophobia.

[Graham]

... I'm the dolt in the crowd who didn't know about MS disabling SMB1.

I suspect that there is at least one more dolt ... I went through the exact same bafflement a few months ago ... and also eventually fixed it by re-enabling SMB1 ... But ... I cannot now remember what problem was solved by SMB1 ... I hope that I remember all this if it (whatever "it" is) happens again ... Typing this has stirred up a vague memory about a problem connecting to a share on Windows from Ubuntu ... but that could have been something completely different.

[baj1]

Ha! Thanks for making feel a little better Graham. I'm no expert, but as I understand it there's three revs of the SMB protocol (protocol?), SMB1, SMB2, and SMB3. The NMTs are old and use SMB1. They since identified some security issues with SMB1 and so Microsoft decided it would be disabled by default in Windoze 10. At first I was pissed about this and how much time I spent figuring this out, but I know it's better for Windohs users overall that it's disabled. I just wished I had found the connection between the share not working and SMB1 faster.

Does your computer run an old version of Ubuntu? I'm running Mint (ubuntu-based) on my laptop and was able to connect to the Windohs 10 shares with that even with SMB1 disabled.