I'm not sure if this is a DOpus problem or if I just don't get network sharing in Windows. From Windows 11 I can't browse my other computer (Windows 10) to see what folders are shared so I just put the full path into the adress bar. Windows explorer shows a credentials dialog if I do that but DOpus tells me that the network name was not found (error code 67). Once I have accessed the folder through Windows Explorer it works on DOpus too.
On both machines I have set my network on private and applied the same sharing settings (enable discovery, enable file sharing, enable password protection).
It definitely works on Windows 10, other than prompting for credentials twice (which is a bug in Windows itself). It's possible Microsoft have broken the API even more in Windows 11.
Does anything else other than File Explorer work here?
I have only one program that doesn't use the native file dialogue to open files over a network: PDF-XChange Editor. And it showed the same behaviour as DOpus. I can only access the shared folder after opening it once in Windows Explorer.
I had the same issue today. Reinstalled Win 11 to have a clean install and I had to use Explorer for the first connection to my NAS. Opus only showed a blank tab with a loading sign and tried to connect. But there was no credential dialog - at least not within a few seconds... Then I closed the tab and tried it with explorer to check if this is a general issue, but explorer showed immediately the dialog.
After log-in via explorer I can connect to the NAS via DOpus.
Is this a Win 11 issue? Other people does not have this issue? I guess most Win 11 User have an upgrade, but no clean install and so the credentials are still remembered.
I deleted the credentials in windows and tried it again. Now I got immediately the error 67.
After adding 67 to the setting you mentioned and restart of DOpus I got a credential dialog and could connect to the NAS.
The NAS is from Synology.
So I assume that it is a Win 11 issue, because for sure there were a lot of Win 10 + Synology + DOpus users the last years and if you did not get similar reports the last years...
(Or most users simly use one time Explorer and ignore the issue)
Different Synology devices / updates have a surprising variety of behaviors in our experience, but if the same NAS/firmware worked OK in Windows 10 then it's probably a Windows 11 change.
Not too important what the cause is, though, since it's something we can work around.