Unable to record to Synology NAS with guest account

[vmq]

Hi!

I'm currently migrating to a new system and I run into the problem of not being able to record to my Synology NAS. This was addressed before, see for example here:
http://forums.nextpvr.com/showthread.php...ord-to-NAS or http://forums.nextpvr.com/showthread.php...ot-working

And frankly on my old system under Windows XP I solved this issue by mapping a drive letter under the system account. Now, the new system is a running Windows 10 and I wanted to keep it as clean as possible, so I created a share on the NAS that the guest account can access without password. This was suggested previously.

Well, that doesn't work. Below is an excerpt from my NRecord.log, first trying to record to the NAS, then to a local directory:

Code:

2016-12-14 17:14:46.269    [DEBUG][10]    Requesting wake up for 'RecordingOID851-backup' at 12/14/2016 5:18 PM
2016-12-14 17:14:46.269    [DEBUG][10]    Requesting wake up for 'RecordingOID851' at 12/14/2016 5:17 PM
2016-12-14 17:15:09.601    [DEBUG][48]    ReloadSettings()
2016-12-14 17:15:09.601    [DEBUG][48]    Checking for new capture devices
2016-12-14 17:15:09.601    [DEBUG][48]    CaptureSource.LoadAll()
2016-12-14 17:15:09.664    [DEBUG][48]    ReloadSettings()
2016-12-14 17:15:09.665    [DEBUG][48]    Checking for new capture devices
2016-12-14 17:15:09.665    [DEBUG][48]    CaptureSource.LoadAll()
2016-12-14 17:19:00.124    [DEBUG][10]    DefaultDirectoryChoice: first
2016-12-14 17:19:00.362    [DEBUG][10]    allocating recording target filename: \\GUPPY\mc_rec\rec_tv\Manual Recordings\Default_20161214_17201730.ts
2016-12-14 17:19:00.362    [DEBUG][10]    About to start recording (851 on 20): \\GUPPY\mc_rec\rec_tv\Manual Recordings\Default_20161214_17201730.ts...
2016-12-14 17:19:00.362    [DEBUG][10]    Asking NDigitalHost to start: \\GUPPY\mc_rec\rec_tv\Manual Recordings\Default_20161214_17201730.ts
2016-12-14 17:19:01.743    [DEBUG][10]    Temp at 12/14/2016 5:19:11 PM
2016-12-14 17:19:01.743    [DEBUG][10]    Started recording (851:25:\\GUPPY\mc_rec\rec_tv\Manual Recordings\Default_20161214_17201730.ts)
2016-12-14 17:19:01.803    [DEBUG][10]    Invalid file passed to StartParallelProcessing(): '\\GUPPY\mc_rec\rec_tv\Manual Recordings\Default_20161214_17201730.ts'
2016-12-14 17:32:00.239    [DEBUG][10]    Stopping recording (851 on 20). Past end time of recording. 25
2016-12-14 17:32:00.311    [DEBUG][10]    StopStream(19)

Code:

2016-12-14 17:39:58.627    [DEBUG][10]    Requesting wake up for 'RecordingOID852' at 12/14/2016 5:38 PM
2016-12-14 17:40:00.179    [DEBUG][10]    DefaultDirectoryChoice: first
2016-12-14 17:40:00.180    [DEBUG][10]    allocating recording target filename: C:\temp\Manual Recordings\Default_20161214_17401750.ts
2016-12-14 17:40:00.180    [DEBUG][10]    About to start recording (852 on 20): C:\temp\Manual Recordings\Default_20161214_17401750.ts...
2016-12-14 17:40:00.180    [DEBUG][10]    Free space 285377081344  (C:\)
2016-12-14 17:40:00.180    [DEBUG][10]    Asking NDigitalHost to start: C:\temp\Manual Recordings\Default_20161214_17401750.ts
2016-12-14 17:40:01.446    [DEBUG][10]    Temp at 12/14/2016 5:40:11 PM
2016-12-14 17:40:01.446    [DEBUG][10]    Started recording (852:26:C:\temp\Manual Recordings\Default_20161214_17401750.ts)
2016-12-14 17:40:01.456    [DEBUG][10]    No C:\Users\Public\NPVR\Scripts\ParallelProcessing.bat

