Accessing </root>

[Grumpy_Geoff]

You're running old firmware. That old firmware doesn't have the "include" instructions to drag in "user" SMB config files.
Since you're on that old firmware, just add your '[Movie]' share specifications directly to the standard smb.conf file.

Better still, upgrade to 20191106 - https://beyonwiz.com.au/downloads/
The 'Movie' share is already included with that.
Because you're running that 16.1-series firmware, you'd need to perform the set up from scratch. I have a method available to copy off your timers and AutoTimer definitions prior to upgrade, and restore afterwards if you wish to do that.

[MrQuade]

Yikes, you're right. I forgot about all that extra user remapping faff that was added in the 17.5 series!

[Grumpy_Geoff]

I forgot about all that extra user remapping faff that was added in the 17.5 series!

faff = root file system protection! Weren't you paying attention in class?

[Paul_oz53]

You're running old firmware. That old firmware doesn't have the "include" instructions to drag in "user" SMB config files.
Since you're on that old firmware, just add your '[Movie]' share specifications directly to the standard smb.conf file.

Better still, upgrade to 20191106 - https://beyonwiz.com.au/downloads/
The 'Movie' share is already included with that.
Because you're running that 16.1-series firmware, you'd need to perform the set up from scratch. I have a method available to copy off your timers and AutoTimer definitions prior to upgrade, and restore afterwards if you wish to do that.

I'd have suggested the beta since it is very stable but, regardless, with the old SMB config files jplouis is likely to run into the 2 GB oplocks problem that plagued me in earlier versions.

As we know, the 19.3 firmware has settings that manage that issue.

[jplouis]

I installed the latest firmware on the T4 - Thanks for pointing me to this Grumpy. I could now the access the mount point Movies from my old DP2 & my wife's laptop - but sadly, still not my desktop.

It turns out this that this Samba mounting problem appears on some Windows 10 machines, but not others - Windows ...... SIGH.

The solution is simply to specifically include the login credentials for the T4 [or any other Samba mount giving you problems, NAS etc] into the Windows Credential Manager.

Problem solved - I can now access the T4 Samba mount from my desktop.

Posted in case this this can help any other poor souls lost in the mysteries of windows networking - The network error from windows, that I had posted earlier, really gives you no indication that this is a simple credentials issue.

[raymondjpg]

Posted in case this this can help any other poor souls lost in the mysteries of windows networking - The network error from windows, that I had posted earlier, really gives you no indication that this is a simple credentials issue.

The error code 0x80070035 that you reported previously appeared to have cropped up about the time Windows 10 feature update 1803 appeared, and one proposed solution was to add the problematic network resource to the hosts file. It also appeared that the issue had been resolved with subsequent Windows 10 feature updates. Are you running a Windows 10 build earlier than 1909 or 1903?

[MrQuade]

one proposed solution was to add the problematic network resource to the hosts file.

eww. The problem solving equivalent of "giving up" IMHO.

[raymondjpg]

eww. The problem solving equivalent of "giving up" IMHO.

There were plenty of bandaid solutions to the networking mess visited on some peoples' pcs following feature update 1803. At that time I was probably transitioning to Windows 10 from Windows 7, and my "giving up" solution was to reinstall Windows 10 from scratch. Things were better with update 1809, and since then I have been pleasantly surprised at the stability of Windows 10 and even networking, apart from the need to periodically restart the Function Discovery Resource Publication Service. My point is at that time of instability with 1803 there weren't that many non "giving up" solutions, at least none that would work for everyone!

[MrQuade]

"giving up"

Hehe, I was definitely not intending that to be a slight on you at all. Just my disgust on the depths we sometimes have to plumb to work around all the new surprise nuggets Microsoft leave us with .

[raymondjpg]

"giving up"

Hehe, I was definitely not intending that to be a slight on you at all. Just my disgust on the depths we sometimes have to plumb to work around all the new surprise nuggets Microsoft leave us with .

