tocleora
asked on
Problems accessing ssh, apache, webmin, but not ping?
I have a Fedora 4 box within my company that's been working fine for three months up until yesterday. Apparently two different servers went down (I was not there when it happened), a FreeBSD box that (a) I have no control over and (b) is the primary DNS Server and this Fedora 4 box. Upon rebooting the Fedora 4 box (they shut it off from the power button since they assumed the server was locked up), ssh, apache and webmin will work from that box (ie. I can do a "localhost" and see the web site and a "localhost:XXXXX" and see webmin) but cannot access ssh/apache/webmin on that box from any other computer. I tried ssh'ing into that box and it fails. We pointed the box to a different DNS Server with the same results. What's weird is ping works. We tried running "security levels" from within Gnome but it says "starting" and never does. we tried "iptables -F" with same results. We can access Internet sites from that server and are able to ping the dns server from it, so we assume the problem is only when we ssh/apache/webmin TO the box. Any ideas? I should also mention that I'm not at the server and since I can't ssh in, I can't get to the server so I can't provide additional information at this point... hopefully it's something common/familiar/easy and maybe someone can just point in the right direction of correcting the problem?
rindi
One thing that could be a reason for this is that due to switching the server of just like that may have left some lck files open. Get someone on site to check for such files and delete them, then reboot.
ASKER
Tried that, did a find . -name *.lck -print from / and it returned no results. Found something on a /var/lock folder searching through google for more information regarding *.lck files, but nothing looks familiar in there either... Any other ideas?
ASKER
Resolved the issue, it *was* the firewall. Don't know if it's separate or not, but when "security levels" wouldn't start I found a program called firestarter as well. When I started it, it said that the firewall was active. Making it inactive resolved the issue. I set it not to start when the system started and everything is working now!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.