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

For about 2 weeks now, I have not been able to connect to any services (httpd, mysql, ssh, etc..) on my server remotely. I can access everything from inside the local network just fine.

I thought maybe the ISP started blocking some ports so I set up a XAMPP install on a different local machine. I redirected httpd and sql ports to that machine and was able to access them from outside the network just fine. This leads me to believe it is an issue with the server.

I'm a little confused though as I was able to access the server remotely just fine up until about 2 weeks ago.

The server is running Fedora Core 15.

If I need to post some diagnostic output or anything let me know and I'll add it to the post.

Any help would be appreciated!


It turns out I am unable to see the internet from the server as well.

route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface   U     1      0        0 p8p1         UG    0      0        0 p8p1
share|improve this question
can you ping the server by its hostname from remote network? what does "nmap -sS hostname" comes up with? oh okay so no connection to WAN from the server? – Danila Ladner Aug 21 '13 at 2:24
I can ping the server remotely. nmap shows ths host as down, but run with -Pn shows it as up with all ports being filtered – Matt Swanson Aug 21 '13 at 2:31
Can you stop iptables daemon just for test? – Danila Ladner Aug 21 '13 at 2:45
Brought iptables down, still have same results – Matt Swanson Aug 21 '13 at 2:54
is that host in AWS or rackspace or whatever cloud? – Danila Ladner Aug 21 '13 at 3:03

Verify that the server has the correct IP address set as its default gateway. Also verify its subnet mask.

share|improve this answer
Looks like the ip and mask is set correctly – Matt Swanson Aug 21 '13 at 3:59
All the symptoms you describe intricate a routing problem. You checked the default gateway, correct? That value is key for this server to be able to communicate outside its subnet. – EEAA Aug 21 '13 at 4:07
I updated the post with the output of route -n – Matt Swanson Aug 21 '13 at 4:15

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.