Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top
/etc/rinetd.conf 443 636
allow *

>lsop -i|grep rinetd
rinetd    27099        root    4u  IPv4 2553556       TCP *:https (LISTEN)

Also iptables -L -n returns nothings.

Still, if I try to telnet to localhost (or using the server IP) to port 443 it will work but if I try the same from another machine it will fail with telnet: Unable to connect to remote host: Connection timed out

So, there is something on that port but it does not want to respond.

What am I missing?

share|improve this question
How does it fail? Do you get an error? If so, what error? – David Schwartz Jul 31 '12 at 10:51
If the connection times out, that means no response is coming back from the network. That's almost always caused by a firewall. (Probably a software firewall on the destination machine.) – David Schwartz Jul 31 '12 at 10:53
This would be very award as all machines I tested can connect directly to the destination one – sorin Jul 31 '12 at 10:56
Try changing to your server IP address – Manula Waidyanatha Jul 31 '12 at 11:02
@ManulaWaidyanatha I already tried this but there is no difference. – sorin Jul 31 '12 at 11:28

"Connection timed out" usually indicates a firewall is in place. If it wasn't the firewall, it would say "Connection refused" or something similar (in case service isn't accessible). Run service iptables stop and if you are on RH based OS be sure to check SELinux and disable it for the time of debugging with setenforce 0.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.