When you say "I cannot ssh into the server" ... how much time are you giving it? Do you wait 3 minutes to see if it connects? If not, consider the possibility that the DMZ server cannot do DNS lookups properly, and you are experiencing the well-known delays associated with reverse-lookup failures. The fix is to get DNS working on the DMZ host. (Or do what I sometimes do; add an entry in /etc/hosts for the IP address you ssh in from; I use this when I remote-admin systems, so DNS problems don't delay troubleshooting connections.)
Only a guess, of course, based largely on your saying a direct connection succeeds "within seconds". At 09:18 AM 2/13/02 -0700, Scott Sandeman-Allen wrote: >Hi, me again! > >I have configured my Dachstien CD based router and parts are working >quite fine. My web server can be seen from its dedicated public IP >and from my masq. network.Unfortunately, I cannot ssh into the server >via the public-ip & router. This despite the fact I have enabled the >port in the same places and the same way as with tcp:80. > >A few days ago I could only get ssh running by having a separate port >(222) forwarded to 22 on the server. > >Off the top, here are some of the pertinent settings: > >DMZ=YES > >SSH & WWW open with EXTERN_TCP_PORTn="0/0 ssh <public_IP>/n" etc. > >INTERN_SERVERS="tcp_<public_IP>_ssh_<dmz_IP>_ssh" > >DMZ_OPEN_DEST="tcp_<public_IP>_ssh" > > (where public-ip is one of my static IPs from the ISP.) > >I have been over the settings quite a few times and did find a couple >of errors but still, no SSH. If I bypass the router,the systems link >within seconds and it all works fine. -- ------------------------------------"Never tell me the odds!"--- Ray Olszewski -- Han Solo Palo Alto, CA [EMAIL PROTECTED] ---------------------------------------------------------------- _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
