From: MERC::"uunet!VM1.NoDak.EDU!ANU-NEWS" 22-JUN-1992 15:30:20.52 To: Multiple recipients of list ANU-NEWS CC: Subj: Re: NNTP over DECnet In article <1992Jun19.134509.698@sjh.org>, vaughan@sjh.org (Tom Vaughan) writes: > In article <1992Jun12.105837.6740@vax.oxford.ac.uk>, daveh@vax.oxford.ac.uk wr ites: >> Hi, >> >> We are trying to establish an NNTP connection between two VAXes over DECnet. >> Node OXVAX is to be the server, and node OXPATH is to be the client. >> >> On both systems we have created an NNTP$SERVER account, and placed NNTP_DEC. EXE >> in a location accesible to this account. NNTP_DEC.EXE has been installed with >> SYSPRV. >> >> The DECnet object NNTP has been created as follows (at both ends, in the >> volative and permanent databases): >> >> SET OBJECT NNTP NUMBER 197 FILE NEWS_DEVICE:[NNTP$SERVER]NNTP_DEC.EXE USER >> NNTP$SERVER PASSWORD [password] PROXY BOTH ALIAS INCOMING ENABLED >> >> The logical NEWS_OXPATH_TASK has been defined to "TASK=NNTP" on OXVAX, and >> NEWS_OXVAX_TASK to the same thing on OXPATH. >> [stuff deleted] > > If anyone gets an answer to the DECNET problem please sing out. I can > run NNTP_CLIENT on the same node as the server and get the same results. > But if I define a proxy login for the users on the client node then all > is well with the world. I just cannot afford to maintain proxy logins for > anyone on a WAN that wants to read NEWS. There are a few different way the server can be setup and there are several sets of instructions floating around, some conflicting with each other. Your problem is you are trying to mix two of the methods. If you define a separte NNTP object number 197 you must connect with NNTP= , you can only use TASK=NNTP if nntp is set up as a TASK object (object 0). Here are some step by step instructions that I wrote for someone else, but I never heard back whether they actually worked and I cannot really give them a good test, since my server is already set up. I think this is the easiest way to do it and does not require a separate object number be assigned. If you use them and they DO work, please let me know and I will submit them to be included in with the normal distribution. And of course also please let me know if they do NOT work or I left something important out, so they can be corrected. - Vanya J Cooper, Pima Community College, District Computer Services - Internet: vcooper@pimacc.pima.edu Paper: 2202 West Anklam Road, Tucson, Arizona 85709 USA Voice: 602 884-6809 ================================================== DECNET NNTP Server ------------------ This procedure allows remote systems to connect to the NNTP server using the task specification: "TASK=NNTP". This is the default for ANU News in client-mode and is supposedly compatible with the task specification of the NNTP process supported under Ultrix. It assumes you want a separate account for the NNTP server to run in. Depending on your security needs, you could also use an existing network account (such as DECNET) or set up proxies for the remote system(s). 1. Create a non-privileged account for the NNTP server to run in. Don't forget to create the directory owned by the account and give it a disk quota if needed. Remember the password you assigned for step 4 below. It should look something like this, but you don't have to use this UIC, device or directory. Username: NNTP_SERVER Owner: NNTP default Account: DECNET UIC: [24,2] ([NEWS,NNTP_SERVER]) CLI: DCL Tables: DCLTABLES Default: NEWS_MANAGER_DEV:[NNTP_SERVER] LGICMD: NL: Login Flags: Lockpwd Restricted Dismail Primary days: Mon Tue Wed Thu Fri Secondary days: Sat Sun Primary 000000000011111111112222 Secondary 000000000011111111112222 Day Hours 012345678901234567890123 Day Hours 012345678901234567890123 Network: ##### Full access ###### ##### Full access ###### Batch: ----- No access ------ ----- No access ------ Local: ----- No access ------ ----- No access ------ Dialup: ----- No access ------ ----- No access ------ Remote: ----- No access ------ ----- No access ------ Expiration: (none) Pwdminimum: 6 Login Fails: 0 Pwdlifetime: 180 00:00 Pwdchange: 3-MAY-1991 15:42 Last Login: (none) (interactive), 15-NOV-1991 13:26 (non-interactive) Maxjobs: 0 Fillm: 20 Bytlm: 8192 Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0 Maxdetach: 0 BIOlm: 18 JTquota: 1024 Prclm: 2 DIOlm: 18 WSdef: 200 Prio: 4 ASTlm: 24 WSquo: 500 Queprio: 0 TQElm: 10 WSextent: 10000 CPU: (none) Enqlm: 30 Pgflquo: 10000 Authorized Privileges: TMPMBX NETMBX Default Privileges: TMPMBX NETMBX 2. Copy NNTP_DEC.EXE to NEWS_MANAGER: if necessary and set the world protection to allow execute. $ SET PROTECTION=W:E NEWS_MANAGER:NNTP_DEC.EXE 3. Use the INSTALL utility to install NNTP_DEC.EXE with SYSPRV. Also add the command to news startup file on the server system. $ INSTALL CREATE NEWS_MANAGER:NNTP_DEC.EXE/OPEN/HEAD/SHARE/PRIV=SYSPRV 4. Define the NNTP task object. There will probably be other tasks defined as object 0 on your system, this is ok and will not cause a conflict. (These commands only need to be done once and do NOT need to be in the news startup file.) NCP> DEFINE OBJECT NNTP NUMBER 0 NCP> DEFINE OBJECT NNTP FILE NEWS_MANAGER:NNTP_DEC.EXE NCP> DEFINE OBJECT NNTP USER NNTP_SERVER PASSWORD [put password here] NCP> DEFINE OBJECT NNTP PROXY NONE NCP> SET OBJECT NNTP ALL DECnet NNTP client readers -------------------------- 1. On each client system copy NEWS.EXE to SYS$SYSTEM and NEWS.HLB to SYS$HELP. 2. Define the at least NEWS_NODE, NEWS_ADDRESS, and NEWS_TIMEZONE logicals as as explained in the NEWS_STARTUP file. Do not define NEWS_ROOT or NEWS_DEVICE. You can create a NEWS_MANAGER directory and logical, but it is not required unless the client is using one of the optional files like NEWS_ADDRESS.CNF or NEWSRC.TEMPLATE. NEWS does not need to be installed with privileges on a client only system. 3. If you do not want the help file in SYS$HELP define a logical for it: $ DEFINE/SYSTEM/EXEC NEWS_HELPLIB help-file 4. If you wish to restrict the client to a particular server, also define the following logicals: $ DEFINE/SYSTEM/EXEC NEWS_NNTP_PROTOCOL DECNET $ DEFINE/SYSTEM/EXEC NEWS_NNTP_NODE server-node 5. If you do not restrict the client as in step 4, specify default server in the system-wide (SYS$SYSLOGIN) or user login file NEWS command definition: $ NEWS :== $NEWS/NETPROTOCOL=DECNET/NETSERVER=server-node