Unable to connect to LAN with latest rev 3.59 of TotalCmd-LAN

[LaurentG]

Since I updated yesterday on F-Droid TotalCmd-LAN from 3.57 to 3.59, I'm no more able to connect to LAN !

I have not changed anything on my laptop, only the version of TotalCmd-LAN on my Smartphone, but now when I try to connect, I get the following error (that I never got it before, with rev 3.57) :

SMB2 AUTH:STATUS_ACCESS_DENIED
(0xc0000022): Authentification failed
for * using com.hieronymous.smbj.auth
///LAN/Dell-Laurent

What can I do ?
Is there a place where to get the previous version, and rollback ?

[sqa_wizard]

May you are still using deprecated SMB1 ?
At properties of your connection (long tap on the connection name) try to enable option for NAS compatibility.

[LaurentG]

I do not use SMB1 (and I do not want to use it !)
Moreover, which connection do you suggest I modify ? On the phone, or on the laptop ?

Anyway, I do not want to change anything.
With rev 3.57 of TotalCmd-LAN, it used to work. This mean that the connections themselves are OK.
And I do not have modified anything, except I upgraded TotalCmd-LAN from 3.57 to 3.59

[sqa_wizard]

The only connection properties you can modify is the the connection on the phone.
This was just a guess, because my connection from phone (Android 14) to PC (Windows 11) is still working fine.

[ghisler(Author)]

Have you tried 3.60 (beta) I mentioned in my reply to your other post?

I wrote:
3.59 uses the latest smbj library. Some users have reported that it doesn't work with their PCs. I have rolled back to the older library in 3.60, which is currently in the beta channel. I hava put that in the beta F-Droid repository now:
https://www.ghisler.com/fdroid.htm

[LaurentG]

Yes, it works ! Thanks a lot !
I'm waiting for the final version, in the "non beta" thread...

I take the opportunity of this post to indicate you that it works.... but with the same problem than before, ie. sometimes, connection initially fails, but after clicking on "Disconnect", it works the second time.
Sometimes, it is even necessary to repeat two times the scenario : Connect -> fail, Disconnect, Connect -> fail, Disconnect, Connect -> OK

[ghisler(Author)]

Can you find out under which conditions the connection fails?
The only situation I know about is when you have two servers with the same name in different networks, e.g. at home and at work, and they have different IP addresses. The library used by the LAN plugin caches connections, so it could still try to access the wrong address.

[LaurentG]

Never been able to find any condition that could explain.
It actually occurs more often when connecting to my laptop (Win10), vs connecting to my wife's laptop (Win11)...
Once connection is OK, if disconnect, the next one is OK in 99.999% of the cases.
Next problem will occur only "long time" after (probably after having switch off WiFi for a time on the phone, then on again , eg. the day after).

And about your hypothesis of several server with the same name, I'm completely out of this picture :
- I'm connecting only at Home, either to my laptop or to my wife's one
- and moreover, I do not connect by name but by IP address (it was one of your advice I read a long tile ago, I do not remember exactly where....)

Anyway, this problem is more annoying than really blocking....

[ghisler(Author)]

It sounds like your laptop is getting different IP addresses each time it connects. If the smb library has still cached the connection to the old IP address, the connection will initially fail. Then it drops the cached connection and the next connection attempt will work.

Solution: Connect to your router's web interface and check whether you can assign a fixed address to your laptop in the DHCP settings.

[LaurentG]

No, of course, to be able to connect by IP, both my laptop and my wife's one have fix IP addresses...

[ghisler(Author)]

You could try to enable logging in Total Commander, maybe it shows you why the connection failed.

[LaurentG]

I just did it.
Of course, first connection after logging enabled was OK at the first try ! Thank you Mr Murphy !

Nevertheless, I let logging enabled, And I'll have a look next time I have the issus, and I'll share it with you.
Thanks.

[LaurentG]

I just got the issue.
First try => Not OK
A second try immediately after (without clicking on disconnect between both) succedeed.
I used the connection to upload the log.txt from totalcommander, and I copy it above.
We can see some log for the unsuccessful attempt, but on the other hand, nothing about the succesful attempt
And we can see the browsing to temp directory on laptop, and the copy of log.txt from smartphone to laptop.

Personnally, I do not understand, reading this log file, why first connection attempt failed. It looks like it was rejected by the laptop, but on the other hand, my laptop never reject a connection coming from elsewhere than my phone....
As a result, I would be very surprised that the problem is on laptop side... since it occurs ONLY with the smartphone....
Moreover, I do not have any "event" in windows event log at the timestamp of unsuccesful connection (and my smartphone and my laptop are strictly synchronized).

