Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

One of my client website was not opening in saudi arabia but it was working in us,uk,india and many more places.

He was tried to open from different sources like office,pc,laptop,browsing cafe,mobile and so on but the website was not opening.

IP banned?

What is the problem? how to solve this?

How to check the website was working in any other places in saudi arabia?

share|improve this question

closed as off-topic by mdpc, dawud, Jenny D, Andrew B, Ward May 11 at 2:52

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

  • "Questions must be relevant to professional system administration. Server Fault is dedicated to professional system and network administrators. End user and enthusiast questions are off-topic (contact your system administrator or hire a professional to help you out). Please see the Help Center for more information." – mdpc, dawud, Jenny D, Ward
If this question can be reworded to fit the rules in the help center, please edit the question.

3 Answers 3

You can try to configure your web browser to navigate to the client's website through some web proxies of Saudi Arabia. There are lists of free proxies available in the Internet such as this.

Then you can confirm that you're accessing the website through a Saudi Arabian IP in here.

Just try some of the proxies of Saudi Arabia and check if the web site is or is not loaded after all.

share|improve this answer

Ask your client for a traceroute, that's probably the easiest way.

  1. If you see packets are lost quite early, i.e. within Saudi Arabia, your IP is blocked on their side.
  2. If you see it gets quite far, out of SA, then someone along the route is blocking it, and you need to talk to them. Ideally, it'll drop nearest to you, so it's probably your firewall (or some external one) doing the blocking.
share|improve this answer
    
Thanks for the idea. Let me check this and comment :) –  Ramkumar Sep 22 '12 at 17:32
    
assuming that some firewalls from governments and Providers dnt just block a basic IP but use there own kind of Proxy or IDS to monitor, track and filter the web, a simple traceroute could not work out as expectet. You Would always have to try something that talks http(s) to be sure. In fact, enableing (temprary/permanently) https on your server could solve the problem. –  Daywalker Oct 4 '13 at 17:37

There could be many reasons for this. It could be a routing issue, but this is not very likely. It could also be blocked by something.

You should run a traceroute from the client machine that can't access your site to your site. On windows, this command is tracert <ip>; on linux it is traceroute <ip>.

Keep in mind that connectivity essentially fails between hosts. So, unless you get a reply saying something like "ICMP network administratively prohibited", you won't likely get to know who is blocking it; just the last forwarder before the packet got tossed and the trail went cold.

Keep in mind also that when talking to the admin of the last router (which you can find by looking up its IP address in whois, and contacting the technical contact for the most specific result) that you don't pay them (unless it's your ISP); their main interest is likely making sure their network is fully routed, not helping you out.

You could also potentially do a traceroute from your server to various nodes in Saudi Arabia that can't access your site (make sure they aren't filtering ICMP replies via windows firewall or similar, and make sure they have an internet-routeable IP), and see if it breaks down at the same or a similar point each time.

share|improve this answer

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