I checked as a different user that the guest access to my NAS actually allows to RW and create files.

If I try accessing the share from a cmd.exe running as system user (PsExec) I get:

Code:

C:\Windows\system32>dir \\guppy\mc_rec
The specified server cannot perform the requested operation.

For other users the dir command works.

Seems like system on Windows 10 is a little different.

Any suggestions what to try next?

Volker

[JavaWiz]

Do you happen to log into windows 10 with a PIN? If so, you might want to check out this thread. Switch back to a password, and it may work

[vmq]

Do you happen to log into windows 10 with a PIN? If so, you might want to check out this thread. Switch back to a password, and it may work

No, I'm logging in with a regular (strong) password. Nice catch, but that link is about share access for "normal" users. Normal user, even ones that are unknown to the NAS work fine, it's just that the system account seems to have problems, hence no recording.

Volker

[ACTCMS]

Why not just change the Nrecord service to run under a user account rather than system?

Alex

[vmq]

Why not just change the Nrecord service to run under a user account rather than system?

Alex

That's my fall back plan. I was just looking for options to set up recording without third party tools (ShareHelper), mapping a driver letter to a network share for the system account or changing the internal settings of the Nrecord service.

The last one seems the least intrusive though. Maybe sub could make that an option for NPVR (hint, hint ;-) ).

Volker

[mvallevand]

If you use the IP it should work fine with a guest share.

Martin

[vmq]

If you use the IP it should work fine with a guest share.

Martin

That's what I thought. First a test from a user that has no corresponding user on the NAS:

Code:

C:\Users\vquet>dir \\192.168.1.168\mc_rec
Volume in drive \\192.168.1.168\mc_rec is mc_rec
Volume Serial Number is F26D-1A74

Directory of \\192.168.1.168\mc_rec

12/14/2016  05:11 PM    <DIR>          .
12/14/2016  05:03 PM    <DIR>          ..
12/14/2016  05:33 PM    <DIR>          rec_tv
12/14/2016  05:33 PM    <DIR>          rec_mv
               0 File(s)              0 bytes
               4 Dir(s)  2,606,730,264,576 bytes free

Works fine, no password or credentials needed, but if I start a shell as system user (PsExec.exe -i -s cmd.exe) I get this:

Code:

C:\Windows\system32>dir \\192.168.1.168\mc_rec
The specified server cannot perform the requested operation.

And finally, if I try to access a share that has a password set, I get:

Code:

C:\Users\vquet>dir \\192.168.1.168\mc
Access is denied.

So the system user is somehow special - or Synology is doing something weird with the guest account.

If it makes a difference, this is on Windows 10 Pro.

Volker

[mvallevand]

What happens in the admin cmd prompt with

net view \\192.168.1.168

Martin

[vmq]

What happens in the admin cmd prompt with

net view \\192.168.1.168

Martin

System user prompt:

Code:

C:\Windows\system32>net view \\192.168.1.168
System error 53 has occurred.

The network path was not found.

Regular user prompt:

Code:

C:\Users\vquet>net view \\192.168.1.168
Shared resources at \\192.168.1.168

Share name  Type  Used as  Comment

-------------------------------------------------------------------------------
homes       Disk           user home
mc          Disk           Mediacenter NPVR + Kodi files
mc_rec      Disk           Recording destinations for TV clients
music       Disk           System default shared folder
The command completed successfully.

[vmq]

Just to bring this to an end. I changed the user of NPVR Recording Service to an account that has permissions on the NAS. Now I just have to remember to change it again when the next NPVR version comes around.

For posterity:
In the Services applet in Windows, locate the "NPVR Recording Service". Right click and select properties. Then click on the "Log On" tab change it from using the service account to a windows account with permission to read/write to the share (it also needs read/write permission to the NextPVR installation and data directories as well.) Click apply and re-start the service.

Volker