S From:	ADVAX::"mcnc!VM1.NoDak.EDU!newsmanager%URZ.UNIBAS.CH" 17-AUG-1990 06:12:45.69 ; To:	Multiple recipients of list ANU-NEWS <ANU-NEWS@NDSUVM1>  CC:	, Subj:	Re: NNTP connection refused on VMS 5.2  I Received: by ADVAX.DECnet (utk-mail11 v1.5) ; Fri, 17 Aug 90 06:12:10 EDT B Received:  from mcnc by ge-dab.GE.COM (5.61/GE-DAB 1.12) with UUCP7 	id AA05045 for everhart; Fri, 17 Aug 90 06:11:59 -0400 A Received: from VM1.NoDak.EDU by mcnc.mcnc.org (5.59/MCNC/6-11-90) ( 	id AA21658; Fri, 17 Aug 90 05:17:01 EDT. Message-Id: <9008170917.AA21658@mcnc.mcnc.org>u Received: from NDSUVM1.BITNET by VM1.NoDak.EDU (IBM VM SMTP R1.2.1MX) with BSMTP id 7873; Fri, 17 Aug 90 04:16:30 CDT L Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.07) with BSMTP id"  7858; Fri, 17 Aug 90 04:16:28 CDT) Date:         Fri, 17 Aug 90 07:40:04 GMT 6 Reply-To: mcnc!VM1.NoDak.EDU!newsmanager%URZ.UNIBAS.CH4 Sender: ANU-NEWS Discussion <ANU-NEWS@VM1.NoDak.EDU>2 From: mcnc!VM1.NoDak.EDU!newsmanager%URZ.UNIBAS.CH4 Subject:      Re: NNTP connection refused on VMS 5.2; To: Multiple recipients of list ANU-NEWS <ANU-NEWS@NDSUVM1>    O In article <4254@pavo.concordia.ca>, NEWSMGR@pavo.concordia.ca (Tim Lapin  Tel: % (514) 848-7639  News Manager) writes: K > I tried to set up an nntp feed from one ANU Server to another to test the @ > speed of transfer.  The new system is running VMS version 5.2.@ > Both the older system and the newer system is running ANU 5.8A > I > When I attempted to transfer articles or use the NNTP_CLIENT.EXE module P > from a different machine, the connection was refused.  The system returned the5 > error:   "invalid login information at remote node"  > E > However, when I tried to access the same generation of ANU NEWS S/W F > (see sig below) on this machine (VMS 5.1) from the new one (VMS 5.2) > everything worked!F > NEW (VMS 5.2) -----------> NNTP -------------> NEW (VMS 5.2)  FAILEDF > OLD (VMS 5.1) -----------> NNTP -------------> NEW (VMS 5.2)  FAILEDF > NEW (VMS 5.2) -----------> NNTP -------------> OLD (VMS 5.1)  WORKED > G > Apparently, DEC has begun using alternate passwords for accounts like D > DECNET, starting with VMS 5.2.  Short of changing the password, isL > there another way to get accross the link?  I would like to stay with nntp? > distribution so as to maintain uniformity across our network.  >    E Since VMS 5.2 DECnet objects are set up in a more restricted way than J before. If you perform the default upgrade, your TASK object gets disabledK for users with no proxies (It is given a -- probably -- nonexistent default A login information). Check in your NEWS and NNTP sources what task G string is used when setting up the DECnet connection (is it "0=NNTP" or I "NEWS=" or "TASK=NNTP") and check the DECnet objects at the VMS 5.2 site.    G I don't know ANU NEWS V5.8, but with V6.0 you can define a logical name @ NEWS_<node>_TASK to be a task string which is used in the DECnetG connection. Or you can change the sources(???). Personally, I like most B the solution Geoff suggests in his "Installing NNTP NEWS Servers":5 At the VMS 5.2 site, define a new network object with    H NCP> DEFINE OBJECT NNTP NUMBER 0 FILE <device>:[<directory>]NNTP_DEC.EXE> NCP> DEFINE OBJECT NNTP USER <newsmanager> PASSWORD <password> NCP> SET OBJECT NNTP ALL   ! and, if necessary, at other sites    * $ DEFINE NEWS_<VMS 5.2 site>_TASK "0=NNTP"   G BTW, if your newsmanager account has privileges you do not want to give H a network account, create a new one with minimal privileges and with the newsmanager's UIC.    Hope this helps 
 Petr Zimak