www.qnx.com nearly unreachable ....

Hi,

here are 2 traces from 2 different locations.
The bottleneck seems to be the ‘router.qnx.com

Are there any plans to solve that problem ???

Armin


UCI Traceroute

Traceroute from: weather.nts.uci.edu to www.qnx.com

1 cpl-cdl-rsm1-vl083 (128.200.83.1) 1 ms 1 ms 1 ms
2 cpl-8510-vl401 (128.195.249.1) 2 ms 2 ms 2 ms
3 durin-gw-vl425 (128.195.249.126) 1 ms 1 ms 1 ms
4 c2-uci-gsr-pos0-1.calren2.net (128.200.240.11) 1 ms 1 ms 1 ms
5 UCR--UCI.POS.calren2.net (198.32.248.13) 2 ms 2 ms 2 ms
6 CIT--UCR.POS.calren2.net (198.32.248.9) 4 ms 4 ms 4 ms
7 JPL--CIT.POS.calren2.net (198.32.248.5) 4 ms 4 ms 4 ms
8 UCLA--JPL.POS.calren2.net (198.32.248.1) 5 ms 5 ms 5 ms
9 UCLA-7507--UCLA.POS.calren2.net (198.32.248.118) 5 ms 5 ms
5ms
10 corerouter2-serial6-0-0-0.Bloomington.cw.net (166.63.131.129)
11 ms 8 ms 7 ms
11 acr2-loopback.Anaheim.cw.net (208.172.34.62) 11 ms 11 ms 11
ms
12 acr2-loopback.Chicagochd.cw.net (208.172.2.62) 64 ms 64 ms 65
ms
13 bell-nexxia.Chicagochd.cw.net (208.172.1.206) 61 ms 61 ms 61
ms
14 core2-chicago23-pos10-0.in.bellnexxia.net (206.108.103.121) 61
ms 62 ms 62 ms
15 core1-toronto12-pos3-0.in.bellnexxia.net (206.108.103.117) 73
ms 73 ms 74 ms
16 core1-ottawa23-pos5-0.in.bellnexxia.net (206.108.107.110) 79
ms 79 ms 78 ms
17 ottdisr01-pos1-1-0.in.bellnexxia.net (206.108.99.154) 267 ms
281 ms 236 ms
18 router.qnx.com (209.226.137.126) 80 ms 81 ms 80 ms
19 * * *
20 * * *
21 * * *



Starting trace … (from Germany )
Tracing to www.qnx.com [209.226.137.53]…
Hops IP Address RTT(ms) DNS Name
1 192.168.0.250 3
2 62.225.253.105 34
3 212.185.254.246 35
4 62.154.10.184 36 KO-EB1.KO.DE.net.dtag.de
5 194.25.6.110 164 NYC-gw12.USA.net.DTAG.DE
6 144.223.25.1 162 sl-gw28-nyc-8-0.sprintlink.net
7 TIMED OUT
8 144.232.7.101 163 sl-bb20-nyc-15-0-2480M.sprintlink.net
9 144.232.7.106 164 sl-bb21-nyc-14-0-2480M.sprintlink.net
10 144.232.7.98 197 sl-gw9-nyc-9-0.sprintlink.net
11 160.81.43.14 163 sl-Nexxia-2-0-0.sprintlink.net
12 206.108.103.189 164 Ncore2-newyork83-pos9-0.in.bellnexxia.net
13 206.108.103.213 173 core1-montreal02-pos4-0.in.bellnexxia.net
14 TIMED OUT
15 206.108.99.150 214 ottdisr01-pos1-0-0.in.bellnexxia.net
16 209.226.137.126 215 router.qnx.com
17 TIMED OUT
18 TIMED OUT
19 TIMED OUT
20 TIMED OUT
21 TIMED OUT
22 TIMED OUT
23 TIMED OUT

Armin,

I can reach www/quics/qdn/news just fine. What problem are
you running into?

Most corporate routers these days don’t allow ‘traceroute’ to
go past them - some don’t even allow pings.

Jay

Armin Steinhoff wrote in message <3B23B42B.64D4A264@web_.de>…

Hi,

here are 2 traces from 2 different locations.
The bottleneck seems to be the ‘router.qnx.com

Are there any plans to solve that problem ???

Armin


UCI Traceroute

Traceroute from: weather.nts.uci.edu to > www.qnx.com

