Can no longer save to network drive

[kamakamadaun]

I have been using DMS for many years recording directly to my NAS. It used to be that the only thing needed was to make sure that the service was running under my user (otherwise there is no access to network drives). But now it stopped working, meaning it records to "C:\Users\Public\Videos" and the status is unable to see free space indicating no access I guess.

Time-wise it coincide with an upgrade to Windows 11 24H2 so I assume it is related. There are many posts online about network issues with 24H2 but they seem more related to accessing a host running 24H2. I tried disabling the firewall as this was the cause of some of the reported issues but that doesn't help.

I tried nextPVR too and it has the same problem.

Does anyone know what could have gone wrong or even how to start debugging this? I realize this is not directly a DSM issue, but I hope someone here has experience with this problem. I don't even know how to debug this as the problem is related to things running as a service.

[Griga]

vor 3 Stunden schrieb kamakamadaun:

I have been using DMS for many years recording directly to my NAS. It used to be that the only thing needed was to make sure that the service was running under my user (otherwise there is no access to network drives). But now it stopped working, meaning it records to "C:\Users\Public\Videos" and the status is unable to see free space indicating no access I guess.

 

Try to run the Media Server as application (not as service) in your user account. Use the tray menu to stop it as service, then double-click DVBVservice.exe in your DVBViewer program directory, which lets a small window appear. Does this enable NAS access?

 

vor 3 Stunden schrieb kamakamadaun:

Time-wise it coincide with an upgrade to Windows 11 24H2 so I assume it is related.

 

Windows 11 24H2 seems to be more or less a PITA, as many posts in the web suggest

 

[kamakamadaun]

Yep that works. Thanks! Now if only the server window could be minimized to tray it would be perfect...

[kamakamadaun]

OK. It seems I finally found the root cause. When restarting to test running the media server as an app I noticed my network drive was not mounted on startup.

It asked for credentials again. But giving it the credentials was not enough. DVBViewer didn't work correctly (with the drive mounted and working in windows) even after logging in again. And after another restart windows again asked for credentials for the network drive.

So in the end it seems the credentials somehow got fubar'red. Removing the credentials from the credentials manager and adding the back seems to have solved the issue. The service now works as before.

Edited December 30, 2024 by kamakamadaun