connection problems

[BJ_M]

as of the last 3 or so days -- i can not seem to connect to several CND websites like the www.thestar.com or www.mls.ca


google seems to indicate that they are up , but i just get timeouts --

ive tried to connect just using ip only and also lowered mtu and raised time out in firefox (also tried IE) ..

what the heck is it - or is it a global connection issue >

[honorarybrutha]

must be local issue. getting thru ok from California to both the sites.

[BJ_M]

crap o la

[BJ_M]

i switched to running through a proxy and it works -- really weird

[Soopafresh]

Traceroute back to yourself via http://network-tools.com/

Or, from your command prompt - Tracert www.mls.ca

The asterisks will indicate dropped packets and routers that are bad along the way.

[BJ_M]

ahh good idea -- didnt think of that

[BJ_M]

freaking bell issue -- way down the line

  3    63 ms    65 ms    64 ms  gateway.synapse.net [199.84.54.1]
  4    81 ms    76 ms    78 ms  g3-0.core02.jfk02.atlas.cogentco.com [38.112.15.45]
  5   106 ms   103 ms   104 ms  p14-0.core02.ord01.atlas.cogentco.com [66.28.4.86]
  6   103 ms   101 ms   271 ms  p15-0.core01.ord01.atlas.cogentco.com [66.28.4.61]
  7   104 ms   103 ms   105 ms  bellnexxia.ord01.atlas.cogentco.com [154.54.11.30]
  8   105 ms   103 ms   104 ms  core2-chicago23-pos0-3.in.bellnexxia.net [206.108.103.126]
  9   115 ms   114 ms   114 ms  core3-toronto63-pos6-3.in.bellnexxia.net [206.108.103.113]
 10   116 ms   114 ms   114 ms  core2-toronto63-pos0-1.in.bellnexxia.net [64.230.242.102]
 11   114 ms   115 ms   116 ms  dis33-toronto63-pos5-0.in.bellnexxia.net [64.230.229.10]
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.

[glockjs]

Traceroute back to yourself via http://network-tools.com/

Or, from your command prompt - Tracert www.mls.ca

The asterisks will indicate dropped packets and routers that are bad along the way.

nice tool

[glockjs]

5	1	1	2		64.1.2.85	p3-0-0.mar1.houston4-tx.us.xo.net
6	7	16	24		65.106.4.201	p4-1-0.rar1.dallas-tx.us.xo.net
7	31	32	31		65.106.0.33	p1-0-0.rar2.chicago-il.us.xo.net
8	32	32	31		65.106.6.138	p1-0.ir1.chicago2-il.us.xo.net
9	32	32	32		64.230.207.209	hse-montreal-ppp111262.qc.sympatico.ca
10	32	32	32		64.230.223.21	hse-sherbrooke-ppp98882.qc.sympatico.ca
11	43	43	43		206.108.103.113	core3-toronto63-pos6-3.in.bellnexxia.net
12	45	43	43		64.230.242.94	core1-toronto63-pos0-1.in.bellnexxia.net
13	43	43	44		64.230.229.6	dis33-toronto63-pos2-0.in.bellnexxia.net
14	44	45	44		204.225.95.130	fat.bt.onramp.ca
15	46	46	44		204.225.95.138	pinball.bf.onramp.ca
16	46	44	45		199.246.72.100	www.crow1.mls.ca

that's www.mls.ca

bell doesnt look too bad for me. ur proxy still up/

[BJ_M]

that was proxy down - with proxy up , it goes through ..

[glockjs]

i could be wrong but i think all a proxy does is act as your cache. so i'd start lookin there

[BJ_M]

no -- its not that,

tracert show a different path using proxy vs straight through ..


it is a box at bell with problems

others also report a problem at dslreports

[glockjs]

that's weird. my path hit some of the same bell server's without prob's. but yours kinda goes a different direction after that. stupid computers.

[BJ_M]

my path to here (videohelp) goes to newyork -> london -> back to usa

go figure

some weird routing going on ...

[fmctm1sw]

Very interesting tool. Mine took 16 jumps.

[BJ_M]

looks like a lot of people are having problems today

http://www.dslreports.com/forum/remark,12816126~root=ool~mode=flat