LAN/SMB problem occurred network communication
Wanted to connect via lan to my PC, setup fine with green tick, when click on the already setup lan PC, shows problem occurred on network communication. Using Guest auth, since my other PC can connect via lan also without username pass.
i had to turn on the smb 1.0 /cifs windows features, it fixed for me 🤷♂️
Using Windows 10_64 on a network with a Buffalo LS220 NAS.
NAS: Had to use SMB1.NAS is set to use either SMB1 or 2.
USB drive on wireless router USB port had to use SMB1 also.
demitria stevara commented
I can establish connection to my pc when i sign in using local account instead of microsoft account.
G. E. M. J. commented
I just managed to pass over the Green Button, but now stuck in the "problem occurred on network communication" error. It seems it stopped to work when paid for the app.
G. E. M. J. commented
I have been struggling for more than a year to connect, use SMB1 worked fine. Thanks all!
After suddenly losing the ability to reliably connect to my W10 network shares via SMB1 and SMB2, the only fix I could find was creating a new Standard user account and using those credentials to connect via Solid Explorer. Not sure if a specific Windows update broke the old account or what, but it was simple enough. None of the other troubleshooting steps helped.
Bits Nagle commented
I formatted my Windows 10 Home and installed Windows 10 pro, but when I am trying to connect Solid Explorer with my PC it throws me error "A problem occurred with Authentication. Please login again". P.S. in username and password I am putting Microsoft account credentials as I was using before formatting, then I was able to access my PC through Solid Explorer SMB
Ken Natco commented
I couldn't get Solid Explorer to connect to the drive plugged into my Asus router. I finally discovered that clicking on "YES" for advanced on the 2nd to last setup screen offered the choice of smb1 or smb2. It had been on smb2. Switched to smb1 and it connected instantly. Yay!
The solution that works. Tested on two different phones.
1) Open Solid Explorer,
2) make sure you have internal storage on both panels(Left and right panel).
3) Reboot the phone
4) open Solid Explorer, and navigate to your SMB.
Should open without a problem.
There is a bug that causes this issue when you used a different cloud connection and then switch to SMB. Some buffer or cache was not cleared. Developer please fix.
To reproduce this issue have a cloud connection (Dav) open on the right panel. Then try to setup a new SMB connection OR connect to an existing one, it should fail.
Is this ever going to get fixed. This was working fine for the last year or two, but now stopped working with the "problem occurred on network communication" error. A different phone with the same version of Solid Explorer works fine, as does CX File Explorer.
Bit annoying when I paid for this
Todd M commented
I know this is old, but I found it on 11/4/20 so maybe someone else will. I ended up looking at the IP when I hit browse for the computer I wanted and then entered that instead. It worked.
I had the same issue, so first I tried all combinations with SMB// etc (like Greg on the 18. August 20) without success. By the way: in German I can edit the connections via ... > Speicher-Manager
Then I deleted the SMB connection and tried again from scratch ("+" > Neue Cloud Verbindung > LAN/SMB).
But this time I let Solid E. search the network for my PC and this took a while but found it.
I selected this connection in "Server-Details" put User and Password and now it works :)
This looks like a bug in Solid E. in that SMB-feature for me. Please fix :)
Brad Dawson commented
Hi can anyone please help me? I have the paid version of the fx file explorer the file Manager with privacy. on my Nvidia shield tv pro 2019 my Computer windows 10 is on the same network my Internet connection is great Whenever I try to open fx connect. I get no Internet connection can anyone please tell me how to fix it? Thank you very much
I have the same problem. I use private network profile on Window 10, with access for files without password. Connection between 2 Win10 computer - worka! Between Linux and Windows - works! Between Windows and Soli? No way!
I'm trying switching between smb1 and smb2, adding SMB//, smb//, SMB:// and smb:// prefixes to host name and even loging by using username and password from Windows profile (not necessary on linux or other Windows) - nothing changes.
I have that problem too, and add it that works for me too.
[Deleted User] commented
Adding SMB//[SERVERNAME] worked for me! Thanks guys for this suggestion!
Zach McDonough commented
As Hansmiller mentioned below, adding SMB// before the hostname/address works for me (eg. SMB//192.168.1.1 or SMB//SERVERNAME)
I've a tab s2 android and tried for hours to connect to my w10 machine with all updates installed. Gave up. Two days later it just works. FM.
Rajat Patel commented
I managed to find a solution to this.
All you need to do is to set the network profile as "Private" and then it works from solid explorer without issues.
It works for me after maybe 12 hours of trial and error over a 3-day period.
Remote host name: Enter your IP address as is. (do ipconfig and find IPv4 Address)
Port Number: 445 (I only knew this from one of the other websites. I figured it should have been the listening port for my IP, but nope)
Display Name: Computer Name (shown as name when doing nslookup on your IP address)
Username and password authentication selected
Username as shown in the path in CMD after the /
Password was tricky, because it's not my Windows password which uses a 4-digit pin. It also is not my gmail address associated with the account. It was a third password that I often use elsewhere; I may have gotten lucky on this try. One thing to note is that I did use this password to create my LAN (different from my wifi password, so maybe that's what it used???)