> Jack if you can ping, but not connect something has specifically been
> done to prevent ot rather than it hasnt been configured to work.
>
> If its not deliberately firewalled out it is just possible that the
> daemons are not binding to the correct interface
>
> Netstsat is your friend and will show you what is listening on what
> ports.
>
> netstat -an | grep LISTEN | grep 'tcp '
>
> iptables will whow you what firewall rules are in place.
>
> sudo iptables -L

Thank you all for your contributions to this thread.  I learned a lot.

My son found the following blog item which seems to have solved the
problem.

https://expresshosting.net/ssh-hanging-authentication/

I added the indicated changes and all ssh connections now work
independent of who is wired or wifi.

It seems the problem lay with the raspberries rather than the wiring.

To be more precise, the interaction between the RPi and my ten year old
router.

My apologies for setting this false wifi/wired trail in the first place.

Jack

--- SoupGate-Win32 v1.05