Thank you. Checked again, background data on both Android devices enabled. Each of their status bars say after the plugin start:
"TotalCmd-LAN (Windows-F...
Servername: Krotus-PC
Alle Verbindungen trennen"
This last line made me think a connection was established.
Unable to connect to LAN with latest rev 3.59 of TotalCmd-LAN
Moderators: petermad, Stefan2, Hacker
Re: Unable to connect to LAN with latest rev 3.59 of TotalCmd-LAN
Addendum: FritzBox-Protokoll liefert zum Zeitpunkt des Einwahlversuchs 2MBit/s down und 75,6 kBit/s up für das Mobile.
Last edited by TC-KA on 2026-02-16, 14:17 UTC, edited 1 time in total.
Re: Unable to connect to LAN with latest rev 3.59 of TotalCmd-LAN
I couldn't understand it's a name/password issue, since, without modifying anything, the connection is OK at the second try... (and sometimes at the first try)
But, nevertheless, maybe it's "almost" such issue, because, in my particular case, the login is anonymous : neither name nor password. I made it OK from my laptop standpoint, but could this be a problem for your plugin ?
But, nevertheless, maybe it's "almost" such issue, because, in my particular case, the login is anonymous : neither name nor password. I made it OK from my laptop standpoint, but could this be a problem for your plugin ?
Re: Unable to connect to LAN with latest rev 3.59 of TotalCmd-LAN
Hier noch der Debug-Log:
2026-02-16 15:16:56.875 HOST:LAN:checkConnectionAlive: 1
2026-02-16 15:17:03.612 HOST:LAN:get dir: /Krotus-PC/users/Admin/Documents/
2026-02-16 15:17:03.619 LAN:DEBUG c.h.p.c.socket.ProxySocketFactory - Connecting to /192.168.2.104:445
2026-02-16 15:17:08.628 LAN:DEBUG c.h.p.c.socket.ProxySocketFactory - Connecting to /192.168.2.104:445
2026-02-16 15:17:13.634 LAN:SMB2 CONNECT:failed to connect to /192.168.2.104 (port 445) from /192.168.2.107 (port 38094) after 5000ms
2026-02-16 15:17:15.138 LAN:DEBUG c.h.p.c.socket.ProxySocketFactory - Connecting to /192.168.2.104:445
2026-02-16 15:17:20.150 LAN:DEBUG c.h.p.c.socket.ProxySocketFactory - Connecting to /192.168.2.104:445
2026-02-16 15:17:25.156 LAN:SMB2 CONNECT:failed to connect to /192.168.2.104 (port 445) from /192.168.2.107 (port 49788) after 5000ms
2026-02-16 15:17:26.660 LAN:DEBUG c.h.p.c.socket.ProxySocketFactory - Connecting to /192.168.2.104:445
2026-02-16 15:17:31.671 LAN:DEBUG c.h.p.c.socket.ProxySocketFactory - Connecting to /192.168.2.104:445
2026-02-16 15:17:36.676 LAN:SMB2 CONNECT:failed to connect to /192.168.2.104 (port 445) from /192.168.2.107 (port 55858) after 5000ms
2026-02-16 15:17:38.183 LAN:DEBUG c.h.p.c.socket.ProxySocketFactory - Connecting to /192.168.2.104:445
2026-02-16 15:17:43.192 LAN:DEBUG c.h.p.c.socket.ProxySocketFactory - Connecting to /192.168.2.104:445
2026-02-16 15:17:48.196 LAN:SMB2 CONNECT:failed to connect to /192.168.2.104 (port 445) from /192.168.2.107 (port 36708) after 5000ms
2026-02-16 15:18:33.125 HOST:LAN:checkConnectionAlive: 1
2026-02-16 15:22:24.578 tc:Move 1 files:/storage/emulated/0/.TotalCommander/->/storage/emulated/0/Download/
2026-02-16 15:16:56.875 HOST:LAN:checkConnectionAlive: 1
2026-02-16 15:17:03.612 HOST:LAN:get dir: /Krotus-PC/users/Admin/Documents/
2026-02-16 15:17:03.619 LAN:DEBUG c.h.p.c.socket.ProxySocketFactory - Connecting to /192.168.2.104:445
2026-02-16 15:17:08.628 LAN:DEBUG c.h.p.c.socket.ProxySocketFactory - Connecting to /192.168.2.104:445
2026-02-16 15:17:13.634 LAN:SMB2 CONNECT:failed to connect to /192.168.2.104 (port 445) from /192.168.2.107 (port 38094) after 5000ms
2026-02-16 15:17:15.138 LAN:DEBUG c.h.p.c.socket.ProxySocketFactory - Connecting to /192.168.2.104:445
2026-02-16 15:17:20.150 LAN:DEBUG c.h.p.c.socket.ProxySocketFactory - Connecting to /192.168.2.104:445
2026-02-16 15:17:25.156 LAN:SMB2 CONNECT:failed to connect to /192.168.2.104 (port 445) from /192.168.2.107 (port 49788) after 5000ms
2026-02-16 15:17:26.660 LAN:DEBUG c.h.p.c.socket.ProxySocketFactory - Connecting to /192.168.2.104:445
2026-02-16 15:17:31.671 LAN:DEBUG c.h.p.c.socket.ProxySocketFactory - Connecting to /192.168.2.104:445
2026-02-16 15:17:36.676 LAN:SMB2 CONNECT:failed to connect to /192.168.2.104 (port 445) from /192.168.2.107 (port 55858) after 5000ms
2026-02-16 15:17:38.183 LAN:DEBUG c.h.p.c.socket.ProxySocketFactory - Connecting to /192.168.2.104:445
2026-02-16 15:17:43.192 LAN:DEBUG c.h.p.c.socket.ProxySocketFactory - Connecting to /192.168.2.104:445
2026-02-16 15:17:48.196 LAN:SMB2 CONNECT:failed to connect to /192.168.2.104 (port 445) from /192.168.2.107 (port 36708) after 5000ms
2026-02-16 15:18:33.125 HOST:LAN:checkConnectionAlive: 1
2026-02-16 15:22:24.578 tc:Move 1 files:/storage/emulated/0/.TotalCommander/->/storage/emulated/0/Download/
Re: Unable to connect to LAN with latest rev 3.59 of TotalCmd-LAN
Solution / reason found!
Disabling Windows Defender Firewall -> Private Network restored the access for both devices' Plug-in to the PC's files again.
It seems that either the recent Windows Update or Defender Update has locked out the LAN-Plugins.
Now it's the question if and how that "Private Network"'s Firewall can be configured such that it gives access to the Plug-Ins again even when activated.
In the meantime, thanks alot, Ghisler, for your patience!
EDIT
Here is the Windows Defender Firewall's configuration that works for me:
In the LAN Plug-In's settings, check SMB2 and SMB3
Set the Windows Firewall [Private Network]: Active
Open
"Allow Access of App through Firewall" (on the bottom of the "Firewall and Network Protection" window).
On the top right of the new window, select "Change Settings"
Then, check below the column "Private":
-> "File and Printer Sharing" [X]
-> "File and Printer Sharing via SMBDirect" [X]
Exit window with OK on its bottom.
You may wish to finally clear the cache of the Plug-In.
Disabling Windows Defender Firewall -> Private Network restored the access for both devices' Plug-in to the PC's files again.
It seems that either the recent Windows Update or Defender Update has locked out the LAN-Plugins.
Now it's the question if and how that "Private Network"'s Firewall can be configured such that it gives access to the Plug-Ins again even when activated.
In the meantime, thanks alot, Ghisler, for your patience!
EDIT
Here is the Windows Defender Firewall's configuration that works for me:
In the LAN Plug-In's settings, check SMB2 and SMB3
Set the Windows Firewall [Private Network]: Active
Open
"Allow Access of App through Firewall" (on the bottom of the "Firewall and Network Protection" window).
On the top right of the new window, select "Change Settings"
Then, check below the column "Private":
-> "File and Printer Sharing" [X]
-> "File and Printer Sharing via SMBDirect" [X]
Exit window with OK on its bottom.
You may wish to finally clear the cache of the Plug-In.
- ghisler(Author)
- Site Admin

- Posts: 53162
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
Re: Unable to connect to LAN with latest rev 3.59 of TotalCmd-LAN
That's odd, why would the firewall let connections through only sometime?
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
Re: Unable to connect to LAN with latest rev 3.59 of TotalCmd-LAN
With TC for Android 3.62b2d with Plugin 3.60 on Android 16 and with TC for Android 3.62 with with Plugin 3.60 on Android 14 I still can't connect:
The connection on the Android 14 device is unchanged since it was working.SMB2 AUTH:STATUS_ACCESS_DENIED
(0xc0000022): Authentification failed
for * using com.hieronymous.smbj.auth

