• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

SBC DSL connection seems to hate eBay

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

Admiral Falcon

Jun 23, 2002
I'm using SBC/Yahoo's DSL service, and I've been using it for a year. Everything was fine until approximately two months ago. Now, whenever I attempt to use ebay, I get a strange problem. It'll work fine until a large page comes up, one that takes a long time to load and/or has pictures stored externally on a bunch of different servers. Then the Internet breaks, from my perspective. Any attempt to access any website is met with a perpetual "resolving host..." status. Trying to login to my router doesn't work at all. I have to unplug the power from the router and re-plug it back in to force a new connection.

The modem is by SpeedStream, don't know which model. The router is a Netgear RP614v2. There are two computers connected to the router, and no changes were made to either of them when this started happening.

The problem is definitely with SBC's service or with the modem -- bypassing the router and directly plugging the DSL modem into the computer produces the same problem.

Does anybody else know what may be causing this?


May 7, 2003
First off I would open a command prompt. Type in "tracert ebay.com" without the quotes. That will give you a nice chart with response times of the routers and servers that you go through to get to ebay's server. Your looking for timeouts and large numbers in the ms column.

Right now I seem to get a timeout after ge-9-1.pcolo2.sanjose1.level13.net.

I'm shure someone can tell you what the problem is once you post the tracert chart. May or may not be able to fix it. :burn:

Admiral Falcon

Jun 23, 2002
Here's the tracert chart:

C:\WINDOWS>tracert ebay.com

Tracing route to ebay.com []
over a maximum of 30 hops:

  1   <10 ms   <10 ms   <10 ms
  2    13 ms    14 ms    14 ms  adsl-68-74-127-254.dsl.emhril.ameritech.net [68.
  3    14 ms    13 ms    14 ms  dist2-vlan50.emhril.ameritech.net []

  4    14 ms    13 ms    14 ms  bb2-g1-0-1.emhril.ameritech.net []
  5    14 ms    27 ms    14 ms  ex2-p6-3.eqchil.sbcglobal.net []
  6    13 ms    14 ms    14 ms  asn2828-xo.eqchil.sbcglobal.net [
  7    27 ms    14 ms    13 ms  p5-0-0.RAR1.Chicago-IL.us.xo.net []

  8    41 ms    41 ms    55 ms  p6-0-0.RAR2.Denver-CO.us.xo.net []
  9    41 ms    41 ms    41 ms  p0-0-0d0.RAR1.Denver-CO.us.xo.net []

 10    69 ms    82 ms    69 ms  p6-0-0.RAR1.SanJose-CA.us.xo.net []
 11    69 ms    82 ms    69 ms  p0-0-0.MAR1.Fremont-CA.us.xo.net []

 12    69 ms    68 ms    69 ms  p0-0.CHR1.Fremont-CA.us.xo.net []
 13     *        *        *     Request timed out.

EDIT: The last line repeats itself until the maximum number of hops is reached.

Here's an example of a page that triggers the problem:

Last edited: