Joseph Ervin
My feedback
2 results found
-
4 votes
An error occurred while saving the comment An error occurred while saving the comment Joseph Ervin
commented
Ok,...I got it to work. Just in case nobody else replies, the trick for me was to create a key on the server side (Fedora36 linux) specifying the PEM key format:
% ssh-keygen -b 2048 -t rsa -m PEMThis resulted in a key that had the format:
-----BEGIN RSA PRIVATE KEY-----
.
.
-----END RSA PRIVATE KEY-----This worked. Without the "-m PEM" argument, the default output of Fedora36 ssh-keygen was in openssh format, i.e.
-----BEGIN OPENSSH PRIVATE KEY-----
.
.
-----END OPENSSH PRIVATE KEY-----While Solid Explorer was happy consuming the OPENSSH key, the connection would not work.
I hope this helps others...
Sincerely,
Joe
Joseph Ervin
shared this idea
·
-
233 votes
An error occurred while saving the comment Joseph Ervin
commented
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!!!!!
An error occurred while saving the comment Joseph Ervin
commented
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.
Joseph Ervin
supported this idea
·
Actually, I retract my previous comment. I went through the whole process again, and now I'm able to make it work with an rsa key created with all default options from ssh-keygen on my Fedora36 build. Not sure what problem I was having initially.
I generated the key with:
% ssh-keygen -t rsa
which shows the "OPENSSH PRIVATE KEY" text at the start and end of the private key file. I used that to create that into solid explorer and it seems to work just fine. Sorry for the misdirection from my previous comment where I thought the private key needed to be in the older "PEM" format. I must have fat-fingered something somewhere along the way. The OPENSSH private key format works fine.