Ok I have 2 Linux computers on my home network a linksys router and my own domain. I can SSH into my main computer fine. I now want to ssh into my 2nd linux computer, so I made a new entry on my routers UPnP forwarding page:

ext.port = new port
Protocol is TCP
Int.Port is 22.
IP Address is the local internal IP of the 2nd computer.

Problem is if I'm connected to PC1 and then ssh to PC2 it disconnects both sessions and won't let me ssh into either box for about 10 minutes or so. I've tried to ssh from both putty in windows and command line from a Linux box(remotely of course)

It seems there is a conflict somewhere, any ideas as to why it disconnects when I ssh into the 2nd computer?



When I say ssh, I mean remotely not internally from PC1 to PC2...

5/16/2006 2:04:41 PM

what distro?

Do you have some funky firewall going or something?

What happens when you connect to both boxes on the LAN side?

5/16/2006 2:12:06 PM

Could you have a conflict with the second port forwarding entry? Seems that you would only need one port forwarding entry to handle ssh from outside the router to your main computer. You shouldn't need port forwarding to ssh between two computers that are both behind the router.

5/16/2006 2:18:25 PM

Box one is Slackware 10.2, Box two is Debian Sarge. Shouldnt be any weird firewall rules. I'm remote right now, But if I ssh into Box one then ssh into box two from box one it's fine. It's just if I try to open 2 putty sessions, one for each box that it disconnects me.

5/16/2006 2:19:14 PM

set ssh to run on another port on one of the machines. 23 is good since no one runs telnet anymore

5/16/2006 2:29:20 PM

yeah thats your best bet because how does you router know to handle on the wan side what box if its set to port 22 on both right now.

5/16/2006 2:43:17 PM

^^ I swear I had tried that before and it didn't work.. I just set port 23 open for box2 and it worked. I also changed the default port in sshd_config and ssh_config..

^

In therory the way I had it set up, its supposed to see portx and forward it to port 22 on box2. It worked.. But there was some conflict that would cause the sessions to drop. So far so good on just opening port 23 to ssh. Thanks.

5/16/2006 2:48:59 PM

That would suck, I use telnet all the time.

5/16/2006 6:40:47 PM

You know that telnet is incredibly insecure, right? And by insecure, I mean not secure at all.

5/16/2006 8:00:12 PM

I hope he's kidding about the telnet comment and by ssh I meant ssh2.

5/16/2006 9:25:54 PM

All depends on what you are using it for.

Some devices only support ssh v1 anyhow.

Just like some things only do WEP.

5/16/2006 10:00:38 PM