+1

And also an issue in a similar topic. The network shares must be first clicked and mounted in the OS and only then are available in mucommander. I tried adding these as SMB, etc., but nothing works. The only solution is to mount these manually every day (they disconnect daily; corporate environment) and only then access them via bookmarks.

@pskowronek that's funny, I was wondering about this myself this week. I worked on adding ADB (#919) and I saw that in trolCommander they've added a menu that lists the devices, so I thought about adding an OSGi service that returns a menu from the plugin that is added to the drive buttons - and I saw we have those network shares and bonjour there. I was trying to see if I can extract them to be a different OSGi bundles that return such a service and realized that smb:// is queried and wondered if it ever returned anything (btw, we had an issue before that smb://<URL>/ didn't return the list of shares on the server - that is supposed to be fixed already). so long story short, I don't know if it ever worked but it also didn't work for me. and I ended up extracting the bonjour menu :)

here, smb connections are working fine, but if I want to connect to a webdav, this will not work. neither in http nor in https. I first have to connect to the webdav via finder on my mac, then I can connect to the webdav in muCommander by choosing it under "volumes". When I try to connect to the webdav directly with muCommander, I get the message "Dieser Ordner existiert nicht oder ist nicht verfügbar" (similar in English: "This target doesn't exist or is unreachable"). The login credentials are correct.

Hi there, it's me again :)
I am using a Macbook Pro with macOS 15.1. (Sequoia) and M1 Pro processor.
Today I tried to connect to a smb share with muCommander (the "connect to server" icon in the menu bar) but it fails.
The credentials are correct but the share is not connected. Instead of that, a message appears. I added the message at this post.
If I connect the same share with the same credentials in finder, it works. After that, I can reach the share under "/Volumes/sharename" in muCommander.
The behavior is the same as written by many at 2003, May, 8th above.

is there any news or a way to fix this behavior?

ChatGPT might have the actual answer as to why it's happening:

This is a known issue with muCommander’s SMB support. It doesn’t use macOS’s own SMB stack (like Finder does), but instead relies on JCIFS (Java CIFS client), which is outdated and only supports SMB1 (NTLMv1).

Your symptoms (Finder works, muCommander fails with “incorrect credentials”) happen because:

• Modern Windows Server / Active Directory defaults to SMB2/3 and NTLMv2 or Kerberos.
• JCIFS in muCommander can’t negotiate those protocols.
• When you type in correct credentials, the AD server rejects them because the auth mechanism is too old.

Options / Workarounds

1. Force NTLMv1/SMB1 on the server side (not recommended, insecure, usually disabled by admins).
2. Try a JCIFS fork with SMB2/3 support, e.g. [SMBj](https://github.com/hierynomus/smbj) — but muCommander doesn’t support it out of the box.
3. Use a different file manager on macOS that relies on the system’s SMB stack (like ForkLift, Commander One, Double Commander with GVFS). These will behave like Finder.
4. Mount the share in Finder first (smb://domain;user@server/share) and then access the mounted volume via muCommander (navigate to /Volumes/...). That way muCommander just sees it as a local path.