Ye' old general discussion board. Basically, for everything that isn't covered elsewhere. Come here to shoot the breeze, shoot your mouth off, or whatever suits your fancy. This forum is not for asking programming related questions.
I am trying to give outside SSH access to my test server but for some reason even though I forward port 22 to the machine, it won't connect. Here is my output:
shiznatix@Joker:~$ ssh -l USERNAME SERVER.COM -vvv
OpenSSH_4.3p2 Debian-8ubuntu1, OpenSSL 0.9.8c 05 Sep 2006
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to SERVER.COM [IP_ADDRESS] port 22.
then it just hangs. I of course can ssh through the internal network but it's just when I try going from the outside that I have problems. I am not sure what really to do so I am hope that one of you network savvy awesome-heads can give me a kick in the right direction.
its not my computers firewall because i can ssh into other servers no problem.
how do i check my servers routing table and firewall? i would think that the servers firewall would not be the problem because i can ssh into it from inside the network but maybe i am wrong? How do I go about checking this (command line only)?
shiznatix wrote:its not my computers firewall because i can ssh into other servers no problem.
how do i check my servers routing table and firewall? i would think that the servers firewall would not be the problem because i can ssh into it from inside the network but maybe i am wrong? How do I go about checking this (command line only)?
Does anything else forward without troubles? Port 80 for example. If nothing forwards then it's definitely a routing or firewall issue. The reason I said routing is because it looks like the connection is opening through NAT, but never actually being responded too.
shiznatix wrote:port 80 goes no problem. port 20 - 22 goes but I have troubles with PASV FTP connections. Those are the only other things this server is using.
PASV FTP connections can't truly be forwarded/rerouted. The details are complicated, but the result is that you would need to forward ports 20-21 and 1024-65535.
Most good FTP clients offer a setting that can help with this issue. I highly recommend Filezilla, a GPL FTP client for windows.
Port 40 is not exactly "non-standard". I was thinking that you should try a port from 49152 to 65535. Also, note that starting a process listening to that low port number requires root privileges, although the ability to connect internally seems to discredit this. Maybe you should explain that more (is it from a different computer on the network?)