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

Some of our users are unable to connect to one particular web server (our library catalogue), getting an "Oops! Google Chrome could not connect to..." type message across all browsers. The only thing they seem to have in common is that their IP addresses are all in the range 2.x.x.x or 90.x.x.x from the same ISP.

I vaguely recall the 2.x range having some historical significance but can't find any reference to it.

share|improve this question
the 2. range was only assigned in 2009, so it may be you remember it not being so. – Sirex Feb 28 '12 at 12:23
up vote 5 down vote accepted

Addresses on the network used to be so-called Bogons / Fullbogons. The network is not on the current Fullbogon list any more and has been assigned to RIPE, so its addresses are valid nowadays, but some admins might still use obsolete data for filtering, thus your trouble.

Check with the network admin responsible for the connectivity of your library catalogue, he should be either able to help directly or escalate it upstream.

share|improve this answer
Thanks syneticon-dj. We can't find any sign of filtering going on and there were other instances of 2.x.x.x IP addresses in the access logs so looks like I'll have to keep looking. You answered the question though :¬) – pelms Feb 28 '12 at 13:59

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.