1 cpl-cdl-rsm1-vl083 (128.200.83.1) 1 ms 1 ms 1 ms
2 cpl-8510-vl401 (128.195.249.1) 2 ms 2 ms 2 ms
3 durin-gw-vl425 (128.195.249.126) 1 ms 1 ms 1 ms
4 c2-uci-gsr-pos0-1.calren2.net (128.200.240.11) 1 ms 1 ms 1 ms
5 UCR--UCI.POS.calren2.net (198.32.248.13) 2 ms 2 ms 2 ms
6 CIT--UCR.POS.calren2.net (198.32.248.9) 4 ms 4 ms 4 ms
7 JPL--CIT.POS.calren2.net (198.32.248.5) 4 ms 4 ms 4 ms
8 UCLA--JPL.POS.calren2.net (198.32.248.1) 5 ms 5 ms 5 ms
9 UCLA-7507--UCLA.POS.calren2.net (198.32.248.118) 5 ms 5 ms
5ms
10 corerouter2-serial6-0-0-0.Bloomington.cw.net (166.63.131.129)
11 ms 8 ms 7 ms
11 acr2-loopback.Anaheim.cw.net (208.172.34.62) 11 ms 11 ms 11
ms
12 acr2-loopback.Chicagochd.cw.net (208.172.2.62) 64 ms 64 ms 65
ms
13 bell-nexxia.Chicagochd.cw.net (208.172.1.206) 61 ms 61 ms 61
ms
14 core2-chicago23-pos10-0.in.bellnexxia.net (206.108.103.121) 61
ms 62 ms 62 ms
15 core1-toronto12-pos3-0.in.bellnexxia.net (206.108.103.117) 73
ms 73 ms 74 ms
16 core1-ottawa23-pos5-0.in.bellnexxia.net (206.108.107.110) 79
ms 79 ms 78 ms
17 ottdisr01-pos1-1-0.in.bellnexxia.net (206.108.99.154) 267 ms
281 ms 236 ms
18 router.qnx.com (209.226.137.126) 80 ms 81 ms 80 ms
19 * * *
20 * * *
21 * * *



Starting trace … (from Germany )
Tracing to > www.qnx.com > [209.226.137.53]…
Hops IP Address RTT(ms) DNS Name
1 192.168.0.250 3
2 62.225.253.105 34
3 212.185.254.246 35
4 62.154.10.184 36 KO-EB1.KO.DE.net.dtag.de
5 194.25.6.110 164 NYC-gw12.USA.net.DTAG.DE
6 144.223.25.1 162 sl-gw28-nyc-8-0.sprintlink.net
7 TIMED OUT
8 144.232.7.101 163 sl-bb20-nyc-15-0-2480M.sprintlink.net
9 144.232.7.106 164 sl-bb21-nyc-14-0-2480M.sprintlink.net
10 144.232.7.98 197 sl-gw9-nyc-9-0.sprintlink.net
11 160.81.43.14 163 sl-Nexxia-2-0-0.sprintlink.net
12 206.108.103.189 164 Ncore2-newyork83-pos9-0.in.bellnexxia.net
13 206.108.103.213 173 core1-montreal02-pos4-0.in.bellnexxia.net
14 TIMED OUT
15 206.108.99.150 214 ottdisr01-pos1-0-0.in.bellnexxia.net
16 209.226.137.126 215 router.qnx.com
17 TIMED OUT
18 TIMED OUT
19 TIMED OUT
20 TIMED OUT
21 TIMED OUT
22 TIMED OUT
23 TIMED OUT

-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 80,000 Newsgroups - 16 Different Servers! =-----

I have been experiencing very slow response as well from inn.qnx.com and
quics. A download of some recently updated
documentation showed a transfer rate of ~300 bytes per second. We have a
T1 pipe to the world and 100 MHz Ethernet
internally.

David McMillan
Oak Ridge National Laboratory

Original Message

On 6/10/2001, 3:39:56 PM, “Jay Hogg” <jh@fastlane.net.r-e-m-o-v-e> wrote
regarding Re: www.qnx.com nearly unreachable …:


Armin,

I can reach www/quics/qdn/news just fine. What problem are
you running into?

Most corporate routers these days don’t allow ‘traceroute’ to
go past them - some don’t even allow pings.

Jay

Armin Steinhoff wrote in message <3B23B42B.64D4A264@web_.de>…

Hi,

