Re: Hp-parts down for several days

john o goyo <j.o.goyo@xxxxxxxxxxxx> wrote:
Frank Slootweg wrote:
john o goyo <j.o.goyo@xxxxxxxxxxxx> wrote:
Specifically, http://h20141.www2.hp.com/hpparts .
Has anyone any information on this?

No problem here. Perhaps you could try go trough the main HP site,
i.e. <http://www.hp.com> -> Support & Drivers -> Additioanl resources
-> Replacement parts. That should bring you to
<http://h20141.www2.hp.com/hpparts/partsdirectory>.

Yes but if I try to reach the HP Parts Store in North America, I
arrive at the same non-working link. I have already reported to HP
(but they must know).

Since it works for me, but not for you, it is likely to a problem at
your end or a routing problem, but a problem at HP's end is unlikely
(but not impossible).

What does "traceroute h20141.www2.hp.com" (or "tracert ..." if
(MS-)Windows) reveal?

I get a single "Request timed out." before traceroute gets to
16.225.136.62. After that I only get "Request timed out.", but that's
probably normal, because 16.* (Net-16) is an HP (ex Compaq) address, and
I think one can't trace a route inside HP (Rick?).

FYI, here's my traceroute:

C:\home\franks>tracert h20141.www2.hp.com

Tracing route to h20141.www2.hp.com [15.201.24.133]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.123.254
2 12 ms 8 ms 12 ms cd4407401.cable.wanadoo.nl [212.64.116.1]
3 11 ms 8 ms 7 ms 10.0.18.130
4 9 ms 8 ms 13 ms 194.134.178.189
5 9 ms 8 ms 9 ms 10GE1-4.cr2-asd4.nl.euro.net [194.134.162.5]
6 73 ms 27 ms 31 ms PC14.er1-asd5.nl.euro.net [194.134.162.11]
7 14 ms 14 ms 13 ms 193.251.247.209
8 18 ms 18 ms 23 ms so-3-1-0-0.loncr4.London.opentransit.net [193.25
1.242.194]
9 94 ms 93 ms 94 ms po10-0.ashcr1.Ashburn.opentransit.net [193.251.2
40.182]
10 92 ms 93 ms 93 ms gi13-0.ashcr2.Ashburn.opentransit.net [193.251.2
41.54]
11 108 ms 108 ms 109 ms so-0-2-0-0.atlcr3.Atlanta.opentransit.net [193.2
51.241.158]
12 104 ms 107 ms 106 ms ggr1-p320.attga.ip.att.net [192.205.33.29]
13 * 136 ms 140 ms tbr2.attga.ip.att.net [12.123.20.206]
14 132 ms 137 ms 132 ms tbr1.dlstx.ip.att.net [12.122.2.89]
15 136 ms 133 ms 148 ms tbr2.hs1tx.ip.att.net [12.122.10.130]
16 138 ms 137 ms 135 ms gar6.hs1tx.ip.att.net [12.122.103.69]
17 140 ms 137 ms 136 ms 12.87.123.74
18 * * * Request timed out.
19 136 ms 135 ms 136 ms 16.225.136.62
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

C:\home\franks>
.

Relevant Pages

  • Re: AOL Servers Probing ???
    ... Speaking of AOL Proxies, I just got a Hit on Port 80 that seems a bit ... Traceroute before on another IP. ... Tracing route to AC982843.ipt.aol.com ... Trace complete. ...
    (microsoft.public.security)
  • Traceroute Anomaly
    ... ago) when trying to traceroute to my FBSD 4.8 and 4.9 servers. ... From any of the FBSD boxes regardless if they are on the immediate ... am unable to trace back to my FBSD boxes. ... Tracing route to maps.ctch.net ...
    (freebsd-net)
  • Re: I cannot connect to ONE particular website
    ... Have you tried a traceroute to the site? ... Tracing route to soundclick.com ... over a maximum of 30 hops: ... Trace complete. ...
    (microsoft.public.windows.mediacenter)
  • Re: Access to two websites
    ... Tracert logs as below ... Tracing route to steelbeasts.com ... over a maximum of 30 hops: ... Trace complete. ...
    (microsoft.public.windows.inetexplorer.ie6.browser)
  • Re: remote access failing . . .
    ... > When the OpenBSD box is up and I run traceroute from an externl site, ... This is consistent with the trace packets being blocked by the firewall. ... One often blocks incoming ICMP packets as a matter of course. ...
    (comp.unix.bsd.openbsd.misc)