On Tuesday 30 January 2007, James D. Parra wrote: > Hello, > > Set up a SLES 10 server and although I can ssh to it from any box on the > local LAN I can't get to it from a remote LAN even though I can ssh to any > other box on the local LAN via ssh. All of the other servers are running > Suse 9.1 to Suse 10, while the one I can't connect to remotely is running > SLES 10. > > The sshd_config is identical to the other servers and the firewall is off. > Nmap results show that the ssh port on the SLES 10 server is appearing as > filtered from the remote network and open from the local LAN. Only the SLES > 10 box has this behavior. Any ideas? Since you seem to be connecting to the same port (192.168.0.6) regardless of where you attempt to connect FROM, I can only assume the machine has only a single nic, Is that right?
Therefore, a connection to that nic from a local machine is going to the same port as a connection from another lan. It seems to me that the firewall is not really off, or that there is a subnetting mask error such that packets can't get back from 192.168.0.6. ~~~~ That seems right to me and, yes, there is only one nic in the server. Any ideas on how to fix it? Where is the conf file (if there is one on SLES 10) for the Firewall settings? When viewing the logs on the host server, it doesn't record ssh login attempts from the remote LAN. From the remote ssh client, ssh just times out. I can ping the host from the remote LAN, but remote ssh packets aren't arriving at the host, or so it appears. Many thanks, ~James -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