here are 2 traces from 2 different locations.
The bottleneck seems to be the ‘router.qnx.com

Are there any plans to solve that problem ???

Armin


UCI Traceroute

Traceroute from: weather.nts.uci.edu to > www.qnx.com

1 cpl-cdl-rsm1-vl083 (128.200.83.1) 1 ms 1 ms 1 ms
2 cpl-8510-vl401 (128.195.249.1) 2 ms 2 ms 2 ms
3 durin-gw-vl425 (128.195.249.126) 1 ms 1 ms 1 ms
4 c2-uci-gsr-pos0-1.calren2.net (128.200.240.11) 1 ms 1 ms 1 ms
5 UCR--UCI.POS.calren2.net (198.32.248.13) 2 ms 2 ms 2 ms
6 CIT--UCR.POS.calren2.net (198.32.248.9) 4 ms 4 ms 4 ms
7 JPL--CIT.POS.calren2.net (198.32.248.5) 4 ms 4 ms 4 ms
8 UCLA--JPL.POS.calren2.net (198.32.248.1) 5 ms 5 ms 5 ms
9 UCLA-7507--UCLA.POS.calren2.net (198.32.248.118) 5 ms 5 ms
5ms
10 corerouter2-serial6-0-0-0.Bloomington.cw.net (166.63.131.129)
11 ms 8 ms 7 ms
11 acr2-loopback.Anaheim.cw.net (208.172.34.62) 11 ms 11 ms 11
ms
12 acr2-loopback.Chicagochd.cw.net (208.172.2.62) 64 ms 64 ms 65
ms
13 bell-nexxia.Chicagochd.cw.net (208.172.1.206) 61 ms 61 ms 61
ms
14 core2-chicago23-pos10-0.in.bellnexxia.net (206.108.103.121) 61
ms 62 ms 62 ms
15 core1-toronto12-pos3-0.in.bellnexxia.net (206.108.103.117) 73
ms 73 ms 74 ms
16 core1-ottawa23-pos5-0.in.bellnexxia.net (206.108.107.110) 79
ms 79 ms 78 ms
17 ottdisr01-pos1-1-0.in.bellnexxia.net (206.108.99.154) 267 ms
281 ms 236 ms
18 router.qnx.com (209.226.137.126) 80 ms 81 ms 80 ms
19 * * *
20 * * *
21 * * *



Starting trace … (from Germany )
Tracing to > www.qnx.com > [209.226.137.53]…
Hops IP Address RTT(ms) DNS Name
1 192.168.0.250 3
2 62.225.253.105 34
3 212.185.254.246 35
4 62.154.10.184 36 KO-EB1.KO.DE.net.dtag.de
5 194.25.6.110 164 NYC-gw12.USA.net.DTAG.DE
6 144.223.25.1 162 sl-gw28-nyc-8-0.sprintlink.net
7 TIMED OUT
8 144.232.7.101 163 sl-bb20-nyc-15-0-2480M.sprintlink.net
9 144.232.7.106 164 sl-bb21-nyc-14-0-2480M.sprintlink.net
10 144.232.7.98 197 sl-gw9-nyc-9-0.sprintlink.net
11 160.81.43.14 163 sl-Nexxia-2-0-0.sprintlink.net
12 206.108.103.189 164 Ncore2-newyork83-pos9-0.in.bellnexxia.net
13 206.108.103.213 173 core1-montreal02-pos4-0.in.bellnexxia.net
14 TIMED OUT
15 206.108.99.150 214 ottdisr01-pos1-0-0.in.bellnexxia.net
16 209.226.137.126 215 router.qnx.com
17 TIMED OUT
18 TIMED OUT
19 TIMED OUT
20 TIMED OUT
21 TIMED OUT
22 TIMED OUT
23 TIMED OUT



-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com > - The #1 Newsgroup Service in the World!
-----== Over 80,000 Newsgroups - 16 Different Servers! =-----

From Michigan, we are experiencing normal speed to inn.qnx.com. Hope that
info helps.

David McMillan wrote:

I have been experiencing very slow response as well from inn.qnx.com and
quics. A download of some recently updated
documentation showed a transfer rate of ~300 bytes per second. We have a
T1 pipe to the world and 100 MHz Ethernet
internally.

David McMillan
Oak Ridge National Laboratory

Original Message

On 6/10/2001, 3:39:56 PM, “Jay Hogg” <> jh@fastlane.net.r-e-m-o-v-e> > wrote
regarding Re: > www.qnx.com > nearly unreachable …:

