Archive-Date: XXX, 1 Apr 1994 09:40:02 -0500 Subject: Re: Problems with SLIP or PPP? Message-ID: <1994Apr1.094002.4666@ivax> From: imhw400@indyvax.iupui.edu (Mark H. Wood) Date: 1 Apr 94 09:40:02 -0500 References: <2nerh9$4h@navaho.cc.bellcore.com> In article <2nerh9$4h@navaho.cc.bellcore.com>, kenton@navaho.cc.bellcore.com (gidewall,kenton c) writes: > We are getting ready to put TCP/IP with PPP on our VMS machines and are Nah, go out and get a terminal server that does PPP instead of trying to run this stuff on your hosts. The DECserver700 does that, as does one of the DECserver90 models. Other brands are also available -- we're using Xyplex here. Just let the hosts pick traffic off your LAN, and don't bother them with how it gets there. Let the terminal server handle all that interrupt load. -- Mark H. Wood, Lead Systems Programmer +1 317 274 0749 [@disclaimer@] Internet: IMHW400@INDYVAX.IUPUI.EDU BITNET: IMHW400@INDYVAX I'm not politically incorrect; I'm conformity-challenged. ================================================================================ Archive-Date: XXX, 1 Apr 1994 13:46:26 CST Subject: MX V4.0 is now available!! (no joke) Message-ID: <1994Apr1.134626.10868@netnews.wku.edu> From: goathunter@wkuvx1.wku.edu (Hunter Goatley, WKU) Date: 1 Apr 94 13:46:26 CST Message Exchange (MX) V4.0 is now available. This is a major release that offers a number of enhancements, including a redesigned queueing subsystem and direct support for Wollongong's WIN/TCP and Pathway products. A complete description is included below my sig. Before installing MX V4.0, please read the release notes carefully!! ------------------------------------------------------------------------------- HOW TO GET MX V4.0 MX V4.0 can be obtained via anonymous ftp from the following ftp sites: ftp.wku.edu in [.MX] ftp.spc.edu in [.MX.MX040] niord.shsu.edu in [FILESERV.MX040] and [.MX] segate.sunet.se in [.MX] The latter is a temporary (?) mirror set up specifically for European sites. Thanks to Terry Kennedy, George Greenwade, and Eric Thomas for providing their sites. You can also get MX V4.0 via e-mail from FILESERV@WKUVX1.WKU.EDU, FILESERV@NIORD.SHSU.EDU (shortly), and FILESERV@SEGATE.SUNET.SE (for the European sites). If you don't already have Eric LaFranchi's PACKASM utility, I urge you to get it---it'll make assembling the parts a snap. MX V4.0 comes in 60 181-block files. To get MX V4.0, send the following commands in the body of a mail message to one of the FILESERVs listed above: SEND MX040 SEND FILESERV_TOOLS !Needed if you don't have UNZIP and MFTU SEND PACKASM and SEND PACKASM_OBJ_EXE will return PACKASM from WKUVX1 and SEGATE. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ------------------------------------------------------------------------------- [1-APR-1994] Message Exchange V4.0 Message Exchange (MX) is electronic mail software for OpenVMS VAX systems running VMS V5.0 or later, including OpenVMS V6.0, and OpenVMS AXP systems running OpenVMS AXP V1.0 or later. It supports Internet mail over CMU-OpenVMS TCP/IP, VMS/ULTRIX Connection, TGV MultiNet, Process Software's TCPware, and Wollongong's WIN/TCP and PathWay; BITNET mail over Wingra's Jnet; and UUCP mail over DECUS UUCP. Also included is support for SMTP message transfers over DECnet and X.25 (using VAX P.S.I). MX uses VMS Mail for local message entry and delivery, and includes support for mailing lists and mail-based file servers. Features: * Users send and receive messages using VMS MAIL. Support for "signature" files is included in the VMS MAIL interface. Full support for automatic forwarding with the VMS MAIL SET FORWARD command is included. User-defined alias databases for e-mail addresses is supported. Binary files may be sent through MX to other VMS sites running MX, PMDF, or MultiNet. * Provides SMTP (RFC 821) message transfers over CMU-OpenVMS TCP/IP (aka CMU-Tek TCP/IP), DEC TCP/IP Services for OpenVMS (aka VMS/ULTRIX Connection, TGV MultiNet, TCPware from Process Software, and PathWay and WIN/TCP from Wollongong. Includes support for Internet domain system MX records. Also supports SMTP over DECnet and X.25 (using VAX P.S.I.). * Provides BSMTP message transfers with other BITNET mailers over Jnet, compatible with the CU Mailer package for VM systems. Fully supports BITNET-Internet gateways for non-Internet-connected systems. When combined with the SMTP support, can also provide a BITNET/Internet gateway service. * Interfaces with DECUS UUCP to provide a single mail interface to all mail protocols. Can also gateway between UUCP and other networks. (Not supported under OpenVMS AXP yet because DECUS UUCP has not been ported to AXP yet.) * Provides a mailing list processor with automatic subscription requests. Mailing lists can be configured to restrict postings only to subscribers or list owners, and to restrict the automatic subscription handling. Internet mailing list conventions and a subset of LISTSERV commands are supported. * Supports one or more file servers that can be set up by the system manager to handle automatic distribution of packages of files using mail as the distribution medium. Large transfers can be deferred to off-hours, and daily per-user, per-system, and/or per-server limits can be placed on each server. * Provides interfaces for a site-provided custom mail transport and custom address processing routines. * Provides its own message queueing subsystem. RMS block I/O is used to provide extremely fast queue access with little overhead. Files in this directory: ------------------------ MX040.ZIP The installation kits for MX V4.0 (for use with VMSINSTAL). MX040_SRC.ZIP Source code, in a compressed Zip file. (Coming soon!) MX040_DOCS_ONLY.ZIP The MX040.K saveset containing the docs. This separate .ZIP file is provided for those who want to start with just the docs. NOTE: The K saveset of the installation kit contains the documentation for MX in PostScript, Bookreader, and plain ASCII formats. <<< You will need the UNZIP program in the [ANONYMOUS.MACRO32] directory >>> <<< to expand the compressed files. >>> -------------------------------------------------------------------------------- CONTACTING THE AUTHORS Comments, suggestions, and questions about this software can be directed to the current maintainer at one of the following addresses: Mail: Hunter Goatley Western Kentucky University Academic Computing, STH 226 Bowling Green, KY 421201 E-mail: goathunter@WKUVX1.WKU.EDU Phone: 502-745-5251 (e-mail is preferred) The original author of MX is Matthew D. Madison: Mail: Matthew Madison TGV, Inc. E-Mail: (Internet) madison@tgv.com A mailing list for additional support of MX exists. To subscribe, send the following command in the body of a mail message to MXserver@WKUVX1.WKU.EDU: SUBSCRIBE MX-List "Your real name here" The MX-List mailing list is gatewayed to the vmsnet.mail.mx newsgroup. ------------------------------------------------------------------------------- COPYRIGHT NOTICE This software is COPYRIGHT © 1993, 1994, MadGoat Software. ALL RIGHTS RESERVED. Permission is granted to copy and redistribute this software for no commercial gain, providing all copyright notices remain intact. DISCLAIMER This software is provided "AS IS". The authors and their respective employers disclaim all warranties on the software, including without limitation, all implied warranties of merchantability and fitness. ================================================================================ Archive-Date: XXX, 5 Apr 1994 23:52:39 GMT Subject: Re: Problems with SLIP or PPP? Message-ID: <2nstk7$d2h@scoop.eco.twg.com> From: larry@eco.twg.com (Larry Henry) Date: 5 Apr 1994 23:52:39 GMT Reply-To: larry@eco.twg.com Sender: larry@taoeco.twg.com (Larry Henry) References: <2nerh9$4h@navaho.cc.bellcore.com> In article <2nerh9$4h@navaho.cc.bellcore.com>, kenton@navaho.cc.bellcore.com (gidewall,kenton c) writes: |> |>We are getting ready to put TCP/IP with PPP on our VMS machines and are |>looking at the various vendors' products. Can anyone verify the following |>info? |> |>- UCX doesn't support SLIP or PPP in their implementation. WIN-TCP and |>Multinet do. |> |>- Wollongong's has had some problems with their SLIP/PPP implementations |>(currently or in the past?), but Multinet is pretty solid. |> |>- What about Process Software's TCPWARE? I've heard the name, but that's |>all. Does the package support SLIP and PPP? Is it any good? |> |>Any advice or recommendations as to which we should use? I really don't |>want to start a religious war over this. I am looking for objective |>opinions (and as many facts as possible). :-) |> |>Kenton Gidewall |> Kenton, My recommendation is to go and get a couple of these implementations and put them to the test. I believe most, if not all VMS TCP/IP vendors offer 30 day evaluations of their software. We have SLIP (no PPP yet), and our SLIP is solid :-). -Larry. ---------------- One man's food is another man's poison. ================================================================================ Archive-Date: XXX, 12 Apr 1994 08:23:44 GMT Subject: Green Card Lottery- Final One? Message-ID: <2odlqg$4ti@herald.indirect.com> From: nike@indirect.com (Laurence Canter) Date: 12 Apr 1994 08:23:44 GMT Green Card Lottery 1994 May Be The Last One! THE DEADLINE HAS BEEN ANNOUNCED. The Green Card Lottery is a completely legal program giving away a certain annual allotment of Green Cards to persons born in certain countries. The lottery program was scheduled to continue on a permanent basis. However, recently, Senator Alan J Simpson introduced a bill into the U. S. Congress which could end any future lotteries. THE 1994 LOTTERY IS SCHEDULED TO TAKE PLACE SOON, BUT IT MAY BE THE VERY LAST ONE. PERSONS BORN IN MOST COUNTRIES QUALIFY, MANY FOR FIRST TIME. The only countries NOT qualifying are: Mexico; India; P.R. China; Taiwan, Philippines, North Korea, Canada, United Kingdom (except Northern Ireland), Jamaica, Domican Republic, El Salvador and Vietnam. Lottery registration will take place soon. 55,000 Green Cards will be given to those who register correctly. NO JOB IS REQUIRED. THERE IS A STRICT JUNE DEADLINE. THE TIME TO START IS NOW!! For FREE information via Email, send request to cslaw@indirect.com -- ***************************************************************** Canter & Siegel, Immigration Attorneys 3333 E Camelback Road, Ste 250, Phoenix AZ 85018 USA cslaw@indirect.com telephone (602)661-3911 Fax (602) 451-7617 ================================================================================ Archive-Date: Wed, 13 Apr 1994 21:51:49 GMT Subject: X.25 and VMS with UCX Message-ID: <1994Apr13.215149.24105@puug.pt> From: gaia@puug.pt (Gaia) Date: Wed, 13 Apr 1994 21:51:49 GMT Keywords: VMS, UCX, X.25 Hello Everybody, I will probably fail on explaining what I really want but I'll try. I would like to know how to configure the former UCX (now tcpware, I think) package under VMS to deal with a X.25 board instead of an Ethernet one. We are having a "political" problem at our Institute and the only way to have Internet access outside Portugal for us is to put UCX ruuning in our VMS machine, but "talking" directly to the X.25 board. The DEC manuals just don't explain how to do it at all. Thank you very much for your help. Jorge -- ***************************************************************************** Jorge Lampreia & Paulina Mata Pho.: 351-1-849 07 10 Rua Actor Isidoro, 3-C, 3 Esq. Fax.: 351-1-847 61 67 1900 LISBOA PORTUGAL Another e-mail: jlp@ctqb01.ctqb.pt ***************************************************************************** ================================================================================ Archive-Date: XXX, 15 Apr 1994 13:15:16 -0400 From: volz@process.com (Bernie Volz) Subject: Re: X.25 and VMS with UCX Message-ID: <1994Apr15.131557.447@process.com> Date: 15 Apr 94 13:15:16 -0400 References: <1994Apr13.215149.24105@puug.pt> >Hello Everybody, > >I would like to know how to configure the former UCX (now tcpware, I >think) package under VMS to deal with a X.25 board instead of an Ethernet >one. > UCX is now called TCP/IP Services for OpenVMS. TCPware (for OpenVMS) is a completely separate and different product, developed and sold by Process Software Corporation (*NOT* Digital Equipment Corporation). > >The DEC manuals just don't explain how to do it at all. > If you have TCP/IP Services for OpenVMS, it does NOT support X.25 (to the best of my knowledge). Hence, that is why the DEC manuals don't explain it at all. TCPware for OpenVMS, however, does have X.25 support and our manuals do explain how to do it (hopefully they do so clearly). > >Thank you very much for your help. > If you have UCX (TCP/IP Services for OpenVMS), try the UCX news group - vmsnet.networks.tcp-ip.ucx. If you have TCPware for OpenVMS and need assistance, open a support call via email at support@process.com or call (USA) 508-879-6994. Or, if you'd like information on TCPware, email to sales@process.com or call the same phone number. We can also be reached via FAX at 508-879-0042. - Bernie Volz Process Software Corporation ================================================================================ Archive-Date: XXX, 23 Apr 1994 20:39:55 +0200 Subject: IP/DECNET tunneling Message-ID: <1994Apr23.203955.292@elmrd6.ineab.ikea.se> From: anos@elmrd6.ineab.ikea.se Date: 23 Apr 94 20:39:55 +0200 Hi In the Managment guide (V 4.0), I can see that it's supported to tunnel IP over Decnet WAN links using a Decnet object specification. Could you (Bernie :-), plese be more specific. I would like to tunnel IP to some of IKEA's european offices as a temorary solution until we have IP routers on all major sites. And, if tunneling is a good thing, is there any reasons NOT to continue doing so...(compared to native IP links of course). /Anders -- +-------------------------------------------------------------------------+ | Internet anos@ineab.ikea.se | | Phone +46-42-25 73 08, Anders Ostling | | IKEA Northern Europe AB, Sweden | +-------------------------------------------------------------------------+ ================================================================================ Archive-Date: XXX, 23 Apr 1994 21:14:11 +0200 Subject: SLIP'in and slidin' Message-ID: <1994Apr23.211411.293@elmrd6.ineab.ikea.se> From: anos@elmrd6.ineab.ikea.se Date: 23 Apr 94 21:14:11 +0200 Me again What's the best way (if possible at all) to run SLIP on TCPware 4.0 given the following setup 1. I dial our dialback modem pool 2. The dialback software dials back using a modem on a Maxserver terminal server (LAT is default protocol on the port, but the port has SLIP capabilities after the command SET PORT INTERN SLIP ENAB). 3. I log into the Vax host and ... /Anders -- +-------------------------------------------------------------------------+ | Internet anos@ineab.ikea.se | | Phone +46-42-25 73 08, Anders Ostling | | IKEA Northern Europe AB, Sweden | | | | + Speaking for myself, my cat, my dog and my birdie...That's all + | +-------------------------------------------------------------------------+ ================================================================================ Archive-Date: XXX, 25 Apr 1994 00:09:02 -0400 From: volz@process.com (Bernie Volz) Subject: Re: IP/DECNET tunneling Message-ID: <1994Apr25.000902.475@process.com> Date: 25 Apr 94 00:09:02 -0400 References: <1994Apr23.203955.292@elmrd6.ineab.ikea.se> In article <1994Apr23.203955.292@elmrd6.ineab.ikea.se>, anos@elmrd6.ineab.ikea.se writes: > Hi > > In the Managment guide (V 4.0), I can see that it's supported to tunnel > IP over Decnet WAN links using a Decnet object specification. Could you > (Bernie :-), plese be more specific. I would like to tunnel IP to some > of IKEA's european offices as a temorary solution until we have IP routers > on all major sites. For each DECnet tunnel, you need to set up a listener node at one end and a active node at the other end, giving the opposite node name in each case. See the NETCU START/IP command regarding starting IP over DECnet links. If you'd like some specific details, open a support call (support@process.com) and provide some of the situations you need to configure. @TCPWARE:CNFNET also asks you for the necessary information if you specify IP over DECnet lines (DECNET-n) when asked for the lines. > And, if tunneling is a good thing, is there any reasons NOT to continue > doing so...(compared to native IP links of course). > You can certainly do tunneling, but it does have more overhead than a direct IP link - overhead in terms of both processing as well bits on the network. So, if you have native IP links available, use them. - Bernie Volz Process Software Corporation ================================================================================ Archive-Date: XXX, 25 Apr 1994 00:21:22 -0400 From: volz@process.com (Bernie Volz) Subject: Re: SLIP'in and slidin'y Message-ID: <1994Apr25.002122.476@process.com> Date: 25 Apr 94 00:21:22 -0400 References: <1994Apr23.211411.293@elmrd6.ineab.ikea.se> In article <1994Apr23.211411.293@elmrd6.ineab.ikea.se>, anos@elmrd6.ineab.ikea.se writes: > > What's the best way (if possible at all) to run SLIP on TCPware 4.0 > given the following setup > > 1. I dial our dialback modem pool > 2. The dialback software dials back using a modem on a Maxserver > terminal server (LAT is default protocol on the port, but the > port has SLIP capabilities after the command SET PORT INTERN SLIP ENAB). > 3. I log into the Vax host and ... > If you are going to use the SLIP support on the terminal server, TCPware need not get involved. Configure the terminal server port to run as a SLIP line (depending on how you configure it, you might also need some routing changes). If you want to use standard LAT connections to connect to the VMS system and turn those into SLIP lines, see the TCPWARE:SLIPLOGIN.COM file. This is a template file which you should edit and make the login file for a new account. When you log into that account, the command procedure will automatically set up the SLIP line. There are some modifications that you might want to make if you don't want to use an entire network number for the SLIP line. To do this, you'd issue the following commands: $ NETCU START/IP 'SLIP_LINE' 'HOSTNAME'/UNNUMBERED 'TERMINAL' $ NETCU ADD ROUTE 'USER_IA' 'SLIP_LINE' $ NETCU ENABLE GATEWAY where: SLIP_LINE is the SLIP-n line identification HOSTNAME is the internet address of the local host (could use HOSTNAME = F$TRNLNM("TCPWARE_DOMAINNAME")) TERMINAL is the terminal (could use TERMINAL = F$TRNLNM("TT")) USER_IA is the internet address of the SLIP host Note that the account will need at least OPER privilege to issue the commands. If you're going to set up a bunch of SLIP login accounts, send me email and I can provide you with a command procedure that makes these accounts much easier to manage (we use it here). If you have other questions, open a support call (support@process.com). - Bernie Volz Process Software Corporation ================================================================================ Archive-Date: XXX, 28 Apr 1994 16:07:50 -0400 From: harris@process.com Subject: TCPware Beta Test Site Questionnaire Message-ID: <1994Apr28.160750.494@process.com> Date: 28 Apr 94 16:07:50 -0400 April 28, 1994 Process Software Corporation is currently looking for additional Beta Test sites for the upcoming release of TCPware for OpenVMS. Beta testing is currently underway. If you are interested in participating in this process, please complete and return the attached questionnaire via internet mail to beta@process.com or by FAX to 508-879-0042 ATTN: Beta Test Coordinator. If you are selected as a Beta test site, you will be contacted with additional information shortly. We look forward to hearing from you. Mireille Dempster Technical Support Group Leader ------------------------------------------------------------------------------ TCPWARE BETA TEST SITE QUESTIONNAIRE ____________________________________ Please take a few moments to answer the following questions. The information you provide will help us to better understand and support you as a Beta test site for TCPware for OpenVMS. Company Name: ___________________________________________________________ Shipping Addr: ___________________________________________________________ ___________________________________________________________ Contact Name: ___________________________________________________________ (and title) Phone: (____)______________ Fax:(____)______________ PSC Software License number: ____________________ 1. How soon will you be able to test the Beta software? ___________________ 2. What model(s) of VAX or Alpha CPU's will you use for testing the Beta test software? ___________________________________________________________________________ 3. What version(s) of OpenVMS or OpenVMS for Alpha will be used? ___________________________________________________________________________ ___________________________________________________________________________ 4. What other computer systems will be interacting on your network with the TCPware for OpenVMS system(s)? ___________________________________________________________________________ ___________________________________________________________________________ 5. Please indicate the type of media on which you would like to receive the Beta test software: TK50 ____ 16MT9 ____ 6. Please indicate which TCPware for OpenVMS - TCP/IP Services features you use regularly: ____ Berkeley R Commands ____ PCNFSD V2.0 Support ____ DECwindows Transport Interface ____ QIO Prog Interfaces ____ Domain Name Services (TCPDRIVER, IPDRIVER,etc) ____ FDDI interface support ____ RARP ____ FTP ____ RAPD ____ IP over DECnet Lines ____ RCP ____ IP over X.25 Support ____ SLIP lines ____ LMF licensing support ____ SMTP ____ Line Printer Services ____ SMTP to All_in-1 Gateway ____ Multiple Telnet Sessions ____ SNMP Agent ____ NFS Client Auditing Support ____ Socket Lib Prog Interface ____ NFS Client Support for Symbolic links ____ TELNET ____ NFS Server and Client Compatibility ____ TFTP or BOOTPD ____ NFS-OpenVMS Client ____ Terminal Server Print Svcs ____ NFS-OpenVMS Server ____ UCX QIO emulation ____ NSLOOKUP ____ Utilities(Traceroute|PING) ____ ONC RPC Services ____ VMSINSTAL on any disk ____ On-line help 7. Please indicate which TCPware for OpenVMS - NetWare Services features you are currently using: ____ File Sharing Services ____ Terminal Emulation Services ____ Network Print Services 8. Would you be willing to act as a reference site upon completion of the Beta test? Yes____ No____ 9. What features would you like to see in future releases of TCPware for OpenVMS? _________________________________________________________________________ _________________________________________________________________________ Upon completion, please return this questionnaire to Process Software FAX # 508-879-0042 ATTN: Beta Test Coordinator Internet mail: beta@process.com Thank you for your time and input in helping us provide the best TCP/IP solution for OpenVMS.