Mapped Drives not showing.

[Keith Rogers]

Hello.  May I say great product, even bought the pro version.  But alas the one thing I wanted it versatility for doesn't seem to work.  I'm running a NAS with smb drives which work fine in explorer but fail to materialize in OC.  I've tried mapping through OC still very buggy.  Is this something you're aware of.  Is windows having a moan due to OC possibly being elevated?  Dunno.  Any advice would be appreciated.  

I'm running the latest pro version on Up to date Windows 11. 

Regards

[OneCommander Support]

When OC is running elevated it uses a different user context so drive mapping is for a "different" user. OC shouldn't run elevated as Windows won't allow drag and drop, context menu items may be different, created files might get different permissions and other things may not work as expected. This is just the way Windows itself works

[Keith Rogers]

Thankyou for the reply.  Even running normally and not as Admin I get the same issue of mapped drives coming and going randomly. 

[OneCommander Support]

Regardless if you map through OC or through Explorer (or Drives>Map Network Drive (Winodows)) it is using the same Windows API to mount it underneath, and it maps direcly on Windows itself, so it the mapping, credentials, connection, lifecycle... are all managed outside of OC. 

When you say it is coming and going, I am not sure what could be going on there as I have both at work drive mapping as SMB3 to Windows Server and a Synology Rachstation and at home to low cost Synologogy Diskstation and I didn't notice issues with it. Is just the drive not showing or it is not accessible at the moment where Explorer can still access it? Try opening directly \\NAS\share and adding that to sidebar favorites, and when it disappears, check if that one still connects. When that happens it is also worth checking Windows Event Viewer for anything network related logged into it, and I can see what I can make OC log to the log files related to drives coming/going and if there is any message attached to those events

[Keith Rogers]

Reguarding this I think I've fixed my problem. I tried TrueNas side with -  

midclt call smb.update '{"smb_options": "smb3 directory leases = yes"}'
service smb restart

So far the drives contents smb windows side are now renumerating as expected.  You did mention SMB3 in your reply but apparently it was off by default for me.  Fingers crossed it sticks. 

Thankyou

[OneCommander Support]

Please let me know if this doesn't ended up not resolving the problem. I didn't know what this command does nor did I work with TrueNAS so I asked AI for other suggestions to your original problem

On Windows clients

• Increase/work around idle disconnects: set LanmanWorkstation\Parameters\KeepConn to a higher value (e.g., 65535 seconds). Microsoft Learn+1

• Ensure the NIC isn’t being powered down: disable “Allow the computer to turn off this device to save power.” Microsoft Learn

• Make logon drive mapping reliable: enable “Always wait for the network at computer startup and logon.” This avoids timing issues so the network is up before mappings are processed. Also ensure “Reconnect at sign-in” on the mapping. Microsoft Learn+1

• Prefer mapping by FQDN (stable DNS) vs. IP, and keep client time in sync (Kerberos/SMB signing can be sensitive to clock skew). Microsoft Learn

On the Samba/TrueNAS side

• Don’t rely on Windows-only autodisconnect; in Samba the analogous control is deadtime (minutes before idle sessions are closed). Keep it 0 (no idle drop) or set conservatively for your environment. (See smb.conf parameter docs.) Samba

• Ensure TCP keepalives are reasonable (Samba uses OS keepalives; very aggressive timeouts on intervening firewalls/VPNs can still kill idle sessions). Samba

• Leave durable handles enabled (default for SMB2/3) so clients can seamlessly recover file handles after brief blips. This helps after a hiccup, but it’s not the same as preventing disconnects. wiki.samba.org+1

• Keep Samba/TrueNAS up to date; newer Samba (4.22+) has directory leases on by default for non-clustered setups and many SMB robustness fixes. wiki.samba.org