Armin,

I can reach www/quics/qdn/news just fine. What problem are
you running into?

Most corporate routers these days don’t allow ‘traceroute’ to
go past them - some don’t even allow pings.

Jay

Armin Steinhoff wrote in message <3B23B42B.64D4A264@web_.de>…

Hi,

here are 2 traces from 2 different locations.
The bottleneck seems to be the ‘router.qnx.com

Are there any plans to solve that problem ???

Armin


UCI Traceroute

Traceroute from: weather.nts.uci.edu to > www.qnx.com

1 cpl-cdl-rsm1-vl083 (128.200.83.1) 1 ms 1 ms 1 ms
2 cpl-8510-vl401 (128.195.249.1) 2 ms 2 ms 2 ms
3 durin-gw-vl425 (128.195.249.126) 1 ms 1 ms 1 ms
4 c2-uci-gsr-pos0-1.calren2.net (128.200.240.11) 1 ms 1 ms 1 ms
5 UCR--UCI.POS.calren2.net (198.32.248.13) 2 ms 2 ms 2 ms
6 CIT--UCR.POS.calren2.net (198.32.248.9) 4 ms 4 ms 4 ms
7 JPL--CIT.POS.calren2.net (198.32.248.5) 4 ms 4 ms 4 ms
8 UCLA--JPL.POS.calren2.net (198.32.248.1) 5 ms 5 ms 5 ms
9 UCLA-7507--UCLA.POS.calren2.net (198.32.248.118) 5 ms 5 ms
5ms
10 corerouter2-serial6-0-0-0.Bloomington.cw.net (166.63.131.129)
11 ms 8 ms 7 ms
11 acr2-loopback.Anaheim.cw.net (208.172.34.62) 11 ms 11 ms 11
ms
12 acr2-loopback.Chicagochd.cw.net (208.172.2.62) 64 ms 64 ms 65
ms
13 bell-nexxia.Chicagochd.cw.net (208.172.1.206) 61 ms 61 ms 61
ms
14 core2-chicago23-pos10-0.in.bellnexxia.net (206.108.103.121) 61
ms 62 ms 62 ms
15 core1-toronto12-pos3-0.in.bellnexxia.net (206.108.103.117) 73
ms 73 ms 74 ms
16 core1-ottawa23-pos5-0.in.bellnexxia.net (206.108.107.110) 79
ms 79 ms 78 ms
17 ottdisr01-pos1-1-0.in.bellnexxia.net (206.108.99.154) 267 ms
281 ms 236 ms
18 router.qnx.com (209.226.137.126) 80 ms 81 ms 80 ms
19 * * *
20 * * *
21 * * *



Starting trace … (from Germany )
Tracing to > www.qnx.com > [209.226.137.53]…
Hops IP Address RTT(ms) DNS Name
1 192.168.0.250 3
2 62.225.253.105 34
3 212.185.254.246 35
4 62.154.10.184 36 KO-EB1.KO.DE.net.dtag.de
5 194.25.6.110 164 NYC-gw12.USA.net.DTAG.DE
6 144.223.25.1 162 sl-gw28-nyc-8-0.sprintlink.net
7 TIMED OUT
8 144.232.7.101 163 sl-bb20-nyc-15-0-2480M.sprintlink.net
9 144.232.7.106 164 sl-bb21-nyc-14-0-2480M.sprintlink.net
10 144.232.7.98 197 sl-gw9-nyc-9-0.sprintlink.net
11 160.81.43.14 163 sl-Nexxia-2-0-0.sprintlink.net
12 206.108.103.189 164 Ncore2-newyork83-pos9-0.in.bellnexxia.net
13 206.108.103.213 173 core1-montreal02-pos4-0.in.bellnexxia.net
14 TIMED OUT
15 206.108.99.150 214 ottdisr01-pos1-0-0.in.bellnexxia.net
16 209.226.137.126 215 router.qnx.com
17 TIMED OUT
18 TIMED OUT
19 TIMED OUT
20 TIMED OUT
21 TIMED OUT
22 TIMED OUT
23 TIMED OUT

-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com > - The #1 Newsgroup Service in the World!
-----== Over 80,000 Newsgroups - 16 Different Servers! =-----

In article <3B2503E1.6CD6C584@faac.com>, Dean says…

