I have browsed wikipedia for insights into the use of the NUT CPU and find that there is no "story" there, as far as I can tell only a dead link. That honestly took me a bit by surprise.
Voyager Series link
Does any of you know why that is and should we not change that?
I am sure this forum can come up with enough significant facts for me (or someone else) to author a short article on that topic.
KimH
(11-16-2018 06:22 AM)KimH Wrote: [ -> ]I have browsed wikipedia for insights into the use of the NUT CPU and find that there is no "story" there, as far as I can tell only a dead link. That honestly took me a bit by surprise.
Voyager Series link
Does any of you know why that is and should we not change that?
I am sure this forum can come up with enough significant facts for me (or someone else) to author a short article on that topic.
KimH
This should get you started.
(You can also pay a visit to TOS for detailed documents)
Massimo, that link is sadly deceased.
The service will be held at 404 Apache Ave...
(11-16-2018 09:32 AM)grsbanks Wrote: [ -> ]Massimo, that link is sadly deceased.
The service will be held at 404 Apache Ave...
Really? That's odd: I can reach it from here.
What about
this?
(11-16-2018 10:30 AM)Massimo Gnerucci Wrote: [ -> ] (11-16-2018 09:32 AM)grsbanks Wrote: [ -> ]Massimo, that link is sadly deceased.
The service will be held at 404 Apache Ave...
Really? That's odd: I can reach it from here.
Me too.
Just tried again with several browsers and I can confirm my initial finding:
![[Image: Screenshot+(24).png]](https://s3-eu-west-1.amazonaws.com/xferperso/forums/Screenshot+(24).png)
(11-16-2018 07:56 AM)Massimo Gnerucci Wrote: [ -> ] (11-16-2018 06:22 AM)KimH Wrote: [ -> ]I have browsed wikipedia for insights into the use of the NUT CPU and find that there is no "story" there, as far as I can tell only a dead link. That honestly took me a bit by surprise.
Voyager Series link
Does any of you know why that is and should we not change that?
I am sure this forum can come up with enough significant facts for me (or someone else) to author a short article on that topic.
KimH
This should get you started.
(You can also pay a visit to TOS for detailed documents)
Thanks a lot, this will help (opened a PDF in less than a second - on my iPad)
I was/am also looking for whether we have some stories/anecdotes from HP about why and when this was made - rather than making a good suggestion. Sort of like the CPU is called NUT because 41C had the Codename CocoNUT (I think..)
(11-16-2018 10:30 AM)Massimo Gnerucci Wrote: [ -> ]Really? That's odd: I can reach it from here.
What about this?
That's better. Thanks.
That's a weird one. It's obviously a local problem because I logged into a remote server of mine and was able to download the PDF from the original link no trouble.
DNS here resolves the hostname to the same IPv4 address and IPv6 address. The host just replies 404 to me and 200 to everyone else!
(11-16-2018 10:33 AM)Harald Wrote: [ -> ] (11-16-2018 10:30 AM)Massimo Gnerucci Wrote: [ -> ]Really? That's odd: I can reach it from here.
Me too.
No problem here (USA)
(11-16-2018 11:25 AM)grsbanks Wrote: [ -> ]That's a weird one. It's obviously a local problem because I logged into a remote server of mine and was able to download the PDF from the original link no trouble.
DNS here resolves the hostname to the same IPv4 address and IPv6 address. The host just replies 404 to me and 200 to everyone else!
I've had no problems with either the first link or the second link.
I'm in the USA, so maybe the different path allow them to work well for me?
smp
(11-16-2018 03:21 PM)rprosperi Wrote: [ -> ]No problem here (USA)
Yes problem here (also USA).
(11-16-2018 11:25 AM)grsbanks Wrote: [ -> ]That's a weird one. It's obviously a local problem because I logged into a remote server of mine and was able to download the PDF from the original link no trouble.
DNS here resolves the hostname to the same IPv4 address and IPv6 address. The host just replies 404 to me and 200 to everyone else!
But within that same ip address it might get internally routed to different load-balancing servers (or VMs?) depending on where your request comes from. I get 404 as well on the first link, the second link works fine.
(11-16-2018 05:51 PM)Claudio L. Wrote: [ -> ] (11-16-2018 11:25 AM)grsbanks Wrote: [ -> ]That's a weird one. It's obviously a local problem because I logged into a remote server of mine and was able to download the PDF from the original link no trouble.
DNS here resolves the hostname to the same IPv4 address and IPv6 address. The host just replies 404 to me and 200 to everyone else!
But within that same ip address it might get internally routed to different load-balancing servers (or VMs?) depending on where your request comes from. I get 404 as well on the first link, the second link works fine.
Same for me here from Germany
Günter
Massimo's PDF link works fine for me.
On my Windows 10 machine, tracert produces this output :
Code:
C:\Windows\system32>tracert hp41.deringenieur.net
Tracing route to hp41.deringenieur.net [88.198.38.73]
over a maximum of 30 hops:
1 140 ms 56 ms 51 ms 10.10.210.1
2 62 ms 53 ms 106 ms v536.ce01.wdc-01.us.leaseweb.net [207.244.100.156]
3 49 ms 54 ms 63 ms ae-7.br01.wdc-01.us.leaseweb.net [108.59.15.128]
4 59 ms 59 ms 109 ms ash-b1-link.telia.net [62.115.35.33]
5 190 ms 217 ms 202 ms ash-bb4-link.telia.net [213.155.136.38]
6 150 ms 137 ms 135 ms ldn-bb4-link.telia.net [62.115.122.60]
7 136 ms 151 ms 134 ms hbg-bb4-link.telia.net [62.115.122.160]
8 182 ms 140 ms 141 ms hbg-b1-link.telia.net [62.115.141.111]
9 197 ms 189 ms 156 ms hetzner-ic-326012-hbg-b1.c.telia.net [213.248.70.1]
10 148 ms 150 ms 148 ms core12.nbg1.hetzner.com [213.239.245.25]
11 147 ms 150 ms 148 ms ex9k1.dc1.nbg1.hetzner.com [213.239.203.226]
12 204 ms 196 ms 195 ms hawking.deringenieur.net [88.198.38.73]
Trace complete.
C:\Windows\system32>
Jonathan
Both links work for me (Chicago, USA).