1

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.

pelms
  • 113
  • 4

1 Answers1

5

Addresses on the 2.0.0.0/8 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.

the-wabbit
  • 40,737
  • 13
  • 111
  • 174
  • 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