Archive-Date: Tue, 06 Aug 1996 12:19:59 GMT Subject: Telnet Message-ID: <009A66F0.243E7C20@edge.dls.net> From: rozenfeld@edge.dls.net (DLS Systems Support Team) Date: Tue, 06 Aug 1996 12:19:59 GMT Reply-To: rozenfeld@edge.dls.net Hello, there. Does anybody know how to disable reverse lookups for Telnet Daemon in Tcpware 5.1-4 ? Sincerely, Sam Rozenfeld. ================================================================================ Archive-Date: XXX, 7 Aug 1996 17:48:55 GMT Subject: Re: Telnet Message-ID: <1996Aug7.174855.308@decus> From: k_schumacher@decus.ch (Kurt Schumacher - KS E & C) Date: 7 Aug 96 17:48:55 GMT References: <009A66F0.243E7C20@edge.dls.net> In article <009A66F0.243E7C20@edge.dls.net>, rozenfeld@edge.dls.net (DLS Systems Support Team) writes: > Hello, there. > > Does anybody know how to disable reverse lookups for Telnet Daemon in Tcpware > 5.1-4 ? > > Sincerely, > Sam Rozenfeld. TCPWARE:TELNET_COMMANDS.COM: ... $ ! *** TELNET ACCPORNAM *** $ ! $ ! The TELNET Server now uses the host name of the client as the $ ! ACCPORNAM (Remote Port Info) string. However, older versions $ ! of TCPware for OpenVMS used the internet address,port number. If $ ! you need to restore the old action, set bit 8 (mask value of $ ! 256) in the TELNETD_FLAGS symbol (by uncommenting the following $ ! line). $ ! $ ! TELNETD_FLAGS == TELNETD_FLAGS .OR. 256 ! Use old style ACCPORNAM simply uncomment this last line! then: $ @tcpware:shutnet telnet $ @tcpware:startnet telnet This should do. regards Kurt -- +----------------------------------------------------------------------+ | Kurt Schumacher E-Mail: Kurt.Schumacher@decus.ch | | PSI-Mail: PSI%47911312::K_SCHUMACHER | | Riedhofstrasse 303 Voice: +41 1 342 42 54 | | CH-8049 Zürich FAX: +41 1 342 42 54 | +----------------------------------------------------------------------+ ================================================================================ Archive-Date: Thu, 08 Aug 1996 12:48:40 GMT Subject: ANU-NEWS Implementation onTCPware Message-ID: <4ucnjh$tr8@nw101.infi.net> From: usatlccc@ibmmail.com (Cameron C. Caffee) Date: Thu, 08 Aug 96 12:48:40 GMT Does anyone have a specific list of implementation tips and techniques for implementation on Process Software's TCPware for VAX/VMS ? A pointer to FAQ's etc. would also be appreciated ! Thanks ! Cameron usatlccc@ibmmail.com ================================================================================ Archive-Date: XXX, 15 Aug 1996 11:02:11 -0400 Subject: Re: ANU-NEWS Implementation onTCPware Message-ID: <1996Aug15.110211@process.com> From: bryant@process.com (Geoff Bryant) Date: 15 Aug 96 11:02:11 -0400 References: <4ucnjh$tr8@nw101.infi.net> In article <4ucnjh$tr8@nw101.infi.net>, usatlccc@ibmmail.com (Cameron C. Caffee) writes: > Does anyone have a specific list of implementation tips and techniques for > implementation on Process Software's TCPware for VAX/VMS ? > > A pointer to FAQ's etc. would also be appreciated ! > > Thanks ! > > Cameron > > usatlccc@ibmmail.com If you have purchased our Internet Server product, we provide everything you need from source to executables on the CD. Here is the initial readme for ANU news from the CD: ANU NEWS V6.1 BETA 10 This kit contains all the zip files contained in the Internet copy of ANU news from the University of Kansas. We've added two other directories called [.NEWS_BUILD_VAX] and [.NEWS_BUILD_ALPHA]. These directories contain subdirectories for the executables and objects built for each architecture, Vax and Alpha. The directory structure contained within is the correct structure for building from scratch. See the news.ps or news.txt files in the [.news_docs] for procedures. The minimum supported version for VAX is OpenVMS 5.5 and for Alpha is OpenVMS 6.1. The [.news_dist] contains template files and com procedures from the base kit. To Set up TCPware(R) for OpenVMS TCP NNTP Server and Server/Client Nodes: 1. Copy nntp_tcpwinmultinet.exe to tcpware_common:[tcpware]nntp_server.exe. 2. Make sure that the following line appears in the tcpware:services. file. nntp 119/tcp readnews # USENET News Transfer Protocol 3. Use NETCU as follows to define the service: $ RUN TCPWARE:NETCU ADD SERVICE NNTP STREAM TCPWARE:NNTP_SERVER.EXE - /PROCESS_NAME = NNTP_SERVER - /NOACCOUNTING - /NOAUTHORIZE - /UIC = [SYSTEM] - /AST_LIMIT = 50 - /BUFFER_LIMIT = 10240 - /ENQUEUE_LIMIT = 100 - /EXTENT = 1024 - /FILE_LIMIT = 50 - /IO_BUFFERED = 16 - /IO_DIRECT = 16 - /MAXIMUM_WORKING_SET = 4096 - /PAGE_FILE = 10000 - /PRIORITY = 4 - /PRIVILEGES = (NOSAME, SYSPRV, PHY_IO, NETMBX, TMPMBX, WORLD) - /QUEUE_LIMIT = 8 - /WORKING_SET = 1024 - /SUBPROCESS_LIMIT = 0 Note: Feel free to alter the quota parameters. These are just initial values. Also, you may want to add access restrictions. 4. You should also add the commands in (3) to the TCPWARE:SERVERS.COM file so that the service will be defined at subsequent TCPware startups. Hope that helps. Geoff Bryant Prcoess Software ================================================================================ Archive-Date: Mon, 12 Aug 1996 06:57:48 GMT Subject: Re: ANU-NEWS Implementation onTCPware Message-ID: <4umkhh$3m3@halley.pi.net> From: kcl@pi.net (John Kattestaart) Date: Mon, 12 Aug 1996 06:57:48 GMT References: <4ucnjh$tr8@nw101.infi.net> usatlccc@ibmmail.com (Cameron C. Caffee) wrote: >Does anyone have a specific list of implementation tips and techniques for >implementation on Process Software's TCPware for VAX/VMS ? >A pointer to FAQ's etc. would also be appreciated ! >Thanks ! They have a website! >Cameron >usatlccc@ibmmail.com John Kattestaart KCL Foundation Netherlands ================================================================================ Archive-Date: Wed, 14 Aug 1996 21:05:58 GMT Subject: TCPware for RSX Message-ID: <840056758snz@ppltd.demon.co.uk> From: Elizabeth Power Date: Wed, 14 Aug 96 21:05:58 GMT Reply-To: ehpower@ppltd.demon.co.uk Is anyone out there using TCPware for RSX? I have just started using it. The functionality is rather limited, but I've encountered a few things which suggest to me that the user base may be even more so! Fortunately what there is seems OK so far and the documentation is quite good. Regards Elizabeth -- Elizabeth Power ================================================================================ Archive-Date: XXX, 28 Aug 1996 15:09:51 EDT Subject: ??? NEWBIE QUESTION ??? Message-ID: <1996Aug28.150951.15954@giant> From: joneil@giant.intranet.com Date: 28 Aug 96 15:09:51 EDT Hi, First of all, I'm *extremely* green in configuring networks, so please bear with me. I'm trying to connect a PC-lan system to a VAX 3100 system running TCPWare V5.1-4. There is a decrouter 90t connected to the ethernet. The address of my vax is 192.9.200.60, and an address in the lan that I'm trying to ping is 192.15.1.99. Something tells me I need to add a ROUTE in NETCU, since the following errors appeared on my first ping attempt: $ PING 192.15.1.99 PING 192.15.1.99: 56 data bytes sendto: no route to host ping: wrote 192.15.1.99 64 chars, ret=-1 sendto: no route to host ping: wrote 192.15.1.99 64 chars, ret=-1 Now you would probably need more information from me, but I'm not sure what info I should forward to you (see, I told you i was *green*). If there's anyone out there who may have done this type of thing, could you either email me or followup post asking for more specific info. I would GREATLY APPRECIATE IT. TIA John O'Neil Intranet, Inc. JONEIL@INTRANET.COM ================================================================================ Archive-Date: Wed, 28 Aug 1996 17:10:05 -0500 Subject: Re: ??? NEWBIE QUESTION ??? Message-ID: <3224C3BC.4E86@process.com> From: Michael Corbett Date: Wed, 28 Aug 1996 17:10:05 -0500 References: <1996Aug28.150951.15954@giant> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit joneil@giant.intranet.com wrote: > > Hi, > > First of all, I'm *extremely* green in configuring networks, so please > bear with me. I'm trying to connect a PC-lan system to a VAX 3100 system > running TCPWare V5.1-4. There is a decrouter 90t connected to the > ethernet. The address of my vax is 192.9.200.60, and an > address in the lan that I'm trying to ping is 192.15.1.99. Something > tells me I need to add a ROUTE in NETCU, since the following errors > appeared on my first ping attempt: > > $ PING 192.15.1.99 > PING 192.15.1.99: 56 data bytes > sendto: no route to host > ping: wrote 192.15.1.99 64 chars, ret=-1 > sendto: no route to host > ping: wrote 192.15.1.99 64 chars, ret=-1 > > Now you would probably need more information from me, but I'm not sure what > info I should forward to you (see, I told you i was *green*). > If there's anyone out there who may have done this type of thing, > could you either email me or followup post asking for more specific > info. I would GREATLY APPRECIATE IT. > John, Try the following - $ NETCU ADD ROUTE 192.15.1.99 /host 192.9.200.60 This will tell TCPware that it can reach that host by sending the packets out over the 192.9.200.60 interface. If your DECserver had an address that started with 192.15.1 and you were using the default subnet mask of 255.255.255.0 there would be no need to do this. I'm not sure what you network configuration is so there may be a reason that the DECserver was given the address it was. Feel free to send me a message or give me a call if you have any questions. regards Mike -- +-----------------------------------------------------------------+ Michael Corbett Email: Corbett@process.com Process Software Corporation Phone: 800 722-7770 x369 959 Concord St. 508 879-6994 x369 Framingham MA 01701-4682 FAX: 508 879-0042 ================================================================================ Archive-Date: Wed, 28 Aug 1996 17:13:24 -0500 Subject: Re: ??? NEWBIE QUESTION ??? Message-ID: <3224C483.32C6@process.com> From: Michael Corbett Date: Wed, 28 Aug 1996 17:13:24 -0500 References: <1996Aug28.150951.15954@giant> <3224C3BC.4E86@process.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Michael Corbett wrote: > John, > > Try the following - > > $ NETCU ADD ROUTE 192.15.1.99 /host 192.9.200.60 > > This will tell TCPware that it can reach that host by > sending the packets out over the 192.9.200.60 interface. > > If your DECserver had an address that started with 192.15.1 Ooopss that should be started with 192.9.200. > and you were using the default subnet mask of 255.255.255.0 there > would be no need to do this. I'm not sure what you network > configuration is so there may be a reason that the DECserver > was given the address it was. > > Feel free to send me a message or give me a call if you > have any questions. > > -- +-----------------------------------------------------------------+ Michael Corbett Email: Corbett@process.com Process Software Corporation Phone: 800 722-7770 x369 959 Concord St. 508 879-6994 x369 Framingham MA 01701-4682 FAX: 508 879-0042 ================================================================================ Archive-Date: XXX, 28 Aug 1996 18:18:33 -0400 Subject: Re: ??? NEWBIE QUESTION ??? Message-ID: <1996Aug28.181833@process.com> From: volz@process.com (Bernie Volz) Date: 28 Aug 96 18:18:33 -0400 References: <1996Aug28.150951.15954@giant> In article <1996Aug28.150951.15954@giant>, joneil@giant.intranet.com writes: > Hi, > > First of all, I'm *extremely* green in configuring networks, so please > bear with me. I'm trying to connect a PC-lan system to a VAX 3100 system > running TCPWare V5.1-4. There is a decrouter 90t connected to the > ethernet. The address of my vax is 192.9.200.60, and an > address in the lan that I'm trying to ping is 192.15.1.99. Something > tells me I need to add a ROUTE in NETCU, since the following errors > appeared on my first ping attempt: > > $ PING 192.15.1.99 > PING 192.15.1.99: 56 data bytes > sendto: no route to host > ping: wrote 192.15.1.99 64 chars, ret=-1 > sendto: no route to host > ping: wrote 192.15.1.99 64 chars, ret=-1 > > Now you would probably need more information from me, but I'm not sure what > info I should forward to you (see, I told you i was *green*). > If there's anyone out there who may have done this type of thing, > could you either email me or followup post asking for more specific > info. I would GREATLY APPRECIATE IT. First of all, if both the PC and the VAX are on the same network, you really should be using the same network number for both. In your case (assuming the default Class C network mask), but systems should be in the 192.15.1 or 192.9.200 network. This assumes a network such as the following: |---|----------------|-----------------|--------| | | | VAX PC Decrouter | |---|---------------| (other network) Now, if the router is connecting the two systems, then you need to set up a default route to tell the VAX (and the PC) to use the router whenever communicating outside of their local network (192.9.200 for the VAX and 192.15.1 for the PC). This assumes a network such as: 192.9.200 network |---|----------------------------------|--------| | | VAX DECrouter | |-------|--------------|---------------| | 192.15.1 network PC In this diagram, the DECrouter has TWO addresses - one will be 192.9.200.x and the other will be 192.15.1.y - since it is connected to both networks. For the VAX running TCPware, best is to use @TCPWARE:CNFNET to set up the default route (enter 192.9.200.x). You can also issue the NETCU SET GATEWAY 192.9.200.x command (but this will be lost when you reboot or restart TCPware unless you also add it to the TCPWARE:ROUTING.COM file. Note that x in 192.9.200.x is whatever internet address was assigned to your router at the end that is connected to the network the VAX is on. You'd also need to configure the PC to use the router - it would use a 192.15.1.y address). Configure the default router (or gateway) to be the 192.15.1.y address of the router. Hope that solves your problem. - Bernie Volz Process Software Corporation ================================================================================ Archive-Date: Thu, 29 Aug 1996 21:45:32 GMT Subject: Re: ??? NEWBIE QUESTION ??? Message-ID: <841355132snz@ppltd.demon.co.uk> From: Elizabeth Power Date: Thu, 29 Aug 96 21:45:32 GMT Reply-To: ehpower@ppltd.demon.co.uk References: <1996Aug28.150951.15954@giant> Re-reading your article, I think you need a mask of 255.0.0.0 to get your system to work. -- Elizabeth Power