Another Thanks to you guys!
I’m able to transfer files now, but I have a few questions I would appreciate answers to, if they are of general interest.
Yes, the sshd needed to be started on each box. Starting it at boot using “expert” caused the network daemon to be started at boot as a dependency.
After rebooting I looked at sshd in the “simple” display. The simple sshd status showed as no*. Expert showed it running. Before I got an ssh connection, I added levels 2,3, and 5, but these may not be necessary.
Before I used yast to start sshd, I removed the ssh service from the firewall settings to see if yast would enable that. Nothing happened, so I manually readded the allowed firewall ssh service. This time I didn’t add any ports.
Ssh is now using port 22, but I don’t see that open port showing up anywhere. A question related to port visibility, is where would this port 22 status show up?
Another question I have at this stage relates to the firewall setting. What does this do? “Protect firewall from internal zone?” It has a checkbox on ssh Allowed Service. This was not enabled by default, but ssh works with the box checked.
So for the file transfer status, I can run ssh from either box, but neither hostname is recognized. So far ssh only works with the IP address. So another question is how and where to enter these hostnames to be recognized?
The IP addresses are not trusted. Originally A dunning comment essentially asked if I wanted to proceed, because ssh didn’t. When I typed out the full work “yes” it connected.
A qusetion here is how to make the host trusted? There are a number of files related to the ssh, several of which are key files. I’m expecting something has to be added to one or some of these files.
Maybe typing yes to the untrusted prompt makes an addition to one or same of these files.
The LXDE file manager doesn’t yet see the other host. It’s networking seems to be geared toward samba. That’s not a big deal as ssh works on it now. Also scp works on the LXDE box, but so far, only from the ssshell.
Another question I have is should scp work from a terminal? My expectation is that it should if the ssh setup is in place.
Dolphin on the KDE box works easily, but if using the hostname rather than IP, it also gives the response “Unable to connect to server. Please check your settings and try again.”
One problem with having to use IP addresses to connect is that the router assigns these addresses in the order the computers are power up. That makes them dynamic in the last digit.
I can live with this, but getting the connections to work with hostnames would be a bonus.
Other than these lingering details, this thread is solved. I’ll wait to see if I get some suggestions regarding the lingering details before I report it solved.