LAN plugin: New beta version available

[JeffCommander]

I've done some more testing.

When I disconnect the cable modem from my router, and all I have is my local network, it works every time with no errors. In case my router had an issue, I bought a new router also, and the same errors occur about 80% of the time, until I again disconnect the router from the external internet.

What I'm thinking is that maybe if the server name is not a Internet address, the LAN plugin should only do a SMB request, and not a DNS request. For example:

If server name = "server" then do SMB.

If server name = "server.com", or "server.example.com", etc. then do DNS.

Thoughts?

[ghisler(Author)]

The problem is that some companies use DNS for local machine name resolution too...

[JeffCommander]

The problem is that some companies use DNS for local machine name resolution too...

Ah, I see. Then I would recommend my previous suggestion whereby the Lan plugin would act as it does now by default , but that DNS and/or SMB could be unselected in the settings by the user.

Would that be difficult to implement?

[Dorset-TX]

Hi,
I have never been able to connect using NetBIOS names so thought I would try these betas but still not working. Tried turning on logging and this is what is logged. Note: I have found you have to prefix the server name with "\" e.g. \OPTIPLEX390\Documents or the server name is simply ignored.

Copy of log.txt:
2014-05-03 19:14:34 LAN:refresh list
2014-05-03 19:14:37 LAN:SMB: Richard@...
2014-05-03 19:14:39 LAN:SMB: Richard@...
2014-05-03 19:15:29 LAN:refresh list
2014-05-03 19:15:32 LAN:DNS Lookup: OPTIPLEX390
2014-05-03 19:15:32 LAN:NetBIOS (192.168.1.255): OPTIPLEX390
2014-05-03 19:15:32 LAN:Lookup: OPTIPLEX390
2014-05-03 19:15:32 LAN:DNS OPTIPLEX390 -> 92.242.132.15
2014-05-03 19:15:32 LAN:SMB: "Richard@92.242.132.15..."
2014-05-03 19:15:52 LAN:refresh list
2014-05-03 19:15:56 LAN:SMB: "Richard@OPTIPLEX390/Documents..."
2014-05-03 19:16:06 LAN:Error connecting to server!
Reported error:
Failed to connect: NETAWARENESS/92.242.132.15
2014-05-03 19:58:27 LAN:refresh list
2014-05-03 19:58:31 LAN:DNS Lookup: OPTIPLEX390
2014-05-03 19:58:31 LAN:NetBIOS (192.168.1.255): OPTIPLEX390
2014-05-03 19:58:31 LAN:Lookup: OPTIPLEX390
2014-05-03 19:58:31 LAN:DNS OPTIPLEX390 -> 92.242.132.15
2014-05-03 19:58:31 LAN:SMB: "Richard@92.242.132.15..."
2014-05-03 19:58:41 LAN:Error connecting to server!
Reported error:
Failed to connect: 0.0.0.0<00>/92.242.132.15
2014-05-03 19:58:59 LAN:refresh list
2014-05-03 19:59:05 LAN:DNS Lookup: OPTIPLEX390
2014-05-03 19:59:05 LAN:NetBIOS (192.168.1.255): OPTIPLEX390
2014-05-03 19:59:05 LAN:Lookup: OPTIPLEX390
2014-05-03 19:59:05 LAN:DNS OPTIPLEX390 -> 92.242.132.15
2014-05-03 19:59:05 LAN:SMB: "Richard@92.242.132.15..."
2014-05-03 19:59:15 LAN:Error connecting to server!
Reported error:
Failed to connect: 0.0.0.0<00>/92.242.132.15
2014-05-03 19:59:40 LAN:refresh list
2014-05-03 19:59:44 LAN:SMB: Richard@OPTIPLEX390/Documents...
2014-05-03 19:59:54 LAN:Error connecting to server!
Reported error:
Failed to connect: NETAWARENESS/92.242.132.15
2014-05-03 20:00:34 LAN:refresh list
2014-05-03 20:00:38 LAN:DNS Lookup: OPTIPLEX390
2014-05-03 20:00:38 LAN:NetBIOS (192.168.1.255): OPTIPLEX390
2014-05-03 20:00:38 LAN:Lookup: OPTIPLEX390
2014-05-03 20:00:38 LAN:DNS OPTIPLEX390 -> 92.242.132.15
2014-05-03 20:00:38 LAN:SMB: "Richard@92.242.132.15..."
2014-05-03 20:00:48 LAN:Error connecting to server!
Reported error:
Failed to connect: 0.0.0.0<00>/92.242.132.15
2014-05-03 20:01:01 LAN:refresh list
2014-05-03 20:01:05 LAN:DNS Lookup: OPTIPLEX390/Documents
2014-05-03 20:01:05 LAN:NetBIOS (192.168.1.255): OPTIPLEX390/Documents
2014-05-03 20:01:05 LAN:Lookup: OPTIPLEX390/Documents
2014-05-03 20:01:10 LAN:SMB: "Richard@OPTIPLEX390/Documents..."
2014-05-03 20:01:25 LAN:Error connecting to server!
Reported error:
Failed to connect: NETAWARENESS/92.242.132.15
2014-05-03 20:04:03 LAN:DNS Lookup: 192.168.1.121
2014-05-03 20:04:03 LAN:Lookup: 192.168.1.121
2014-05-03 20:04:03 LAN:DNS 192.168.1.121 -> 192.168.1.121
2014-05-03 20:04:03 LAN:SMB: "Richard@192.168.1.121..."
2014-05-03 20:04:16 LAN:SMB: "Richard@192.168.1.121..."
2014-05-03 20:04:16 LAN:SMB: "Richard@192.168.1.121..."

