Topic: [SME 6.0.0][SSH] Port 22 closed ??

[G2LOQ]

Hi,

I'm desperately trying to connect to my SME box using SSH from the WAN but the port 22 stays always closed for the outside (my box is quite far from my home). I used this link to check my box : https://grc.com/x/ne.dll?bh0bkyd2
I have the same problem with the https protocol (443), it's also always closed (no webmail with https possible). From the LAN, everything works perfectly. I'm sure my configuration in the "server-manager" is correct.
Does anybody able to give me a track where I can search ?

[mbachmann]

Server Manager -> Security -> Remote Access?

[G2LOQ]

Server Manager -> Security -> Remote Access?

Well, that's already done but my ports seem to stay closed.

Maybe, the first thing to learn is how I can check the state of my ports seen from the WAN? And with this test, checking if the state changes when I use the server-manager Remote-Access panel.

Do you know how I can do that or if you imagine a better way to start? I stay stuck

[Anonymous]

Try iptables --list on the console, search for ssh and https entrys/ports. Try also iptables -h and man iptables.

[mbachmann]

... and don't forget to seach for iptables here. There is also a contrib called masq-manager from Muzo which gives a comfortable overview via server-manager.

[G2LOQ]

Hmmm... with that kind of log I can only suspect that my provider blocks the ssh and https ports. Is there a way I can check it?

Code: [Select]

Chain InboundTCP_24513 (1 references)
target prot opt source destination
denylog all -- anywhere !10.x.x.x
ACCEPT tcp -- anywhere anywhere tcp dpt:auth
ACCEPT tcp -- anywhere anywhere tcp dpt:ftp
ACCEPT tcp -- anywhere anywhere tcp dpt:www
ACCEPT tcp -- anywhere anywhere tcp dpt:https
ACCEPT tcp -- anywhere anywhere tcp dpt:imap2
denylog tcp -- anywhere anywhere tcp dpt:ldap
ACCEPT tcp -- anywhere anywhere tcp dpt:pop3
ACCEPT tcp -- anywhere anywhere tcp dpt:1723
ACCEPT tcp -- anywhere anywhere tcp dpt:smtp
ACCEPT tcp -- anywhere anywhere tcp dpt:ssh
denylog tcp -- anywhere anywhere tcp dpt:telnet

BTW thanks for your help

[mbachmann]

The ssh port on SME is open if you set it via server manager.

Try connecting your server from elsewhere on 22.
Just ask the provider if the port is closed.
Search for "shields up" or a similiar service to check the port. Make sure it is open at the testing time.
Nmap and Ethereal (also for Winbloze) are other tools to check.

[Lada]

Saw that this morning. I've said it before....for all you want to talk about United and their international profile http://www.development.h12.ru/, they really seem to do business the right way. I'm interested to see just how much Kenyon had to do with these results, so next year will be interesting.

[wlu_lax6]

Topics containing links to people's sites are unneeded and contribute nothing as a whole, much like topics containing content like this one. You could have PMed a moderator and asked this same question and received the same http://www.development.h12.ru/ response. Please do so in the future.