From: ADVAX::"mcnc!VM1.NoDak.EDU!newsmanager%URZ.UNIBAS.CH" 17-AUG-1990 06:12:45.69 To: Multiple recipients of list ANU-NEWS CC: Subj: Re: NNTP connection refused on VMS 5.2 Received: by ADVAX.DECnet (utk-mail11 v1.5) ; Fri, 17 Aug 90 06:12:10 EDT Received: from mcnc by ge-dab.GE.COM (5.61/GE-DAB 1.12) with UUCP id AA05045 for everhart; Fri, 17 Aug 90 06:11:59 -0400 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> 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 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 Reply-To: mcnc!VM1.NoDak.EDU!newsmanager%URZ.UNIBAS.CH Sender: ANU-NEWS Discussion From: mcnc!VM1.NoDak.EDU!newsmanager%URZ.UNIBAS.CH Subject: Re: NNTP connection refused on VMS 5.2 To: Multiple recipients of list ANU-NEWS In article <4254@pavo.concordia.ca>, NEWSMGR@pavo.concordia.ca (Tim Lapin Tel: (514) 848-7639 News Manager) writes: > 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 > > When I attempted to transfer articles or use the NNTP_CLIENT.EXE module > from a different machine, the connection was refused. The system returned the > error: "invalid login information at remote node" > > However, when I tried to access the same generation of ANU NEWS S/W > (see sig below) on this machine (VMS 5.1) from the new one (VMS 5.2) > everything worked! > NEW (VMS 5.2) -----------> NNTP -------------> NEW (VMS 5.2) FAILED > OLD (VMS 5.1) -----------> NNTP -------------> NEW (VMS 5.2) FAILED > NEW (VMS 5.2) -----------> NNTP -------------> OLD (VMS 5.1) WORKED > > Apparently, DEC has begun using alternate passwords for accounts like > DECNET, starting with VMS 5.2. Short of changing the password, is > there another way to get accross the link? I would like to stay with nntp > distribution so as to maintain uniformity across our network. > Since VMS 5.2 DECnet objects are set up in a more restricted way than before. If you perform the default upgrade, your TASK object gets disabled for users with no proxies (It is given a -- probably -- nonexistent default login information). Check in your NEWS and NNTP sources what task string is used when setting up the DECnet connection (is it "0=NNTP" or "NEWS=" or "TASK=NNTP") and check the DECnet objects at the VMS 5.2 site. I don't know ANU NEWS V5.8, but with V6.0 you can define a logical name NEWS__TASK to be a task string which is used in the DECnet connection. Or you can change the sources(???). Personally, I like most the solution Geoff suggests in his "Installing NNTP NEWS Servers": At the VMS 5.2 site, define a new network object with NCP> DEFINE OBJECT NNTP NUMBER 0 FILE :[]NNTP_DEC.EXE NCP> DEFINE OBJECT NNTP USER PASSWORD NCP> SET OBJECT NNTP ALL and, if necessary, at other sites $ DEFINE NEWS__TASK "0=NNTP" BTW, if your newsmanager account has privileges you do not want to give a network account, create a new one with minimal privileges and with the newsmanager's UIC. Hope this helps Petr Zimak