2026-02-15 11:47:28.676 HOST:LAN:initiate connection to plugin
2026-02-15 11:47:28.681 HOST:LAN:bindService succeeded
2026-02-15 11:47:28.687 HOST:LAN:WaitUntilConnected:Background
2026-02-15 11:47:28.753 HOST:LAN:Service connected!
2026-02-15 11:47:28.758 HOST:LAN:get dir: /
2026-02-15 11:47:28.782 HOST:LAN:checkConnectionAlive: 1
2026-02-15 11:47:31.334 HOST:LAN:get dir: /Dell-Laurent/
2026-02-15 11:47:31.362 LAN:CONNECT Dell-Laurent
2026-02-15 11:47:36.001 LAN:SMB2 CONNECT:failed to connect to /192.168.1.65 (port 445) from /10.1.10.1 (port 32910) after 5000ms: isConnected failed: ECONNREFUSED (Connection refused)
2026-02-15 11:47:40.612 LAN:SMB2 CONNECT:failed to connect to /192.168.1.65 (port 445) from /10.1.10.1 (port 32928) after 5000ms: isConnected failed: ECONNREFUSED (Connection refused)
2026-02-15 11:47:45.217 LAN:SMB2 CONNECT:failed to connect to /192.168.1.65 (port 445) from /10.1.10.1 (port 41522) after 5000ms: isConnected failed: ECONNREFUSED (Connection refused)
2026-02-15 11:47:49.827 LAN:SMB2 CONNECT:failed to connect to /192.168.1.65 (port 445) from /10.1.10.1 (port 41546) after 5000ms: isConnected failed: ECONNREFUSED (Connection refused)
2026-02-15 11:47:54.046 HOST:LAN:get dir: /Dell-Laurent/
2026-02-15 11:47:58.660 LAN:SMB2 CONNECT:failed to connect to /192.168.1.65 (port 445) from /10.1.10.1 (port 37064) after 5000ms: isConnected failed: ECONNREFUSED (Connection refused)
2026-02-15 11:48:23.804 HOST:LAN:get dir: /Dell-Laurent/
2026-02-15 11:48:26.495 HOST:LAN:get dir: /Dell-Laurent/Temp/
2026-02-15 11:48:32.427 HOST:LAN:checkConnectionAlive: 1
2026-02-15 11:48:32.430 HOST:LAN:get dir: /Dell-Laurent/Temp/
2026-02-15 11:48:32.532 tc:Copy 1 files:/storage/emulated/0/.TotalCommander/->///LAN/Dell-Laurent/Temp/

[TC-KA]

Since three days, all of a sudden, I am experiencing on my mobile and my tablet the identical issue as LaurantG. I tried everything mentioned before, including the newest version 3.60, and checked successfully the permission for the mobile to open ports in my router.
System:
Win 11 latest version
Router Fritz!Box 7590AX 5 GHz all - WPA2+WPA 3 - "communication between all registered devices allowed" [x]
Pixel 6 Pro - fix IP address - WiFi 6, WPA 3
Samsung Tablet S7+ - fix IP address WiFi 6, WPA 2

The log

2026-02-15 13:59:18.568 HOST:LAN:checkConnectionAlive: 1
2026-02-15 13:59:18.574 HOST:LAN:get dir: /
2026-02-15 13:59:22.064 HOST:LAN:get dir: /Krotus-PC/Users/Admin/Documents/
2026-02-15 13:59:22.077 LAN:CONNECT Krotus-PC
2026-02-15 13:59:32.097 LAN:SMB2 CONNECT:failed to connect to /192.168.2.104 (port 445) from /192.168.2.107 (port 34596) after 5000ms
2026-02-15 13:59:43.611 LAN:SMB2 CONNECT:failed to connect to /192.168.2.104 (port 445) from /192.168.2.107 (port 39330) after 5000ms
2026-02-15 13:59:55.131 LAN:SMB2 CONNECT:failed to connect to /192.168.2.104 (port 445) from /192.168.2.107 (port 50618) after 5000ms
2026-02-15 14:00:06.650 LAN:SMB2 CONNECT:failed to connect to /192.168.2.104 (port 445) from /192.168.2.107 (port 52572) after 5000ms

seems to say, as that of LaurentG, that the plug-in does find the server, but simply is not able to open port 445 in time, although permitted on router's side.
By the way, before that issue the mobile was continuously connected to the PC and re-connected automatically when either of both was switched off and on at any time.
Thanks for looking into it again.

[ghisler(Author)]

These don't look like the same issue:
2LaurentG
You are getting a "connection refused" error, which means that the plugin manages to connect, but the login fails. The plugin retries with anonymous credentials when this happens, so please double check your user name and password.
2TC-KA
The plugin doesn't even connect to the server. Maybe you have disabled background data on your phone? The plugin is invisible, so it's always in the background.