Path: utzoo!utgpu!water!watmath!clyde!rutgers!rochester!bbn!uwmcsd1!ig!agate!ucbvax!noah.arc.CDN!kenw
From: kenw@noah.arc.CDN (Ken Wallewein)
Newsgroups: comp.os.vms
Subject: DECnet X.29 error messages
Message-ID: <675*kenw@noah.arc.cdn>
Date: 8 Feb 88 15:03:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 19


  Every so often I met OPCOM messages like:

> %%%%%%%%%%%  OPCOM   8-FEB-1988 08:57:19.60  %%%%%%%%%%%
> Message from user DECNET
> DECnet event 7.10, call failure
> From node 1.27 (CALARC),  8-FEB-1988 08:57:19.53
> Module X25-PROTOCOL, DTE = xxxxxxxx, Network = DATAPAC
> Direction = Outgoing, Call failure = Remote DTE cleared
> Remote DTE = xxxxxxxx

  Now, I know how to turn these messages off, and all that. What I _really_
want to know is WHICH (*^@$_*(&@# PROCESS IS RESPONSIBLE FOR ORIGINATING THE
CALL!?!?!?  I mean, _somebody_ is trying, knowingly or otherwise, to connect
to the remote DTE. The question is, who? 

   Does anybody have a solution?

/kenw