The last entry in the log is a successful connect using IP address which is the only way that works for me.

The issue would appear to be that most Internet service providers certainly in the UK have taken to returning an address that points to a webpage for failed lookups. In my case 92.242.132.15 gets resolved to a dns error page on their network.

Strangely the failed to connect is reporting the Workgroup name not the server name.

regards,
Richard.

[ghisler(Author)]

A new beta version of the LAN plugin is available now:
https://plugins.ghisler.com/beta/tcandroidlan207b4.apk

The DNS lookup is now done 2 seconds after the SMB lookup, so the SMB lookup will take precedence. Also the DNS lookup will be ignored if the lookup of a fake name gives the same results. This is for providers who return a standard address if the name doesn't exist.

[JeffCommander]

This works GREAT! And I don't even perceive anything close to a 2 second delay.

Thanks again!

[ghisler(Author)]

Nice to hear that! The 2 seconds delay only applies to DNS lookups (domain name system=internet names). When the server can be found via SMB functions, the lookup will be much faster.

[ghisler(Author)]

Another new beta version of the LAN plugin is available now:
https://plugins.ghisler.com/beta/tcandroidlan207b5.apk

This version has two improvements:
1. Read large directories (several 1000 files) - this didn't work due to a 1MB inter-process communication limit on Android (between plugins and TC)
2. Reading large directories should be much faster now. The JCIFS library is flawed, it re-requests all the file details when reading them (file size, file timestamp, file attributes) instead of using those from the listFiles() command. This was fixed.

[coolskin]

Hi,

if i update the playstore plugin with this beta, will the configured connections be available after update or deleted?

thx & take care
Coolskin

[ghisler(Author)]

Yes, the connections remain available, the plugin is signed with the same certificate. Just do NOT uninstall the previous version!

[karlh]

I have a Galaxy Note 10.1 2014 edition tablet running Android 4.4.2
I am using the 2.05b2 version with the 2.07b5 LAN plugin
Any attemp to copy a file to the Total Commander directory on the external card results in a "Write error"
I can copy files to a USB OTG flash drive, so I know the plugin/NAS is working correctly

[ghisler(Author)]

Sorry, it's not possible, Samsung has locked this in Android 4.4.2.

[mysteray]

Is it not possible to copy/move to the total commander subdir on the sd-card via the LAN plugin or am I the only one facing this problem?

[mysteray]

To clarify. I am aware of the SD card writing restriction under Kitkat. But TC should be able to write in it's own directory, right? Because that's not working via the LAN plugin at least not on my S4.

[ghisler(Author)]

No, it is not possible. Why? The LAN plugin is a separate app, so it has its own protected directory on the SD-Card. Android does not allow it to write to the Total Commander directory.