Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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

Recently I've been having an issue with my CentOS 6 test server running Apache and Webmin running on port 10000 where when I try accessing any part of the server - SSH/FTP and even my domains (I have two - both keep getting timeout errors) when I try accessing from any computer on my home network.

However when I access via tethering or via my office networks everything loads fine.

While the firewall is the first issue at mind, my router never was set to block any special ports, and even after adding port 10000 as a specific exception I'm having no luck.

Also, I doubt this is an IP blacklisting issue because I have websites on other servers using CloudFlare for security and I haven't gotten any warnings.

Any assistance is greatly apprecaiated.

UPDATE: Just some extra details about the issue: My ISP to my knowledge only blocks off ports 25 and 80 for residential users to prevent them from running web servers - however this issue has only come up a day or two ago, before that I was using the server successfully for months.

Also the server is not physically located in any of my workspaces - it's a VPS housed in a datacenter

UPDATE TWO: I've narrowed this issue down to my home router because when I do a direct wire to the modem I do not have the error (which are server timeouts). Additionally I was able to access my site wirelessly shortly via Comodo TrustConnect (which is a VPN) but after an hour or so of working the timeout came back and the software did not help on my other systems.

Setting my notebooks to the DMZ also provided temporary relief but as with the VPN it got choked up after an hour or so of working.

Currently my router is a Linksys/Cisco E200 Wireless N Router and it has been working fine for awhile now so I'm not sure what caused this issue. Any insights are greatly appreciated as this issue has even boggled a few of my colleges. I'm thinking of buying a new router, but as this is specific to just my one website I'm a bit iffy as it seems extreme.

share|improve this question

closed as off-topic by HopelessN00b Jan 14 '15 at 2:59

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions should demonstrate reasonable business information technology management practices. Questions that relate to unsupported hardware or software platforms or unmaintained environments may not be suitable for Server Fault - see the help center." – HopelessN00b
If this question can be reworded to fit the rules in the help center, please edit the question.

Is that server on the same network as the system you're trying to access it from? – Shane Madden Mar 28 '12 at 1:57
Does your home ISP filter anything port-wise? – jscott Mar 28 '12 at 2:08
Have you tried running nmap against your server from home/work and comparing the results? – Andrew Mar 28 '12 at 3:03

I would start by running tcpdump or wireshark (command line version of WireShark is tshark). These tools let you see the actual network packets on your server. Using that, you can see with certainty whether the packets from your other machine are making it to your server. If you see them, it's a problem with the server. If you don't see the traffic attempts from your other computer, the problem lies somewhere else.

share|improve this answer

Has the server itself blocked your home IP address? Have you checked its logs?

Assuming your home Internet connection has a dynamic IP address you could try rebooting the modem, which in most cases will also get you a new IP address, after which you could retry the connection.

share|improve this answer

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