From Michigan, we are experiencing normal speed to inn.qnx.com. Hope that
info helps.

Could you proide a traceroute output at a normal working time??

Armin


David McMillan wrote:

I have been experiencing very slow response as well from inn.qnx.com and
quics. A download of some recently updated
documentation showed a transfer rate of ~300 bytes per second. We have a
T1 pipe to the world and 100 MHz Ethernet
internally.

David McMillan
Oak Ridge National Laboratory

Original Message

On 6/10/2001, 3:39:56 PM, “Jay Hogg” <> jh@fastlane.net.r-e-m-o-v-e> > wrote
regarding Re: > www.qnx.com > nearly unreachable …:

Armin,

I can reach www/quics/qdn/news just fine. What problem are
you running into?

Most corporate routers these days don’t allow ‘traceroute’ to
go past them - some don’t even allow pings.

Jay

Armin Steinhoff wrote in message <3B23B42B.64D4A264@web_.de>…

Hi,

here are 2 traces from 2 different locations.
The bottleneck seems to be the ‘router.qnx.com

Are there any plans to solve that problem ???

Armin


UCI Traceroute

Traceroute from: weather.nts.uci.edu to > www.qnx.com

1 cpl-cdl-rsm1-vl083 (128.200.83.1) 1 ms 1 ms 1 ms
2 cpl-8510-vl401 (128.195.249.1) 2 ms 2 ms 2 ms
3 durin-gw-vl425 (128.195.249.126) 1 ms 1 ms 1 ms
4 c2-uci-gsr-pos0-1.calren2.net (128.200.240.11) 1 ms 1 ms 1 ms
5 UCR--UCI.POS.calren2.net (198.32.248.13) 2 ms 2 ms 2 ms
6 CIT--UCR.POS.calren2.net (198.32.248.9) 4 ms 4 ms 4 ms
7 JPL--CIT.POS.calren2.net (198.32.248.5) 4 ms 4 ms 4 ms
8 UCLA--JPL.POS.calren2.net (198.32.248.1) 5 ms 5 ms 5 ms
9 UCLA-7507--UCLA.POS.calren2.net (198.32.248.118) 5 ms 5 ms
5ms
10 corerouter2-serial6-0-0-0.Bloomington.cw.net (166.63.131.129)
11 ms 8 ms 7 ms
11 acr2-loopback.Anaheim.cw.net (208.172.34.62) 11 ms 11 ms 11
ms
12 acr2-loopback.Chicagochd.cw.net (208.172.2.62) 64 ms 64 ms 65
ms
13 bell-nexxia.Chicagochd.cw.net (208.172.1.206) 61 ms 61 ms 61
ms
14 core2-chicago23-pos10-0.in.bellnexxia.net (206.108.103.121) 61
ms 62 ms 62 ms
15 core1-toronto12-pos3-0.in.bellnexxia.net (206.108.103.117) 73
ms 73 ms 74 ms
16 core1-ottawa23-pos5-0.in.bellnexxia.net (206.108.107.110) 79
ms 79 ms 78 ms
17 ottdisr01-pos1-1-0.in.bellnexxia.net (206.108.99.154) 267 ms
281 ms 236 ms
18 router.qnx.com (209.226.137.126) 80 ms 81 ms 80 ms
19 * * *
20 * * *
21 * * *



Starting trace … (from Germany )
Tracing to > www.qnx.com > [209.226.137.53]…
Hops IP Address RTT(ms) DNS Name
1 192.168.0.250 3
2 62.225.253.105 34
3 212.185.254.246 35
4 62.154.10.184 36 KO-EB1.KO.DE.net.dtag.de
5 194.25.6.110 164 NYC-gw12.USA.net.DTAG.DE
6 144.223.25.1 162 sl-gw28-nyc-8-0.sprintlink.net
7 TIMED OUT
8 144.232.7.101 163 sl-bb20-nyc-15-0-2480M.sprintlink.net
9 144.232.7.106 164 sl-bb21-nyc-14-0-2480M.sprintlink.net
10 144.232.7.98 197 sl-gw9-nyc-9-0.sprintlink.net
11 160.81.43.14 163 sl-Nexxia-2-0-0.sprintlink.net
12 206.108.103.189 164 Ncore2-newyork83-pos9-0.in.bellnexxia.net
13 206.108.103.213 173 core1-montreal02-pos4-0.in.bellnexxia.net
14 TIMED OUT
15 206.108.99.150 214 ottdisr01-pos1-0-0.in.bellnexxia.net
16 209.226.137.126 215 router.qnx.com
17 TIMED OUT
18 TIMED OUT
19 TIMED OUT
20 TIMED OUT
21 TIMED OUT
22 TIMED OUT
23 TIMED OUT

