Could this be the problem ??

[tobor]

With the GPU servers...




I hope we get some input from the man soon..

[Nathan_P]

I can't even connect to the main folding.stanford.edu site, looks like its a pretty major fail somewhere

[toTOW]

As far as I can remember, I always saw a couple of node not answering in the traceroute ... I don't think it's an issue.

Nathan_P> it's working here ... so as fah-web.stanford.edu ...

[Tobit]

toTOW is correct. As evidenced by your traceroute at steps 15 and 16, you are reaching your intended destination just fine. Hops 13&14 are likely some type of firewall device.

[tobor]

toTOW is correct. As evidenced by your traceroute at steps 15 and 16, you are reaching your intended destination just fine. Hops 13&14 are likely some type of firewall device.

Yup,I shoulda realized if It was gettn to the destination It had to be a firewall of some sort..

Thnx

[noorman]

.

I get the same ...

Code: Select all

Tracing route to vsp10v-vz01.Stanford.EDU [171.67.108.201]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.2.1
  2    <1 ms    <1 ms    <1 ms  192.168.3.1
  3     6 ms     7 ms     6 ms  d51537001.access.telenet.be [81.83.112.1]
  4    11 ms    13 ms     9 ms  dD5E0C521.access.telenet.be [213.224.197.33]
  5     9 ms     9 ms    10 ms  dD5E0FD59.access.telenet.be [213.224.253.89]
  6     7 ms     7 ms    12 ms  dD5E0FDB9.access.telenet.be [213.224.253.185]
  7     8 ms     9 ms     8 ms  xe-0-2-0.anr11.ip4.tinet.net [77.67.65.177]
  8    18 ms    51 ms    17 ms  xe-0-0-0.lon11.ip4.tinet.net [89.149.185.166]
  9    19 ms    19 ms    19 ms  te7-6.mpd02.lon01.atlas.cogentco.com [130.117.15.49]
 10    19 ms    20 ms    20 ms  te1-1.mpd02.ams03.atlas.cogentco.com [130.117.1.97]
 11    20 ms    20 ms    20 ms  te4-2.ccr01.ams03.atlas.cogentco.com [130.117.49.62]
 12   106 ms   108 ms   106 ms  te3-2.mpd01.ymq02.atlas.cogentco.com [154.54.0.70]
 13   197 ms   203 ms   202 ms  te9-8.mpd01.ord01.atlas.cogentco.com [38.20.46.9]
 14   155 ms   153 ms   157 ms  te0-3-0-1.mpd21.mci01.atlas.cogentco.com [154.54.7.138]
 15   244 ms   205 ms   219 ms  te9-4.mpd01.sfo01.atlas.cogentco.com [154.54.2.210]
 16   329 ms   225 ms   205 ms  te7-4.mpd01.sjc04.atlas.cogentco.com [154.54.28.82]
 17   174 ms   174 ms   174 ms  Stanford_University2.demarc.cogentco.com [66.250.7.138]
 18     *      195 ms   186 ms  boundarya-rtr.Stanford.EDU [68.65.168.33]
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21   187 ms   186 ms   185 ms  vsp10v.Stanford.EDU [171.67.108.18]
 22   186 ms   186 ms   186 ms  vsp10v-vz01.Stanford.EDU [171.67.108.201]

Trace complete.

That 's from the other side of the big Pond (Europe/Belgium/near Brussels)

.

[John Naylor]

Likewise from the UK...

Code: Select all

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\John>tracert assign-GPU.stanford.edu

Tracing route to vsp10v-vz01.stanford.edu [171.67.108.201]
over a maximum of 30 hops:

  1     2 ms     1 ms    <1 ms  gw.customer.elgar.uob.lan [10.111.0.1]
  2    <1 ms    <1 ms    <1 ms  br2-gws401.uob.ask4internet.com [78.109.182.2]
  3    13 ms     4 ms     4 ms  man-xmr.tcw-uob.core.ask4.net [81.23.48.214]
  4     5 ms     4 ms     5 ms  149.6.11.17
  5    11 ms    11 ms    11 ms  te7-8.mpd02.lon01.atlas.cogentco.com [130.117.48.33]
  6    85 ms    85 ms    85 ms  te0-2-0-6.mpd21.jfk02.atlas.cogentco.com [130.117.1.105]
  7   113 ms   113 ms   113 ms  te3-2.mpd01.ord01.atlas.cogentco.com [154.54.29.161]
  8   126 ms   125 ms   124 ms  te0-3-0-1.mpd21.mci01.atlas.cogentco.com [154.54.7.138]
  9   162 ms   162 ms   163 ms  te2-2.mpd01.sfo01.atlas.cogentco.com [154.54.6.38]
 10   164 ms   163 ms   163 ms  te4-2.mpd01.sjc04.atlas.cogentco.com [154.54.2.166]
 11   163 ms   163 ms   163 ms  Stanford_University2.demarc.cogentco.com [66.250.7.138]
 12   163 ms   163 ms   163 ms  bnda-rtr-1.Stanford.EDU [68.65.168.33]
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15   159 ms   159 ms   159 ms  vsp10v.Stanford.EDU [171.67.108.18]
 16   163 ms   163 ms   163 ms  vsp10v-vz01.Stanford.EDU [171.67.108.201]

Trace complete.

C:\Users\John>

[noorman]

.

The suggestion of a firewall must be the answer, since that long delay is on the Stanford campus network which you enter 2 hops before the Time Outs occur.

Never thought of that one before Wondered what it was though ...
One learns something new every day

.

[bruce]

From here in the Los Angeles area, it looks similar.

It's not uncommon for routers to either refuse to reply to pings or to treat that in a low-priority activity in order to expedite their primary function of moving a lot of data quickly rather than wasting time responding to pings. Note that the Boundary Router is slower to reply to the ping (hop 9) that the actual server vsp10v itself.

Code: Select all

Tracing route to vsp10v-vz01.Stanford.EDU [171.67.108.201]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    12 ms    11 ms    11 ms  netblock-****(edited)*********
  3    11 ms    12 ms    11 ms  lax1_cr1_gig_10_0_120.dslextreme.com [66.218.48.145]
  4    11 ms    12 ms    11 ms  66.186.192.157
  5    12 ms    11 ms    12 ms  cenic.laap.net [198.32.146.32]
  6    22 ms    22 ms    22 ms  dc-svl-px1--lax-px1-mpls.cenic.net [137.164.47.152]
  7    22 ms    21 ms    21 ms  dc-paix-px1--svl-px1-ge.cenic.net [137.164.47.20]
  8    22 ms    25 ms    21 ms  dc-stanford--paix-px1-ge.cenic.net [137.164.50.90]
  9   138 ms   204 ms   200 ms  boundarya-rtr.Stanford.EDU [68.65.168.33]
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12    23 ms    22 ms    22 ms  vsp10v.Stanford.EDU [171.67.108.18]
 13    22 ms    23 ms    23 ms  vsp10v-vz01.Stanford.EDU [171.67.108.201]

Trace complete.