SABnzbd Forums

So I elected to rebuild my HTPC and moved from Vista to Win7. I configured everything basically the same way I had before and point all my files to an unRaid server. I've started to notice that some of my post-processing in SAB has failed. Upon looking in the log it appears it couldn't find the dir? I go to Windows explorer and sure enough my shares have a red X through them, but the instant I click on the share they are accessible. Then if I manually call the same file again the post-processing works fine. Has anyone experienced this? Are there any workarounds to have the share seen rather than manually clicking on it?

When you initially connect a share, there should be an option
that basically says " reconnect on next system start".

Thanks, however, I initially chose that when creating the mapped drives.

Could be an issue with Win7 trying to use SMB3, whereas Vista I think only supported SMB2. And unraid by default doesn't appear to support either.

I had an issue with Sab running on an XP machine saving its files to a share on a Win7 machine but the network drive dropping off the XP machine, and the solution was to disable SMB2 on the WIn7 machine.

Try

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters]
"SMB2"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters]
"SMB3"=dword:00000000

and see what happens

Thanks. I might give that a try some time when I need to rebuild my Media Browser cache. It takes quite some time and since I've got it all finally working now I feel I should leave it as-is. If memory serves it was UAC that was interfering with the mapped drives. I know I'm taking on some risk here, but I've got to believe it is pretty minor, that is, I had to completely disable UAC. Once I did that all the mapped drives show up upon each boot without any of the inaccuraet red x's. It has worked hundreds of times now without an issue.