-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com > - The #1 Newsgroup Service in the World!
-----== Over 80,000 Newsgroups - 16 Different Servers! =-----

Attached

Armin Steinhoff wrote:

In article <> 3B2503E1.6CD6C584@faac.com> >, Dean says…

From Michigan, we are experiencing normal speed to inn.qnx.com. Hope that
info helps.

Could you proide a traceroute output at a normal working time??

Armin


David McMillan wrote:

I have been experiencing very slow response as well from inn.qnx.com and
quics. A download of some recently updated
documentation showed a transfer rate of ~300 bytes per second. We have a
T1 pipe to the world and 100 MHz Ethernet
internally.

David McMillan
Oak Ridge National Laboratory

Original Message

On 6/10/2001, 3:39:56 PM, “Jay Hogg” <> jh@fastlane.net.r-e-m-o-v-e> > wrote
regarding Re: > www.qnx.com > nearly unreachable …:

Armin,

I can reach www/quics/qdn/news just fine. What problem are
you running into?

Most corporate routers these days don’t allow ‘traceroute’ to
go past them - some don’t even allow pings.

Jay

Armin Steinhoff wrote in message <3B23B42B.64D4A264@web_.de>…

Hi,

here are 2 traces from 2 different locations.
The bottleneck seems to be the ‘router.qnx.com

Are there any plans to solve that problem ???

Armin


UCI Traceroute

Traceroute from: weather.nts.uci.edu to > www.qnx.com

1 cpl-cdl-rsm1-vl083 (128.200.83.1) 1 ms 1 ms 1 ms
2 cpl-8510-vl401 (128.195.249.1) 2 ms 2 ms 2 ms
3 durin-gw-vl425 (128.195.249.126) 1 ms 1 ms 1 ms
4 c2-uci-gsr-pos0-1.calren2.net (128.200.240.11) 1 ms 1 ms 1 ms
5 UCR--UCI.POS.calren2.net (198.32.248.13) 2 ms 2 ms 2 ms
6 CIT--UCR.POS.calren2.net (198.32.248.9) 4 ms 4 ms 4 ms
7 JPL--CIT.POS.calren2.net (198.32.248.5) 4 ms 4 ms 4 ms
8 UCLA--JPL.POS.calren2.net (198.32.248.1) 5 ms 5 ms 5 ms
9 UCLA-7507--UCLA.POS.calren2.net (198.32.248.118) 5 ms 5 ms
5ms
10 corerouter2-serial6-0-0-0.Bloomington.cw.net (166.63.131.129)
11 ms 8 ms 7 ms
11 acr2-loopback.Anaheim.cw.net (208.172.34.62) 11 ms 11 ms 11
ms
12 acr2-loopback.Chicagochd.cw.net (208.172.2.62) 64 ms 64 ms 65
ms
13 bell-nexxia.Chicagochd.cw.net (208.172.1.206) 61 ms 61 ms 61
ms
14 core2-chicago23-pos10-0.in.bellnexxia.net (206.108.103.121) 61
ms 62 ms 62 ms
15 core1-toronto12-pos3-0.in.bellnexxia.net (206.108.103.117) 73
ms 73 ms 74 ms
16 core1-ottawa23-pos5-0.in.bellnexxia.net (206.108.107.110) 79
ms 79 ms 78 ms
17 ottdisr01-pos1-1-0.in.bellnexxia.net (206.108.99.154) 267 ms
281 ms 236 ms
18 router.qnx.com (209.226.137.126) 80 ms 81 ms 80 ms
19 * * *
20 * * *
21 * * *



