[HECnet] unable to connect to listener

Whichever you think is more appropriate for the task. SG1 would be nice so I can test set host if ncp is being wonky. -brian On 12/29/2011 9:17 AM, Steve Davidson wrote: Brian, I will create an account for you on SG1:: or SGC:: (or both if you wish) so that you can build (and test) your DCL script. Access will be either telnet or ssh. I will send you the specifics to your account on RIFTER::. Enjoy! -Steve -----Original Message----- From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Brian Hechinger Sent: Thursday, December 29, 2011 9:12 AM To: hecnet at Update.UU.SE Subject: [HECnet] unable to connect to listener RIFTER$ mcr ncp show known circuits Known Circuit Volatile Summary as of 29-DEC-2011 09:05:41 Circuit State Loopback Adjacent Name Routing Node QNA-0 on TCP-0-19 on 19.41 (SG1) TCP-0-33 on -starting RIFTER$ mcr ncp tell sg1 show known circuits %NCP-F-CONNEC, unable to connect to listener -SYSTEM-F-UNREACHABLE, remote node is not currently reachable RIFTER$ This has worked in the past, but now I can't connect. Oh, and now it worked: RIFTER$ mcr ncp tell sg1 show known circuits Known Circuit Volatile Summary as of 29-DEC-2011 09:11:01 Circuit State Loopback Adjacent Name Routing Node SVA-0 on 11.2 (MAISA) SVA-0 4.249 (SLAVE) SVA-0 1.300 (CTAKAH) SVA-0 6.1 (STAR69) SVA-0 19.40 (SGC) SVA-0 42.1 (CANADA) SVA-0 2.1 (LEGATO) SVA-0 1.13 (MIM) SVA-0 44.43 (OZON) TCP-0-0 on 19.301 (DUSTY) TCP-0-2 on 2.1 (LEGATO) TCP-0-20 on 20.1 (WOPR) TCP-0-3 on 3.47 (RVDSXL) TCP-0-33 on 33.14 (FRUGAL) TCP-0-4 on -starting TCP-0-52 on 52.2 (RIFTER) TCP-0-59 on 59.58 (STUPI) TCP-0-6 on 6.134 (ROOSTA) TCP-0-8 on 8.400 (GORVAX) RIFTER$ Is there any way to figure out why I keep losing connectivity like that? Could it just be the tunnel bouncing? This is going to complicate my plans to write a DCL script to walk the circuits to attempt to map them. :-D -brian