Key server down?

Howard Cheng (hcheng@cs.ualberta.ca)
Tue, 8 Apr 1997 21:39:15 -0600 (MDT)


Hi,

Is the key server down? My client stopped working sometime today (not
exactly sure when) as it seems to be waiting for the key server's response.
Doing a ping to 206.168.13.85 gives me no response, and a traceroute looks
like:

traceroute to 206.168.13.85 (206.168.13.85), 30 hops max, 40 byte packets
1 router-24-108-2-1 (24.108.2.1) 13.265 ms 18.376 ms 17.26 ms
2 net217host37.videotron.ab.ca (206.75.217.37) 8.288 ms 13.736 ms 18.015 ms
3 net217host6.videotron.ab.ca (206.75.217.6) 16.192 ms 28.565 ms 34.542 ms
4 192.168.60.17 (192.168.60.17) 16.973 ms 34.19 ms 23.925 ms
5 psp2.ab.canet.ca (206.108.107.33) 45.772 ms 43.099 ms 47.283 ms
6 psp2.bc.canet.ca (205.207.238.185) 65.212 ms 75.704 ms 101.281 ms
7 psp.wa.canet.ca (205.207.238.134) 78.797 ms 87.177 ms 71.01 ms
8 border2-hssi1-0.Seattle.mci.net (204.70.53.5) 127.263 ms 108.106 ms 107.391 ms
9 core1-fddi-1.Seattle.mci.net (204.70.3.145) 96.934 ms 101.924 ms 104.043 ms
10 sl-stk-1-H9/0-T3.sprintlink.net (206.157.77.66) 117.796 ms 141.423 ms 129.848 ms
11 sl-stk-1-H9/0-T3.sprintlink.net (206.157.77.66) 106.531 ms 119.203 ms 119.463 ms
12 sl-che-1-H2/0-T3.sprintlink.net (144.228.10.90) 149.462 ms 145.513 ms 136.855 ms
13 sl-che-3-F0/0.sprintlink.net (144.224.10.3) 142.936 ms 119.929 ms 127.37 ms
14 sl-cica-2-H0-T3.sprintlink.net (144.224.13.6) 135.776 ms 158.213 ms 154.115 ms
15 gw23.boulder.co.coop.net (199.45.132.131) 151.63 ms * 306.723 ms
16 * * *
17 * * *

...

Is this a bad network link, or is there something wrong with the key server?
In any case, my client should be standing by as soon as the key server can
be contacted again.

Thanks

Howard

-- 
Howard Cheng                     e-mail: hcheng@gpu.srv.ualberta.ca
University of Alberta                    hcheng@cs.ualberta.ca
4th year Honors Comp. Sci.       URL   : http://ugweb.cs.ualberta.ca/~hcheng/

I have the proof, but there isn't room to write it in this margin.