Starting trace … (from Germany )
Tracing to > www.qnx.com > [209.226.137.53]…
Hops IP Address RTT(ms) DNS Name
1 192.168.0.250 3
2 62.225.253.105 34
3 212.185.254.246 35
4 62.154.10.184 36 KO-EB1.KO.DE.net.dtag.de
5 194.25.6.110 164 NYC-gw12.USA.net.DTAG.DE
6 144.223.25.1 162 sl-gw28-nyc-8-0.sprintlink.net
7 TIMED OUT
8 144.232.7.101 163 sl-bb20-nyc-15-0-2480M.sprintlink.net
9 144.232.7.106 164 sl-bb21-nyc-14-0-2480M.sprintlink.net
10 144.232.7.98 197 sl-gw9-nyc-9-0.sprintlink.net
11 160.81.43.14 163 sl-Nexxia-2-0-0.sprintlink.net
12 206.108.103.189 164 Ncore2-newyork83-pos9-0.in.bellnexxia.net
13 206.108.103.213 173 core1-montreal02-pos4-0.in.bellnexxia.net
14 TIMED OUT
15 206.108.99.150 214 ottdisr01-pos1-0-0.in.bellnexxia.net
16 209.226.137.126 215 router.qnx.com
17 TIMED OUT
18 TIMED OUT
19 TIMED OUT
20 TIMED OUT
21 TIMED OUT
22 TIMED OUT
23 TIMED OUT

-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com > - The #1 Newsgroup Service in the World!
-----== Over 80,000 Newsgroups - 16 Different Servers! =-----

“Armin Steinhoff” <A-Steinhoff@web_.de> wrote in message
news:3B23B42B.64D4A264@web_.de…

Hi,

here are 2 traces from 2 different locations.
The bottleneck seems to be the ‘router.qnx.com

Are there any plans to solve that problem ???

Armin

if you cannot ping/traceroute www.qnx.com (209.226.137.53) it dosn’t meat
that this server is down. it means only that it dosn’t respond on ICMP
[echo] requests or some hop on the way filters ICMP trafic. my guess is that
this hope is router.qnx.com (209.226.137.126). on the other hand in order to
access www services you don’t need to ping target host. just try “#telnet
www.qnx.com 80” and type smth like “get index.html” html page with error
message 400 should be returned.

another thing are inn.qnx.com or quics.qnx.com which aren’t protected by
router/or configured to answer on external ICMP echo packets:


Tracing route to inn.qnx.com [209.226.137.7]
over a maximum of 30 hops:

1 <10 ms <10 ms <10 ms fw.nd.novosoft.ru [192.168.1.1]
2 <10 ms <10 ms <10 ms c2621-n-100m.novosoft.ru [194.149.224.1]
3 <10 ms <10 ms 10 ms cisco-external.novosoft.ru [194.149.224.66]
4 <10 ms 10 ms 10 ms c1720-tcms8.novosoft.ru [194.149.224.69]
5 20 ms 10 ms 10 ms tcms8-4.risp.ru [192.188.187.161]
6 <10 ms 10 ms <10 ms tcms8-5.risp.ru [212.164.0.101]
7 10 ms 10 ms 10 ms bb-fddi1-0-100m.novosibirsk.rostelecom.ru
[213.59.1.9]
8 20 ms 20 ms 20 ms bb-pos2-0-155m.ekaterinburg.rostelecom.ru
[213.24.141.205]
9 100 ms 51 ms 50 ms bb-pos1-0-0-155m.moscow.rostelecom.ru
[213.59.1.97]
10 40 ms 50 ms 40 ms gsr-pos1-0-155m.moscow.rostelecom.ru
[195.161.2.113]
11 40 ms 40 ms 50 ms bgw-giga6-0-0.moscow.rostelecom.ru
[195.161.0.1]
12 160 ms 161 ms 160 ms bgw-ser0-1-0.newyork.rostelecom.ru
[195.161.161.162]
13 180 ms 161 ms 170 ms if-10-1-0.bb6.newyork.teleglobe.net
[207.45.205.41]
14 161 ms 160 ms 170 ms if-0-0.bb8.NewYork.Teleglobe.net
[207.45.221.77]
15 170 ms 181 ms * if-1-0.core1.Toronto3.Teleglobe.net
[207.45.220.54]
16 191 ms 170 ms 180 ms ix-8-0.core1.Toronto3.Teleglobe.net
[216.6.0.146]
17 181 ms 190 ms 180 ms core1-toronto12-pos10-2.in.bellnexxia.net
[206.108.107.229]
18 171 ms 180 ms 190 ms core1-ottawa23-pos5-0.in.bellnexxia.net
[206.108.107.110]
19 181 ms 190 ms 180 ms ottdisr01-pos1-1-0.in.bellnexxia.net
[206.108.99.154]
20 180 ms 180 ms 190 ms router.qnx.com [209.226.137.126]
21 * 200 ms 180 ms inn.qnx.com [209.226.137.7]

