Asus-router NAS not appearing in Folder Tree or File Display

My Asus-router-connected NAS (USB Drive) does not appear automatically in the Folder Tree or File Display in Directory Opus. The NAS does appear, automatically, in the Windows File Explorer.

I tried rebooting as suggested in an older discussion thread but discovered that I am after the end of the trial period so could not restart Directory Opus nor generate the screen shots I was going to use to describe the problem.

I was able to get the NAS volumes to appear by entering its IP address in the File Display address bar and was then able to browse to them and their sub-folders. I was also able to save shortcuts to the NAS volumes and use those to browse the NAS volumes. But subsequent Directory Opus windows would be missing the NAS volumes in the Folder Tree (Network) and the File Display panes, even while other, already open, Directory Opus windows displayed the volumes in those places.

I have tried searching the forum but seem to be doing something wrong. I am not getting many relevant hits. Even hits I got, I cannot always find again. Searching for "nas folder tree file display" displays 6 hits but not including the post where "nas folder tree file display" were mentioned and where I found some tips for dealing with the problem. I read something useful somewhere; maybe it was a FAQ not a post; but I cannot seem to find it again.

Oh, I did ensure that the server caching was ON. There was one other setting that I confirmed was set the right way. It didn't help.

I'd appreciate any insights. Thanks.

On the same Preferences page, there's a place you can add a list of servers which are always included in the Network list. That may solve the problem, depending on what the reason is for it not appearing automatically.

I found I still had Directory Opus running on a different computer, Windows 11 but same problem.

I am not sure why "Network Servers" would fall under "Folders" in the preferences but I found the spot where I can "add these computers" and I could/would do that but, I am still wondering what might prevent the auto-discovery of NAS units that File Explorer finds with no difficulty.

Edit: I did add the "\\Router-mounted USB" to the added computers list. It did work - part way. See the next post.

I was able to get a couple of Screen shots:

The Windows File Explorer sees the NAS:

But DIrectory Opus doesn't:

Entering "\\router-mounted USB" in the address bar of the File Display seems to add it to the Folder Tree and thereby to provide accress to its contents in the File Display.

But then clicking on Network in the Folder Tree still shows the "Router-mounted USB" in the Folder Tree but not in the File Display.

Closing and reopening (clicking on Network twice) still shows the "Router-mounted USB" under Network in the Folder Tree only.

Adding "\\Router-mounted USB" in Settings | Preferences | Folders | Network Servers now has the NAS appear in the Folder Tree when DO is brought to the foreground and when a new Lister is displayed but still not in the File Display until I click on ""Router-mounted USB" under Network in the Folder Tree. Whether anything changes after a DO/system restart/reboot is something I'll have to wait to discover.

Because "Network" is a (special type of) folder in Windows.

Network discovery has never been reliable in Windows. It also varies from request to request, process to process, and reboot to reboot. It has always been like this, unfortunately.

(Firewall/antivirus can also block some or all processes from seeing some or all servers, although that's unlikely in this case, as you can still access the server.)

That's why we added the ability to force items into the Network folder.

Going to a folder will force it into the tree, even if it hadn't been discovered/enumerated before that.

When the file display shows the Network folder, it delegates it to the Windows shell (File Explorer, more or less), so that isn't even Opus enumerating the computers or displaying the list of them in the file display (only in the folder tree).

That at least proves the problem is with the system rather than Opus itself, since it's going wrong with Microsoft's code as well as ours.