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? ~~~ Local LAN - 192.168.0.0 to SLES 10 server on 192.168.0.0 ~~~ Starting nmap 3.81 ( http://www.insecure.org/nmap/ ) at 2007-01-30 10:04 PST Interesting ports on 192.168.0.6: (The 1656 ports scanned but not shown below are in state: closed) PORT STATE SERVICE 22/tcp open ssh 111/tcp open rpcbind 389/tcp open ldap 427/tcp open svrloc 631/tcp open ipp 888/tcp open accessbuilder 10000/tcp open snet-sensor-mgmt ~~~ Remote LAN - 192.168.1.0 to SLES 10 server on 192.168.0.0 ~~~ Starting nmap V. 3.00 ( www.insecure.org/nmap/ ) Interesting ports on (192.168.0.6): (The 1594 ports scanned but not shown below are in state: closed) Port State Service 22/tcp filtered ssh 111/tcp open sunrpc 389/tcp open ldap 427/tcp open svrloc 631/tcp open ipp 888/tcp open accessbuilder 10000/tcp open snet-sensor-mgmt ~~~ Remote LAN - 192.168.1.0 to Suse 10 server on LAN 192.168.0.0 ~~~ Starting nmap V. 3.00 ( www.insecure.org/nmap/ ) Interesting ports on (192.168.0.44): (The 1593 ports scanned but not shown below are in state: closed) Port State Service 22/tcp open ssh 111/tcp open sunrpc 139/tcp open netbios-ssn 445/tcp open microsoft-ds 631/tcp open ipp 888/tcp open accessbuilder 5432/tcp open postgres 10000/tcp open snet-sensor-mgmt Thank you in advance, James -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
