Ranjan Maitra <maitra.mbox.ignored <at> inbox.com> writes: > So, I have a strange problem which I can't figure out. After Friday's > updates, I was unable to ssh into the machine with a nonstandard port. > I changed the port to the default and was able to get in. I was able to > resolve this only after stopping and starting iptables service. Possible simple explanation: Do you have an iptables rule that restricts access to the target system to a specific host? If so, did you specify the system to allow in using a host name (or FQDN) or did you use that system's IP address? If the host name can't be resolved at startup but resolves once the system is fully up, you could have an explanation for the behavior you're seeing. I think I've also seen this with a slow DNS or a resolv.conf that includes an unavailable DNS server. Cheers, Dave -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