OK thanks. But as I said, I have been much surprised at how far Windows 10 has come over the past year. Not one bugcheck bluescreen have I seen, and I find networking and network discovery to be working much as expected now with Samba 1 disabled.

(Whisper whisper I still preferred Windows 7. Call me a Luddite if you will.)

[Paul_oz53]

...

The solution is simply to specifically include the login credentials for the T4 [or any other Samba mount giving you problems, NAS etc] into the Windows Credential Manager.

Problem solved - I can now access the T4 Samba mount from my desktop.

Posted in case this this can help any other poor souls lost in the mysteries of windows networking - The network error from windows, that I had posted earlier, really gives you no indication that this is a simple credentials issue.

By trial and error I stumbled on the need to provide credentials in Win10.

One of my Win10 machines works fine but the other is a basket case after an update. It stopped recognising the SSD and borked on trying a system restore. Took it back to Win7 until I get well enough to revisit the problem.

[jplouis]

raymondjpg

The windows build I'm using is

Windows 10 (x64) (build 18362)

netless

[raymondjpg]

raymondjpg

The windows build I'm using is

Windows 10 (x64) (build 18362)

netless

That looks like Win10 1903. I'd be applying feature update 1909; it is a minor update to 1903 purportedly turning on some features already incorporated in1903. I haven't seen any reports of major disasters either with 1903 or 1909, but caveat emptor.

[Sandy B]

After re-flashing due to my recent problems with my T4 (see T4 wants to reboot), I have noticed that I am not able to access root as noted on the above discussion. I consequently tried to reinstall the <smb_user.conf> file to “internal Flash” > “etc” > “samba”, the first time it noted that the file existed and asked if I wanted to replace it, to which I said yes. After a GUI restart I noted that I still could not access root a power off restart also did not solve the problem I have now tried a few time to again re-copy the <smb_user.conf> and noted on subsequent attempts that it did not ask if I wanted to replace the and it just copied the file, I believe that the file was coped as I highlighted/tagged the <smb_user.conf> with media prior to copying and the tag quickly disappears after pressing the yellow copy buttom. Again after GUI restart and a power off restart I am running out of ideas.

[prl]

So, in some unspecified version of the Beyonwiz firmware, a samba config file with unstated contents that once worked in a possibly different unspecified version of the firmware didn't work when copied onto the Beyonwiz?

First possible problem: The filename you should use (at least in firmware 20210119) is smb-user.conf, not smb_user.conf.

The directory you wrote it to, though, is correct: “Internal Flash” > “etc” > “samba”.

Why do you want to give Windows share access to the PVR's root directory?

You can view the contents of .conf files in the File Commander (MENU>Sources / Files) by navigating to the file and pressing OK.

[Sandy B]

The filename you should use (at least in firmware 20210119) is smb-user.conf, not smb_user.conf.

I am using the latest firmware, but did not realise the file name change to smb-user.conf. I changed the file name and installed into samba.

Why do you want to give Windows share access to the PVR's root directory?

I find that when trying to play a file on the computer using Openwebif program it does not work, and consequently use File Explorer to play files, I cannot do that with the T4’s attached HDD. Also much easier to copy from computer to attached hard drives.

Thanks for your help all working now.

[prl]

I find that when trying to play a file on the computer using Openwebif program it does not work, and consequently use File Explorer to play files, I cannot do that with the T4’s attached HDD. Also much easier to copy from computer to attached hard drives.

You don't need to allow access to the filesystem root to do that, access to /media/usb should do it.

Allowing access to the filesystem root allows the possibility that firmware files might be removed or modified accidentally. If you want root access to modify those files intentionally, then the problem of accidental modification is what you live with. If you only want to access USB drives, you don't need to allow root access.

Thanks for your help all working now.

No problem.

[Grumpy_Geoff]

I find that when trying to play a file on the computer using Openwebif program it does not work, and consequently use File Explorer to play files, I cannot do that with the T4’s attached HDD.

You should be able to stream from an attached USB device using OWIF. See below where I streamed a recording.

Listing of directory on USB drive -

Streamed recording -