SMB stands for Server Message Block, a network protocol enabling file sharing, printing, and communication between devices. A very slow SMB connection refers to a sluggish data transfer process, often caused by network congestion, hardware limitations, or latency issues. This sluggishness leads to extended file access times, delayed responses, and overall poor performance in accessing shared resources, impacting productivity and operational efficiency within a networked environment. If you are looking for a career in any technical field and improving your technical skill, get courses like python certification course, data science , machine learning, iot and many more courses.
visit:https://www.theiotacademy.co/python-training

SMB SERVER CONNECTION IS VERY SLOW. TAKE TOO MUCH TIME TO OPEN FILE AND FOLDERS.

also attached screenshot of speed.

Has anyone figured out how to fix this? I've got a S8 with slow SMB speeds.

Ok,...here's progress. I've determined that if I specify the SMB server by "name", then the connection happens more or less immediately. However, if I specify the server by ip address, which I am forced to do on some ad-hoc networks (like at home) where my linux SMB server is not known to the DNS server, then it take 20 seconds to connect. Solid does not have a way to specify name versus ip address when specifying the server (it really should!!!) and so I'll bet that Solid is trying for the first 20 seconds to resolve the ip address as a name via DNS, and timing out after 20 seconds and then attempting to use it directly as an IP address. This is pretty brain-dead. Solid should allow a server to be specified by name or by IP address in an unambiguous way so it won't subsequently have to try to resolve an ip address as an ascii string, i.e. as though my server's *name* was "192.168.1.102", when really that's its direct ip address. I could be wrong about the underlying problem, but it seems clear that Solid is timing out after 20 seconds trying to do *something*, which does not occur if I specify the server by a DNS-resolvable name. But it should work properly in either case.

Please fix this!!!!!

With the demise of ES Explorer, I'm in the market for a new tool, and Solid Explorer is a strong candidate, but frankly, the 20 second delay every time I connect to my samba servers is a deal breaker. I'm going to keep looking.

Netbytes,...you have a real opportunity to clean up in this space, but you've ignored this serious slow SMB connection delay problem for what looks like many years. Badly done on this front. Solid looks nice in other ways, but this is a deal breaker.

Still not fixed

can this please get fixed already holy shit

samba is 1/3 speed of other apps

*not a real fix*

I've got this problem too. Solved it by disabling SMB2.0 in Windows 10 and enabling SMB1.0 (default is disabled) .

Run Powershell as administrator and enter the following commands, then reboot.

set-smbserverconfiguration -enablesmb1protocol $true
set-smbserverconfiguration -enablesmb2protocol $false

You might have to have to add SMB1.0 as an optional part of Windows. The menu can be found in the windows config screen.

Now I know this is not the fix you've been hoping for, but it beats nothing.

This. Very much this.

sad that this is still a problem
browsing in SE is significantly slower than ES.
I have a directory of ~3300 files that never loads with SE but loads in 3 seconds with ES.
But, for reasons that are obvious to everyone that's used ES in the last year or so, I don't want to use it.

Any update on this?

For some reason the problem went away on my Nexus 5X, but I got a new Moto G5 Plus now and I'm hitting the same 15-20 second connection issue. I have the settings exactly the same as on the Nexus, sitting here with both and one takes half a second while the other takes an unacceptable amount of time.

This is a very old issue now.

Same here. It takes 20 seconds to connect to a PC in the network and when trying to open a share it just returns an error 0xc0000005

Same here. Both with smb and sftp. Neatbytes, any comment?!

Ditto here on s8. Takes for ever to copy some mp3 over my nas.

Experience the same problems with file transfers using Samba. Slow and will often get failing result.

LAN/smb rarally works, and when it do, is very slow.

My SMB connection does not work. Any ideas as to why?

Same for me. S7 on Nougat. Not sure if Nougat is to blame or what. But I have a NAS that I usually stream videos from using MX Player. Transfer rate is very slow. If I use FTP protocol, everything is very fast, like expected.

Almost unusable for me.