Trace complete.


180ms seems to be more than enough for news reading purposes :slight_smile:

// wbr

Hi,
try to use the “multiproxy” - server with the option “next fastest available
server” marked, instead of a direct connect. It seems to work around our
connection problem from germany. I get about 30 KB instead of less than 1 KB
(using no proxy at all) on the iso-download …
And accessing qnx.com and qdn works fine as well .

ie


“Armin Steinhoff” <A-Steinhoff@web_.de> schrieb im Newsbeitrag
news:3B23B42B.64D4A264@web_.de…

Hi,

here are 2 traces from 2 different locations.
The bottleneck seems to be the ‘router.qnx.com

Are there any plans to solve that problem ???

Armin


UCI Traceroute

Traceroute from: weather.nts.uci.edu to > www.qnx.com

1 cpl-cdl-rsm1-vl083 (128.200.83.1) 1 ms 1 ms 1 ms
2 cpl-8510-vl401 (128.195.249.1) 2 ms 2 ms 2 ms
3 durin-gw-vl425 (128.195.249.126) 1 ms 1 ms 1 ms
4 c2-uci-gsr-pos0-1.calren2.net (128.200.240.11) 1 ms 1 ms 1 ms
5 UCR--UCI.POS.calren2.net (198.32.248.13) 2 ms 2 ms 2 ms
6 CIT--UCR.POS.calren2.net (198.32.248.9) 4 ms 4 ms 4 ms
7 JPL--CIT.POS.calren2.net (198.32.248.5) 4 ms 4 ms 4 ms
8 UCLA--JPL.POS.calren2.net (198.32.248.1) 5 ms 5 ms 5 ms
9 UCLA-7507--UCLA.POS.calren2.net (198.32.248.118) 5 ms 5 ms
5ms
10 corerouter2-serial6-0-0-0.Bloomington.cw.net (166.63.131.129)
11 ms 8 ms 7 ms
11 acr2-loopback.Anaheim.cw.net (208.172.34.62) 11 ms 11 ms 11
ms
12 acr2-loopback.Chicagochd.cw.net (208.172.2.62) 64 ms 64 ms 65
ms
13 bell-nexxia.Chicagochd.cw.net (208.172.1.206) 61 ms 61 ms 61
ms
14 core2-chicago23-pos10-0.in.bellnexxia.net (206.108.103.121) 61
ms 62 ms 62 ms
15 core1-toronto12-pos3-0.in.bellnexxia.net (206.108.103.117) 73
ms 73 ms 74 ms
16 core1-ottawa23-pos5-0.in.bellnexxia.net (206.108.107.110) 79
ms 79 ms 78 ms
17 ottdisr01-pos1-1-0.in.bellnexxia.net (206.108.99.154) 267 ms
281 ms 236 ms
18 router.qnx.com (209.226.137.126) 80 ms 81 ms 80 ms
19 * * *
20 * * *
21 * * *



Starting trace … (from Germany )
Tracing to > www.qnx.com > [209.226.137.53]…
Hops IP Address RTT(ms) DNS Name
1 192.168.0.250 3
2 62.225.253.105 34
3 212.185.254.246 35
4 62.154.10.184 36 KO-EB1.KO.DE.net.dtag.de
5 194.25.6.110 164 NYC-gw12.USA.net.DTAG.DE
6 144.223.25.1 162 sl-gw28-nyc-8-0.sprintlink.net
7 TIMED OUT
8 144.232.7.101 163 sl-bb20-nyc-15-0-2480M.sprintlink.net
9 144.232.7.106 164 sl-bb21-nyc-14-0-2480M.sprintlink.net
10 144.232.7.98 197 sl-gw9-nyc-9-0.sprintlink.net
11 160.81.43.14 163 sl-Nexxia-2-0-0.sprintlink.net
12 206.108.103.189 164 Ncore2-newyork83-pos9-0.in.bellnexxia.net
13 206.108.103.213 173 core1-montreal02-pos4-0.in.bellnexxia.net
14 TIMED OUT
15 206.108.99.150 214 ottdisr01-pos1-0-0.in.bellnexxia.net
16 209.226.137.126 215 router.qnx.com
17 TIMED OUT
18 TIMED OUT
19 TIMED OUT
20 TIMED OUT
21 TIMED OUT
22 TIMED OUT
23 TIMED OUT