OK for me on Greenbee

Link opens to the website OK using Madasafish

Tracing route to imaging-resource.com [208.43.255.194]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 33 ms 31 ms 33 ms lo1.pcl-ag06.plus.net [195.166.128.46]
3 * 36 ms 31 ms unknown.plus.net [84.92.3.73]
4 32 ms 34 ms 32 ms te2-2.thn-gw2.plus.net [212.159.0.190]
5 33 ms 33 ms 34 ms vl23.pte-gw2.plus.net [212.159.4.28]
6 33 ms 32 ms 32 ms cr1-linx-peer.lon005.internap.net [195.66.224.44]
7 117 ms 118 ms 120 ms cr1.wdc005.inappnet.cr1.lon005.internap.net [66.79.147.37]
8 117 ms 117 ms 116 ms cr1-cr2.wdc005.internap.net [66.79.146.201]
9 117 ms * 247 ms core2.wdc002.inappnet-62.cr1.wdc005.internap.net [66.79.151.
130]
10 116 ms 117 ms 116 ms border1.te7-1-bbnet1.wdc008.pnap.net [216.52.127.36]
11 117 ms 117 ms 117 ms te1-1.cer01.wdc01.washingtondc-datacenter.com [66.151.100.66
]
12 115 ms 113 ms 116 ms po1.fcr01.wdc01.washingtondc-datacenter.com [208.43.118.134]

13 116 ms 118 ms 116 ms ir.theimagingresource.com [208.43.255.194]

Trace complete.

Thanks guys for the input.

It still fails for me on the washington.dc0-datacenter 'hop'.

What can cause such a failure at the same 'hop' for some and not for others??? Tracert report request timeout as the error!

Can someone explain that?

TIA

Annoyance big time. But site is perfectly reachable using Hotspotshield, Ultrasurf or other free proxy.

In reply to a post by Goodoldsanta:

Annoyance big time. But site is perfectly reachable using Hotspotshield, Ultrasurf or other free proxy.

Thanks for that ~ I have heard of Proxy servers but never (yet) had a need to make use of such a service.

Googled and found one where you enter the URL and lo & behold up comes ths site in question. Tied zend.com & freeproxyserver.net

But still the question - what the heck is happening that is stopping me at that hop using the direct method??? Are some of the PlusNet IP range being blocked but not others???

Edit - could it be the gateway as I 'suggested/asked' earlier?

Edited by deleted (Sun 27-Sep-09 22:46:07)

It's OK from my home machine. I have an 80.229.x.x IP addy and am connecting via thn-ag3.

If you're having problems, post your IP addy, the gateway you're connecting to and a traceroute and that way we should be able to see any patterns emerging.

Text

1 23 45 67 89 1011 1213 1415 1617 1819 2021 2223 2425 26

C:\Users\Bobby>tracert www.imaging-resource.com  Tracing route to imaging-resource.com [208.43.255.194] over a maximum of 30 hops:    1    94 ms    99 ms   100 ms  home.gateway [192.168.1.254]  2    39 ms    37 ms    44 ms  lo0-plusnet.thn-ag3.plus.net [195.166.128.80]   3    40 ms    39 ms    39 ms  vl303.thn-gw1.plus.net [84.92.3.177]  4    40 ms    40 ms    39 ms  te2-3.thn-gw2.plus.net [212.159.1.58]   5    38 ms    39 ms    44 ms  vl23.pte-gw2.plus.net [212.159.4.28]  6    40 ms    43 ms    39 ms  cr1-linx-peer.lon005.internap.net [195.66.224.44 ]  7   123 ms   131 ms   128 ms  cr1.wdc005.inappnet.cr1.lon005.internap.net [66. 79.147.37]  8   127 ms   126 ms   126 ms  cr1-cr2.wdc005.internap.net [66.79.146.201]   9   119 ms   119 ms   119 ms  core2.wdc002.inappnet-62.cr1.wdc005.internap.net [66.79.151.130]  10   124 ms   123 ms   123 ms  border1.te7-2-bbnet2.wdc008.pnap.net [216.52.127.98]  11   126 ms   124 ms   127 ms  te1-1.cer01.wdc01.washingtondc-datacenter.com [66.151.100.66]  12   136 ms   126 ms   126 ms  po1.fcr01.wdc01.washingtondc-datacenter.com [208.43.118.134]  13   117 ms   118 ms   117 ms  ir.theimagingresource.com [208.43.255.194]  Trace complete.

Still the same from here

Tracing route to imaging-resource.com [208.43.255.194]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 39 ms 38 ms 38 ms lo0-plusnet.pcl-ag04.plus.net [195.166.128.134]
3 38 ms 37 ms 37 ms gi1-6-604.pcl-gw02.plus.net [84.92.0.229]
4 37 ms 41 ms 37 ms te2-2.thn-gw2.plus.net [212.159.0.190]
5 38 ms 47 ms 37 ms vl23.pte-gw2.plus.net [212.159.4.28]
6 38 ms 38 ms 39 ms cr1-linx-peer.lon005.internap.net [195.66.224.44]
7 123 ms 122 ms 121 ms cr1.wdc005.inappnet.cr1.lon005.internap.net [66.79.147.37]
8 122 ms 122 ms 122 ms cr1-cr2.wdc005.internap.net [66.79.146.201]
9 118 ms 118 ms 119 ms core2.wdc002.inappnet-62.cr1.wdc005.internap.net [66.79.151.130]
10 120 ms 119 ms 118 ms border1.te7-2-bbnet2.wdc008.pnap.net [216.52.127.98]
11 119 ms 118 ms 119 ms te1-1.cer01.wdc01.washingtondc-datacenter.com [66.151.100.66]
12 119 ms 118 ms 119 ms po1.fcr01.wdc01.washingtondc-datacenter.com [208.43.118.134]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.

What are the first two octets of your IP address Jim or is it dynamic?

It is not dynamic 81.174.***.*** is that enough for your needs

Edited by deleted (Mon 28-Sep-09 10:24:11)

Hi Bob

I am on ptn-ag2

IP 81.174.xxx.xxx

And as noted before if fails at the washingtondatacenter hop just as oldjim reports as well.

Hoe that helps to see a resolution?

TIA