[WEB4LIB] DSL Woes

[Richard Wiggins]

As Karen and another observed, it's 192.168.x.x, not 192.68.x.x, so unless a) DSL providers have done something bizarre and b) they did it with a typo, the theory seems unlikely.

If you can get some of the scattered reporters to do some testing with you, have them do a ping or a traceroute to your server from their PC.  This should not be hard to diagnose if you have one cooperative victim.
 
Without specifics as to the mode of failure, everything is speculative. 

/rich

On Fri, 11 January 2002, "Donald Barclay" wrote:

> 
> We have been getting scattered reports that DSL users cannot access our
> library webpages (www.library.tmc.edu). At first the reports came
> exclusively from users (including two of our librarians) of Southwestern
> Bell DSL, but today we got a report from someone using RoadRunner DSL. Does
> anyone know of any reason why webpages that are otherwise completely
> accessible cannot be accessed by users of DSL?
> 
> We tried to contact Southwestern Bell DSL about this problem, but they won't
> respond to their own customers, much less us.
> 
> One far-out thought we had was this: The numerical IP of our main webserver
> is 192.68.30.200. Numerical IPs that begin with 192.68.*.* can be used for
> private networks. Could the DSL providers be blocking IPs that start with
> "192.68" in the belief that they are protecting private networks?
> Interestingly, one of our DSL-using librarians reports that another website
> she cannot hit using DSL is www.sun.com, and the numerical address of this
> site begins with "192" (though the second part of the address is not "68").
> 
> Any ideas will be much appreciated.
> 
> Donald A. Barclay
> Assistant Director for Systems and Informatics
> Houston Academy of Medicine--
> Texas Medical Center Library
> dbarclay at library.tmc.edu
> 713.799.7120
> 
> always the beautiful answer
> who asks a more beautiful question
>                  --e.e. cummings

Richard Wiggins
Writing, Speaking, and Consulting on Internet Topics
rich at richardwiggins.com       www.richardwiggins.com