That would probably allow a ssh connection unless there is some deeper problem with the firewall like a bad NAT rule which is more difficult to diagnose. You can add a temporary firewall allow rule, so you can test to see if the firewall is an issue, by running: iptables -I INPUT -m tcp -p tcp -dport 22 -j ACCEPT If, however, it returns 20 or more lines of output, there is probably a firewall in place. However, it may also mean that there are no rules. If iptables-save returns nothing, it may mean that you aren't running it as root. If it's not there, you'll probably need to have whoever runs the networking check firewalls that may exist there. If you have root access on the server, check the host firewall with iptables-save | less (or similar if it's not Linux). If SSH for some reason isn't running, you would get a 'connection refused' error. If that takes many seconds and reports 'Connection timed out', it really does seem like there's a firewall in the way.ДЄs you say, if tcpwrappers was the problem it would likely be as 'connection closed unexpectedly' result. Use the IP address from the ping in the telnet and telnet to the SSH port. Though not being able to ping it does not mean that you don't have connectivity to it, as pings could be filtered out. If you can ping it, you know you have network connectivity to it. The ping will test the resolution of the name into an IP and that you can ping that host. Try breaking down the connection into the individual steps performed at the network level: 'Connection timed out' sounds like a firewall issue. Is it possible that the firewall blocks certain ip addresses and allows other? Now the error is different and I think that it has to do something with firewalls of the network, I just don't understand why I could log in before with a different IP and now I can't. I am sure it's not the hosts.allow issue because when my ip wasn't allowed I had a different error message, something like: 'The server connection closed unexpectedly' and was trying to reconnect in 5 secs. The server is located on a VLAN which should be accessible to me, I can ping it but I can't connect to it through putty or WinSCP, it listens on the default port 22, I have a dynamic IP and everytime I have to connect to the server a colleague who has static IP logs onto it and adds my ip to the hosts.allow file, It worked fine at first but lately it stopped working. Red Hat Satellite 5.8 - satellite-schema-5.8.0.Hey guys, I am having a problem with connecting to a red hat enterprise linux server through ssh, the following error appears:.Red Hat Satellite 5.7 - satellite-schema-5.7.0.37.File '/usr/lib64/python2.6/socket.py', line 567, in create_connection File '/usr/lib64/python2.6/httplib.py', line 771, in connect File '/usr/lib/python2.6/site-packages/rhn/connections.py', line 144, in connect File '/usr/lib/python2.6/site-packages/rhn/connections.py', line 166, in connect File '/usr/share/rhn/proxy/rhnShared.py', line 128, in _connectToParent ValueError: embedded newline in response header with name 'SERVER_SIGNATURE' and value'(address)Apache/2.2.15 (Red Hat) Server at Port 80 Registration via Satellite Proxy mod_wsgi (pid=2557): Exception occurred processing WSGI script '/usr/share/rhn/wsgi/xmlrpc.py'. (60, 'ORA-00060: deadlock detected while waiting for resource The message was: Connection timed out on readlineДatabase reports deadlock issues on Oracle Spacewalk 19921 9 12:12:04 -04:00: ('Unhandled exception', URI: /XMLRPCД®rror reported from client rhn-plugin: Error communicating with server. Exception while handling function registration.new_system Satellite timed out when trying to register a new system => /var/log/httpd/error_log Red Hat JBoss Enterprise Application Platform.Red Hat Advanced Cluster Management for Kubernetes.

Network error connection timed out