> robin_listas;2498654 Wrote:
>> The commands you were given were to be run on the server, not the
>> Also you commented nothing on the opening of the firewall instructions
> I do not have sudo privileges on the server so I didn’t think to run
> those command on the server. I ran them on my computer and provided the
I think what Carlos wrote is confusing, and what you did was correct. I
think that Carlos may have meant to say to run the commands on the
machine that is running the sshd server daemon, and that is of course
your own computer. Whilst when he said ‘client’, I expect he meant ‘ssh
client’ which is of course running on one of your servers. As I say,
> Apologies for not commenting on the opening of the firewall
> instructions. Provided below is the printout from YAST for the Firewall
> Configuration Summary.
> External Zone
> - Intel Ethernet controller / eth0
> Open Services, Ports, and Protocols
> - Secure Shell Server
> - TCP Ports: XXXX
> Custom Rules
> - 1 custom rules are defined
> It’s still not working. Does it not appear to be a port issue?
So it is saying that the port is open, but nmap says not. However, I
think you ran nmap on 127.0.0.1 - the localhost i/f. I think you need to
run it on the external i/f, whatever IP address you actually use on your
network. However, I might be wrong, I’m not an expert. But please repeat
the nmap with the real IP address.
What is the “custom rule” in the firewall?
Another trick is to use telnet to simulate whatever protocol you’re
having trouble with:
telnet your-ip-address 22
and report back whatever message it gives you.
Even if you eventually want to use a different port, I would stick with
22 until you get ssh working. Otherwise, it’s another factor to get