NextPVR and NAS support

[rosede]

I wrote ShareHelper and use it everyday and yes it works. Not sure about your virus scanner. It is an old file so the MD5 hasn't changed since 2010 1b47ec0b574b1e753ec624043a82a0e6

Seems it has been checked online too http://whitelisting.kaspersky.com/adviso...043a82a0e6 and https://www.reasoncoresecurity.com/share...9ea49.aspx with no problems.

Martin

I'll take another look at it.

Thanks

Daryl

[rosede]

I installed "ShareHelper" as instructed. The first attempt failed with invalid user name:

Code:

2016-12-08 07:58:09:686 VERBOSE    [?]    ShareHelper Service Started
2016-12-08 07:58:09:694 VERBOSE    [?]    Mounting R: \\nas01\NextPVR\Recordings
2016-12-08 07:58:11:158 VERBOSE    [?]    Mount Error The specified username is invalid
2016-12-08 07:58:11:158 VERBOSE    [?]    Mounting T: \\nas01\NextPVR\TEMP
2016-12-08 07:58:13:391 VERBOSE    [?]    Mount Error The specified username is invalid

I did not pass a user name and password, so I inserted my user name in the xml file. I am an administrator on the NAS, so the utility should be able to read/write with no issues.

Code:

2016-12-08 08:04:03:192 VERBOSE    [?]    ShareHelper Service Started
2016-12-08 08:04:03:201 VERBOSE    [?]    Mounting R: \\nas01\NextPVR\Recordings
2016-12-08 08:04:05:683 VERBOSE    [?]    Mount Error The specified server cannot perform the requested operation
2016-12-08 08:04:05:683 VERBOSE    [?]    Mounting T: \\nas01\NextPVR\TEMP
2016-12-08 08:04:07:095 VERBOSE    [?]    Mount Error The specified server cannot perform the requested operation

Any thoughts as to what the issue might be?

Thanks

Daryl

[mvallevand]

Normally you would mount to the share point not a sub directory in the share

ie \\nas01\NextPVR

Also Windows shouldn't let you map two letters to the same share point. Use R:\Recordings and R:\Temp in NextPVR and ignore T:

Martin

[rosede]

Normally you would mount to the share point not a sub directory in the share

ie \\nas01\NextPVR

Also Windows shouldn't let you map two letters to the same share point. Use R:\Recordings and R:\Temp in NextPVR and ignore T:

Martin

Martin,

I remounted the share as you suggested

e.g. \\nas01\NextPVR

I adjusted the .xml to reflect the new mount point:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
<appSettings>
<add drive="R:" share="\\nas01\NextPVR" username="daryl" password="" />
<!--add share="\\192.168.1.101\videos" username="nmt" password="1234" /-->
</appSettings>
</configuration>

I then changed the "Live TV Buffer" location to R:\Temp

I started ShareHelper and stop/started NextPVR. I still receive the same errors in the log:

2016-12-11 04:40:40:790 VERBOSE [?] ShareHelper Service Started
2016-12-11 04:40:40:798 VERBOSE [?] Mounting R: \\nas01\NextPVR
2016-12-11 04:40:41:747 VERBOSE [?] Mount Error The specified server cannot perform the requested operation

Any additional suggestions?

Thank you.

Daryl

[mvallevand]

Did you try with the IP rather than netbios name?

Martin

[rosede]

Did you try with the IP rather than netbios name?

Martin

Yes I did. I use DNS and I can resolve the NAS correct. I even tried FQDN as well as the IP, but I still get the following error:

2016-12-11 05:53:17:004 VERBOSE [?] ShareHelper Service Started
2016-12-11 05:53:17:012 VERBOSE [?] Mounting R: \\192.168.0.130\NextPVR
2016-12-11 05:53:17:820 VERBOSE [?] Mount Error The specified server cannot perform the requested operation

Any additional thoughts?

Daryl

[mvallevand]

Hooking up a Windows client to a Linux share is really dependent on how you make their security match, The fact that you can't even enable a guest account on your NAS makes it sound very basic which doesn't match the Enterprise grade defaults in Windows. Maybe try reducing the encryption from 128 bit in you file share options https://www.tenforums.com/tutorials/5102...-10-a.html You can also tell Windows SMB to not require a security signature which is another problem.

Martin

[rosede]

I finally got this to work. I created a nextpvr user (with password) on the NAS and passed the user and password in the sharehelper.xml file. That finally resolved this issue.

Thank you very much for your assistance.

Daryl