Archive-Date: Wed, 5 Jul 2000 09:24:22 -0400 Return-Path: From: Andy Reply-To: Info-TCPware@process.com Subject: Looking for "Specialised" PING Date: Wed, 05 Jul 2000 12:58:40 GMT Message-ID: <8jvbdo$560$1@nnrp1.deja.com> To: Info-TCPware@PROCESS.COM I'm on the scrounge I'm afraid... The background to this request is long & convoluted so I won't bore anyone with the details, but I'm looking to see if anybody's written their own kind of PING program for VMS that will asynchronously PING a whole range of IP addresses and record the responders to a file. If not, I'll just have to sharpen my coding pencil. I need it to do a kind of: $ PING/OUT=OUTPUT.LIS 10.1.0.0 10.1.233.100 and this would PING all IP addresses in the range of .0.0 thru .233.100 inclusive. Does anybody have this kind of code that they'd be willing to share ? Cheers, Sent via Deja.com http://www.deja.com/ Before you buy. ================================================================================ Archive-Date: Wed, 5 Jul 2000 09:40:18 -0400 Date: Wed, 5 Jul 2000 8:38:24 -0500 From: Hunter Goatley Reply-To: Info-TCPware@process.com To: Info-TCPware@process.com CC: andyw9804@my-deja.com Message-ID: <000705083825.202000cb@goatley.com> Subject: RE: Looking for "Specialised" PING Andy writes: > >The background to this request is long & convoluted so I won't bore >anyone with the details, but I'm looking to see if anybody's written >their own kind of PING program for VMS that will asynchronously PING a >whole range of IP addresses and record the responders to a file. If >not, I'll just have to sharpen my coding pencil. > >I need it to do a kind of: > >$ PING/OUT=OUTPUT.LIS 10.1.0.0 10.1.233.100 > >and this would PING all IP addresses in the range of .0.0 thru .233.100 >inclusive. > >Does anybody have this kind of code that they'd be willing to share ? > I have a callable ping() routine that will make it easier to do what you want. You'd just have to supply a wrapper program that called the callable ping() for each host. If you, or anyone else is interested, drop me a line at the address below, and I'll send it out to you. Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ http://www.goatley.com/hunter/ ================================================================================ Archive-Date: Wed, 5 Jul 2000 09:45:01 -0400 Sender: bryant@process.com Date: Wed, 5 Jul 2000 09:42:55 -0400 From: Geoff Bryant Reply-To: Info-TCPware@process.com To: Info-TCPware@process.com CC: bryant@process.com Message-ID: <009EC9ED.DBE550EB.55@process.com> Subject: RE: Looking for "Specialised" PING If you are looking to ping a subnet and there is a network route for that network, then send to subnet.all-ones will broadcast a ping. Might be more widespread than you are looking for though and works only on local wire. Hunter Goatley writes: > >Andy writes: >> >>The background to this request is long & convoluted so I won't bore >>anyone with the details, but I'm looking to see if anybody's written >>their own kind of PING program for VMS that will asynchronously PING a >>whole range of IP addresses and record the responders to a file. If >>not, I'll just have to sharpen my coding pencil. >> >>I need it to do a kind of: >> >>$ PING/OUT=OUTPUT.LIS 10.1.0.0 10.1.233.100 >> >>and this would PING all IP addresses in the range of .0.0 thru .233.100 >>inclusive. >> >>Does anybody have this kind of code that they'd be willing to share ? >> >I have a callable ping() routine that will make it easier to do what >you want. You'd just have to supply a wrapper program that called the >callable ping() for each host. > >If you, or anyone else is interested, drop me a line at the address >below, and I'll send it out to you. > >Hunter >------ >Hunter Goatley, Process Software, http://www.process.com/ > http://www.goatley.com/hunter/ ------------------------------------------------------------- Geoff Bryant bryant@process.com TCPware/Multinet Engineering Process Software Corporation http://www.process.com/ 959 Concord St. Framingham, MA 01701 USA ================================================================================ Archive-Date: Thu, 6 Jul 2000 11:29:56 -0400 Date: Thu, 06 Jul 2000 11:27:34 -0500 (EST) From: bryant@PROCESS.COM Reply-To: Info-TCPware@process.com Subject: TCPware ECO kit available: DRIVERS_V543P030 To: TCPware-Announce@PROCESS.COM Message-ID: <01JRG1E45QMQ006BKB@DELTA.PROCESS.COM> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE TCPware ECO kit announcement The following ECO kit is now available for TCPware: ECO: DRIVERS_V543P030 Description: Fix Paired Network Interface failover w/ certain NI= Cs Release date: 6-JUL-2000 Ranking: 2 Versions: 5.4-3,5.3-3,5.3-2 ftp://ftp.process.com/support/54_3/drivers_v543p030.zip To search the TCPware ECO database, please visit the following URL: http://vms.process.com/eco.html For more information, contact Process Software via: E-mail: support@process.com Phone: 1-800-394-8700 The ECO kit README contents are below. ----------------------------------------------------------- DRIVERS patch kit revision 3.0 for TCPware Version 5.4-3 3= 0-JUN-2000 Copyright =A9 1999-2000 Process Software This patch kit provides new versions of the following drivers for TCPware Version 5.4-3: =09IPDRIVER - On some Alphas, VMS's VCI layer does not report =09=09 a device error when a cable is unplugged from =09=09 the network card. This version of IPDRIVER =09=09 provides a workaround, which allows the paired =09=09 network interface failover support to work. =09=09 (D/E 6150) (ECO rank: 2) This kit also includes the following changes from previous ECO ki= ts: For TCPware V5.4-3: DRIVERS_V543P020 ------------------ =09BGDRIVER - Add support for "privileged sockets" to allow beta 2 = of =09 the Apache server from Compaq to work. (D/E 5732) =09 - Add support for the DEC C values of the multicast =09 options to BGDRIVER (actual change was to IPDRIVER). =09 (D/E 5733) =09=09 - Under certain circumstances, code introduced in =09 DRIVERS_V543P020 could cause an Unexpected System =09 Service Exception and crash the system when doing =09 NETCU SET BG_TCP commands. (D/E 6224, D/E 6243) =09TCPDRIVER - Add proper VMS V7.2 privilege check. (D/E 5775) =09UDPDRIVER - Add proper VMS V7.2 privilege check. (D/E 5775) =09IPDRIVER - Add proper VMS V7.2 privilege check. (D/E 5775) DRIVERS_V543P010 ------------------ =09TCPDRIVER - Changes made to the Outgoing Access Restrictions feat= ure =09 that corrects problems introduced in TCPware 5.4 and =09=09 DRIVERS_V533P050. (D/E 5350) For TCPware V5.3-3: DRIVERS_V533P050 ------------------ =09BGDRIVER - Modify behaviour of IO$_DEACCESS (D/E 2298) =09 - Modified to allow DCL/Perl scripts to work properly =09 under the Netscape FastTrack web server. (D/E 3509) =09 - Provide proper privilege checks under OpenVMS Alpha V= 7.2 =09 and higher. (D/E 5296) =09INETDRIVER - Correct the output of an extra for output from =09 REXEC (D/E 339) =09 - Provide proper privilege checks under OpenVMS Alpha =09 V7.2 and higher. (D/E 5296) =09IPDRIVER - Fix routine which derives largest MTU of all physical =09 interfaces. This is used by TCP to set the MSS =09 advertised at connection establishment. (D/E 2213) =09 - EWA twisted pair Ethernet controllers with the cable removed would hang TCPware during startup. This= problem =09 has been corrected. (D/E 2453) =09 - Provide proper privilege checks under OpenVMS Alpha =09 V7.2 and higher. (D/E 5296) =09NTDRIVER - Drop any received data when closing. (D/E 3330) =09 - Permanent NTA /w CLOSE_DASSGN cannot be=20 =09 deleted. (D/E 1537) =09 - Provide proper privilege checks under OpenVMS Alpha =09 V7.2 and higher. (D/E 5296) =09TCPDRIVER - Recognize SYN packets in successive connections when = old =09 connection is in TIME_WAIT (RLOGIN clients no longer = hang =09 on successive connections) (D/E 3872) =09 - Provide proper privilege checks under OpenVMS Alpha =09 V7.2 and higher. (D/E 5296) =09UDPDRIVER - Provide proper privilege checks under OpenVMS Alpha =09 V7.2 and higher. (D/E 5296) NOTE: You must reboot your system after installing this patch in or= der to load the new driver(s). The old versions of the driver(s) will be renamed to *.EXE_OLD. Once installed, you may undo this patch by renaming the file(s) bac= k to: TCPWARE_COMMON:[TCPWARE]INETDRIVER.EXE_OLD to TCPWARE_COMMON:[TCPWARE]INETDRIVER.EXE TCPWARE_COMMON:[TCPWARE]IPDRIVER.EXE_OLD to TCPWARE_COMMON:[TCPWARE]IPDRIVER.EXE TCPWARE_COMMON:[TCPWARE]BGDRIVER.EXE_OLD to TCPWARE_COMMON:[TCPWARE]BGDRIVER.EXE TCPWARE_COMMON:[TCPWARE]TCPDRIVER.EXE_OLD to TCPWARE_COMMON:[TCPWARE]TCPDRIVER.EXE TCPWARE_COMMON:[TCPWARE]NTDRIVER.EXE_OLD to TCPWARE_COMMON:[TCPWARE]NTDRIVER.EXE TCPWARE_COMMON:[TCPWARE]UDPDRIVER.EXE_OLD to TCPWARE_COMMON:[TCPWARE]UDPDRIVER.EXE [End of ECO announcement] ================================================================================ Archive-Date: Thu, 6 Jul 2000 17:48:32 -0400 From: "Robert Cervantez" Reply-To: Info-TCPware@process.com To: "'Info-TCPware'" Subject: DNS Problems Date: Thu, 6 Jul 2000 14:46:06 -0700 Message-ID: <000801bfe793$97bb0c50$786acbd1@symcastsg.com> MIME-Version: 1.0 Content-Type: text/plain === The original message was multipart MIME === === All non-text parts (attachments) have been removed === I'm having some problems enabling DNS on an AlphaServer 2100, running OpenVMS 6.2, TCPWare v5.2-3. After configuring the server to act as a Caching server (even secondary or primary for that matter), I get an error when running @TCPWARE:STARTNET DNS. Here is the nameserver.log file that is generated.. I'm wondering what command in the many command files is having a problem.. I've tried a SET VERIFY and SET ON, but can't seem to track down the problem. Any help is appreciated. Rob. TCPWARE:NAMESERVER.LOG === NAMED TCPware(R) for OpenVMS V5.2-3 Copyright (c) 1997 Process Software Corporation %%%%%%%%%%%% NAMED 6-JUL-2000 14:33:38.99 %%%%%%%%%%%% %%%%%%%%%%%% NAMED Process ID = 00017C04 %%%%%%%%%%%% %%%%%%%%%%%% NAMED 6-JUL-2000 14:33:39.00 %%%%%%%%%%%% %%TCPWARE_NAMED-I-STARTUP, domain name server started %%%%%%%%%%%% NAMED 6-JUL-2000 14:33:39.68 %%%%%%%%%%%% %%TCPWARE_NAMED-F-IVDIR, unable to change to directory TCPWARE_ROOT:[TCPWARE.NAMED] %NAMED-F-DIRERR, could not change to specified directory -NAMED-I-CHECKLOG, check name server log file %SYSTEM-W-NOSUCHFILE, no such file NameD Exited 2320 SYSTEM job terminated at 6-JUL-2000 14:33:40.48 Accounting information: Buffered I/O count: 65 Peak working set size: 3024 Direct I/O count: 9 Peak page file size: 17392 Page faults: 234 Mounted volumes: 0 Charged CPU time: 0 00:00:00.19 Elapsed time: 0 00:00:01.81 === === MIME part removed : unknown type === ================================================================================ Archive-Date: Thu, 6 Jul 2000 17:55:31 -0400 Sender: miller@process.com Date: Thu, 6 Jul 2000 17:53:24 -0400 From: Valerie Miller Reply-To: Info-TCPware@process.com To: Info-TCPware@process.com CC: miller@process.com Message-ID: <009ECAFB.8B738C28.35@process.com> Subject: RE: DNS Problems >I'm having some problems enabling DNS on an AlphaServer 2100, running >OpenVMS 6.2, TCPWare v5.2-3. [...] >%%%%%%%%%%%% NAMED 6-JUL-2000 14:33:39.68 %%%%%%%%%%%% >%%TCPWARE_NAMED-F-IVDIR, unable to change to directory > TCPWARE_ROOT:[TCPWARE.NAMED] VMS 6.2 has a bug in the C RTL in the chdir() call. It cannot chdir() to a search list (such as TCPWARE_ROOT). You didn't say if you are using VAX or Alpha, but you need to install one of the following VMS ECOs: ALPACRT06_062 (for alpha) VAXCRTL11_062 (for vax) Valerie Miller Process Software ================================================================================ Archive-Date: Thu, 6 Jul 2000 18:46:14 -0400 Message-ID: <39650B7A.C17466D8@PROCESS.COM> Date: Thu, 06 Jul 2000 18:43:06 -0400 From: Michael Corbett Reply-To: Info-TCPware@process.com MIME-Version: 1.0 To: info-tcpware@process.com Subject: RE: DNS Problems Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > > >I'm having some problems enabling DNS on an AlphaServer 2100, running > >OpenVMS 6.2, TCPWare v5.2-3. > > [...] > > >%%%%%%%%%%%% NAMED 6-JUL-2000 14:33:39.68 %%%%%%%%%%%% > >%%TCPWARE_NAMED-F-IVDIR, unable to change to directory > > TCPWARE_ROOT:[TCPWARE.NAMED] > > VMS 6.2 has a bug in the C RTL in the chdir() call. It cannot chdir() > to a search list (such as TCPWARE_ROOT). You didn't say if you are > using VAX or Alpha, but you need to install one of the following > VMS ECOs: > > ALPACRT06_062 (for alpha) > VAXCRTL11_062 (for vax) or change the DIRECTORY statement in the NAMED.BOOT file from TCPWARE_ROOT:[TCPWARE.NAMED] to TCPWARE_SPECIFIC:[TCPWARE.NAMED] and make sure all the NAMED files are in the specific directory. 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: Thu, 13 Jul 2000 18:07:47 -0400 From: "Robert Cervantez" Reply-To: Info-TCPware@process.com To: "'Info-TCPware'" Subject: POP3 problem Date: Thu, 13 Jul 2000 15:01:17 -0700 Message-ID: <000001bfed15$dfc132e0$786acbd1@symcastsg.com> MIME-Version: 1.0 Content-Type: text/plain === The original message was multipart MIME === === All non-text parts (attachments) have been removed === I've recently started getting this error message and of course POP3 problems for all users: %%%%%%%%%%% OPCOM 13-JUL-2000 14:48:32.47 %%%%%%%%%%% Message from user SYSTEM on ALPHA TCPware_POP3, Server exited with error: %SYSTEM-F-ACCVIO, access violation, reas on mask=!XB, virtual address=!XL, PC=!XL, PS=!XL The only thing that has changed recently is the server's default gateway address. Thanks, Rob. === MIME part removed : unknown type === ================================================================================ Archive-Date: Thu, 13 Jul 2000 18:10:04 -0400 Message-ID: <4.3.2.7.2.20000713160652.00b22fb0@pop.clsp.uswest.net> Date: Thu, 13 Jul 2000 16:07:43 -0600 To: Info-TCPware@process.com From: Dan O'Reilly Reply-To: Info-TCPware@process.com Subject: Re: POP3 problem In-Reply-To: <000001bfed15$dfc132e0$786acbd1@symcastsg.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed What version of TCPware? Any patches applied to POP? Can you turn on debug for the POP server? At 04:01 PM 7/13/2000, Robert Cervantez wrote: > === The original message was multipart MIME === > === All non-text parts (attachments) have been removed === > >I've recently started getting this error message and of course POP3 problems >for all users: > >%%%%%%%%%%% OPCOM 13-JUL-2000 14:48:32.47 %%%%%%%%%%% >Message from user SYSTEM on ALPHA >TCPware_POP3, Server exited with error: %SYSTEM-F-ACCVIO, access violation, >reas >on mask=!XB, virtual address=!XL, PC=!XL, PS=!XL > >The only thing that has changed recently is the server's default gateway >address. > >Thanks, >Rob. > > === MIME part removed : unknown type === ------ +-------------------------------+---------------------------------------+ | Dan O'Reilly | | | Principal Engineer | "Time flies like an arrow. Fruit | | Process Software | flies like a banana." | | http://www.process.com | -- Groucho Marx | +-------------------------------+---------------------------------------+ ================================================================================ Archive-Date: Fri, 14 Jul 2000 12:10:37 -0400 Return-Path: From: "Jeff Shanely" Reply-To: Info-TCPware@process.com Subject: Port question Date: Fri, 14 Jul 2000 11:44:59 -0400 Message-ID: To: Info-TCPware@process.com When initializing a queue in vms using tcpware, do I need to insert a port name after the ip address. ie - init/que/proc=tcpware_tssym/ on="xxx.xx.xx.xx, portname" quename and if so, what do I use or where do I find the name of the port used. Thanks ================================================================================ Archive-Date: Fri, 14 Jul 2000 12:21:58 -0400 Message-ID: <396F3D30.C7DDEA15@ipworks.com> Date: Fri, 14 Jul 2000 12:17:52 -0400 From: Matthew Brightman Reply-To: Info-TCPware@process.com MIME-Version: 1.0 To: Info-TCPware@process.com Subject: Re: Port question References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Jeff, You don't need to put a port NAME. However you do need to provide the port NUMBER when you create a TSSYM queue. That port number is provided to you by the printer manufacturer. The TCPware Mgt Guide lists a number of manufacturers and the port numbers that they often use. That's on page 14-16 of the v5.4 Mgt Guide. If your manufacturer isn't listed there then check the documentation of the printer or contact the manufacturers tech support. An example of a init command would be as follows for an HP Jet Direct Printer (which use port 9100) $ init/que/proc=tcpware_tssym/on="192.168.1.1,9100" testqueue $ start/que testqueue Regards, -Matt Brightman IPWorks Inc. Jeff Shanely wrote: > > When initializing a queue in vms using tcpware, do I need to insert a port > name after the ip address. ie - init/que/proc=tcpware_tssym/ > on="xxx.xx.xx.xx, portname" quename and if so, what do I use or where do > I find the name of the port used. > Thanks ================================================================================ Archive-Date: Fri, 14 Jul 2000 12:33:35 -0400 Reply-To: Info-TCPware@process.com From: "Joe Gray" To: Subject: RE: Port question Date: Fri, 14 Jul 2000 11:31:03 -0500 Message-ID: <000501bfedb0$e7644b40$f13f366a@jgpc> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit In-Reply-To: I use --- /on=mynode::"''ipaddr'"/proc=... The most common port is 9100 for HP laserjets, I have one Intel that has 1 parallel and 2 serial with are 2501,3001,3002. I found those on the intel.com site. I think there is an official list like ethernet addrs divi'ed up by mfg but I don't know where to find it. -----Original Message----- From: Jeff Shanely [mailto:jshanely@cartech.com] Sent: Friday, July 14, 2000 10:45 AM To: Info-TCPware@process.com Subject: Port question When initializing a queue in vms using tcpware, do I need to insert a port name after the ip address. ie - init/que/proc=tcpware_tssym/ on="xxx.xx.xx.xx, portname" quename and if so, what do I use or where do I find the name of the port used. Thanks ================================================================================ Archive-Date: Fri, 14 Jul 2000 12:34:13 -0400 From: "Lutes, Dale" Reply-To: Info-TCPware@process.com To: Info-TCPware@process.com Message-ID: <396EFA13.4455CB88@cessna.textron.com> Date: Fri, 14 Jul 2000 11:31:31 -0500 MIME-Version: 1.0 Subject: Re: Port question References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit The port number depends upon the terminal server or network interface card connected to your printer. The chapter on print services in the TCPware Managment Guide lists some common port numbers. If you have the v5.3 doc set, look on page 14-12. Jeff Shanely wrote: > > When initializing a queue in vms using tcpware, do I need to insert a port > name after the ip address. ie - init/que/proc=tcpware_tssym/ > on="xxx.xx.xx.xx, portname" quename and if so, what do I use or where do > I find the name of the port used. > Thanks -- Dale D. Lutes Flight Data Systems Cessna Aircraft Company 316-517-7109 ================================================================================ Archive-Date: Fri, 14 Jul 2000 18:32:50 -0400 From: "Robert Cervantez" Reply-To: Info-TCPware@process.com To: Subject: RE: Port question Date: Fri, 14 Jul 2000 15:27:15 -0700 Message-ID: <000a01bfede2$aa364b60$786acbd1@symcastsg.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit In-Reply-To: <000501bfedb0$e7644b40$f13f366a@jgpc> The most common ports that I've seen are 9100 (HP and XCD). Of course, you could always telnet your specific print server, and do a listing of the ports. Rob. I use --- /on=mynode::"''ipaddr'"/proc=... The most common port is 9100 for HP laserjets, I have one Intel that has 1 parallel and 2 serial with are 2501,3001,3002. I found those on the intel.com site. I think there is an official list like ethernet addrs divi'ed up by mfg but I don't know where to find it. ================================================================================ Archive-Date: Mon, 17 Jul 2000 16:50:46 -0400 Message-ID: <4.3.2.7.2.20000717144801.00b816c8@pop.clsp.uswest.net> Date: Mon, 17 Jul 2000 14:48:31 -0600 To: Info-TCPware@process.com From: Dan O'Reilly Reply-To: Info-TCPware@process.com Subject: Re: POP3 problem In-Reply-To: <4.3.2.7.2.20000713160652.00b22fb0@pop.clsp.uswest.net> References: <000001bfed15$dfc132e0$786acbd1@symcastsg.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Robert - Has your problem gone away? Haven't heard from you for several days. At 04:07 PM 7/13/2000, Dan O'Reilly wrote: >What version of TCPware? Any patches applied to POP? Can you turn on >debug for the POP server? > >At 04:01 PM 7/13/2000, Robert Cervantez wrote: >> === The original message was multipart MIME === >> === All non-text parts (attachments) have been removed === >> >>I've recently started getting this error message and of course POP3 problems >>for all users: >> >>%%%%%%%%%%% OPCOM 13-JUL-2000 14:48:32.47 %%%%%%%%%%% >>Message from user SYSTEM on ALPHA >>TCPware_POP3, Server exited with error: %SYSTEM-F-ACCVIO, access violation, >>reas >>on mask=!XB, virtual address=!XL, PC=!XL, PS=!XL >> >>The only thing that has changed recently is the server's default gateway >>address. >> >>Thanks, >>Rob. >> >> === MIME part removed : unknown type === > >------ >+-------------------------------+---------------------------------------+ >| Dan O'Reilly | | >| Principal Engineer | "Time flies like an arrow. Fruit | >| Process Software | flies like a banana." | >| http://www.process.com | -- Groucho Marx | >+-------------------------------+---------------------------------------+ > ------ +-------------------------------+---------------------------------------+ | Dan O'Reilly | | | Principal Engineer | "Time flies like an arrow. Fruit | | Process Software | flies like a banana." | | http://www.process.com | -- Groucho Marx | +-------------------------------+---------------------------------------+ ================================================================================ Archive-Date: Mon, 17 Jul 2000 18:27:20 -0400 From: "Robert Cervantez" Reply-To: Info-TCPware@process.com To: Subject: RE: POP3 problem Date: Mon, 17 Jul 2000 15:23:42 -0700 Message-ID: <000701bff03d$aa5a9e40$786acbd1@symcastsg.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <4.3.2.7.2.20000717144801.00b816c8@pop.clsp.uswest.net> Oh yeah, this has been resolved. The problem involved someone (not the SYSTEM account) making changes to the config. Once I logged back on as SYSTEM, ran the same commands, and restarted TCPWARE, everything was fine. Thanks, Rob. -----Original Message----- From: Dan O'Reilly [mailto:dano@process.com] Sent: Monday, July 17, 2000 1:49 PM To: Info-TCPware@process.com Subject: Re: POP3 problem Robert - Has your problem gone away? Haven't heard from you for several days. At 04:07 PM 7/13/2000, Dan O'Reilly wrote: >What version of TCPware? Any patches applied to POP? Can you turn on >debug for the POP server? > >At 04:01 PM 7/13/2000, Robert Cervantez wrote: >> === The original message was multipart MIME === >> === All non-text parts (attachments) have been removed === >> >>I've recently started getting this error message and of course POP3 problems >>for all users: >> >>%%%%%%%%%%% OPCOM 13-JUL-2000 14:48:32.47 %%%%%%%%%%% >>Message from user SYSTEM on ALPHA >>TCPware_POP3, Server exited with error: %SYSTEM-F-ACCVIO, access violation, >>reas >>on mask=!XB, virtual address=!XL, PC=!XL, PS=!XL >> >>The only thing that has changed recently is the server's default gateway >>address. >> >>Thanks, >>Rob. >> >> === MIME part removed : unknown type === > >------ >+-------------------------------+---------------------------------------+ >| Dan O'Reilly | | >| Principal Engineer | "Time flies like an arrow. Fruit | >| Process Software | flies like a banana." | >| http://www.process.com | -- Groucho Marx | >+-------------------------------+---------------------------------------+ > ------ +-------------------------------+---------------------------------------+ | Dan O'Reilly | | | Principal Engineer | "Time flies like an arrow. Fruit | | Process Software | flies like a banana." | | http://www.process.com | -- Groucho Marx | +-------------------------------+---------------------------------------+ ================================================================================ Archive-Date: Tue, 18 Jul 2000 05:16:29 -0400 Return-Path: From: Andy Reply-To: Info-TCPware@process.com Subject: 'Bad file number' on RCP Date: Tue, 18 Jul 2000 08:55:58 GMT Message-ID: <8l162p$ajv$1@nnrp1.deja.com> To: Info-TCPware@PROCESS.COM Environment: RCP command from system 'A' to system 'B'. Both boxes run TCPware V5.3-2 under OpenVMS VAX V6.2 We have a batch job that runs nightly to copy a fairly large file from system 'A' to system 'B' using RCP. This job has been running for years but about 10 days ago we started getting intermittent failures like this one: $ rcp/user=xxxx zzzz yyyy:zzzz ! yyyy is the remote host bad file number %SYSTEM-F-REJECT, connect to network object rejected $ It failed again this morning, taking the number of failures to 4 in 12 days. The developers/maintainers tell me "nothing has changed", and repeated attempts to recreate the error interactively haven't yet worked; it copies successfully every time. There's nothing that I could see in the online error messages. Has anyone else hit this and managed to suss it out ? Cheers, -Andy Sent via Deja.com http://www.deja.com/ Before you buy. ================================================================================ Archive-Date: Tue, 18 Jul 2000 09:52:14 -0400 Sender: goatley@triton.process.com Return-Path: From: "Scott Layne" Reply-To: Info-TCPware@process.com To: Info-TCPware@process.com Subject: Re: 'Bad file number' on RCP Date: Tue, 18 Jul 2000 05:28:30 EDT MIME-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: Andy, Here's my WAG... The file already exists on the remote system yyyyy, and has a version number of ;32767 Scott ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com ================================================================================ Archive-Date: Tue, 18 Jul 2000 10:45:58 -0400 Sender: goatley@triton.process.com Return-Path: Return-Path: From: Andy Reply-To: Info-TCPware@process.com Subject: Re: 'Bad file number' on RCP Date: Tue, 18 Jul 2000 14:19:24 GMT Message-ID: <8l1p0q$nue$1@nnrp1.deja.com> To: Info-TCPware@PROCESS.COM Sorry Scott, nice try but no cigar... The file that get copied has a unique name based on the date and time... I also just did a quick test: Trying to create an illegally high version of the file simply returns %RCP-E-ERROR, !AS Not a wonderful error message, but not what we're occasionally seeing. Thanks anyway, -Andy In article , Scott Layne wrote: > Andy, > > Here's my WAG... > > The file already exists on the remote system yyyyy, and has a version number > of ;32767 > > Scott > ________________________________________________________________________ > Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com > > Sent via Deja.com http://www.deja.com/ Before you buy. ================================================================================ Archive-Date: Wed, 19 Jul 2000 19:12:08 -0400 Message-ID: From: "Thibodeau, Marie-Line (NBLC/SANB)" Reply-To: Info-TCPware@process.com To: "'Info-TCPware@process.com'" Subject: RE: TCPware ECO kit available: DRIVERS_V543P030 Date: Wed, 19 Jul 2000 20:09:27 -0300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Bryant; I am out of the office until January 2001. Could you make arrangments = for my name to be taken out of this distribution list, please? Thanks Marie-Line > -----Original Message----- > From: bryant@PROCESS.COM [SMTP:bryant@PROCESS.COM] > Sent: Thursday, July 06, 2000 1:28 PM > To: TCPware-Announce@PROCESS.COM > Subject: TCPware ECO kit available: DRIVERS_V543P030 >=20 > TCPware ECO kit announcement >=20 > The following ECO kit is now available for TCPware: >=20 > ECO: DRIVERS_V543P030 > Description: Fix Paired Network Interface failover w/ certain = NICs > Release date: 6-JUL-2000 > Ranking: 2 > Versions: 5.4-3,5.3-3,5.3-2 >=20 > ftp://ftp.process.com/support/54_3/drivers_v543p030.zip >=20 > To search the TCPware ECO database, please visit the following URL: >=20 > http://vms.process.com/eco.html >=20 > For more information, contact Process Software via: >=20 > E-mail: support@process.com > Phone: 1-800-394-8700 >=20 > The ECO kit README contents are below. >=20 > ----------------------------------------------------------- > DRIVERS patch kit revision 3.0 for TCPware Version 5.4-3 > 30-JUN-2000 >=20 > Copyright =A9 1999-2000 Process Software >=20 > This patch kit provides new versions of the following drivers for > TCPware Version 5.4-3: >=20 > IPDRIVER - On some Alphas, VMS's VCI layer does not report > a device error when a cable is unplugged from > the network card. This version of IPDRIVER > provides a workaround, which allows the paired > network interface failover support to work. > (D/E 6150) (ECO rank: 2) >=20 > This kit also includes the following changes from previous ECO = kits: >=20 > For TCPware V5.4-3: >=20 > DRIVERS_V543P020 > ------------------ > BGDRIVER - Add support for "privileged sockets" to allow beta 2 of > the Apache server from Compaq to work. (D/E 5732) > - Add support for the DEC C values of the multicast > options to BGDRIVER (actual change was to IPDRIVER). > (D/E 5733) > - Under certain circumstances, code introduced in > DRIVERS_V543P020 could cause an Unexpected System > Service Exception and crash the system when doing > NETCU SET BG_TCP commands. (D/E 6224, D/E 6243) >=20 > TCPDRIVER - Add proper VMS V7.2 privilege check. (D/E 5775) >=20 > UDPDRIVER - Add proper VMS V7.2 privilege check. (D/E 5775) >=20 > IPDRIVER - Add proper VMS V7.2 privilege check. (D/E 5775) >=20 > DRIVERS_V543P010 > ------------------ > TCPDRIVER - Changes made to the Outgoing Access Restrictions > feature > that corrects problems introduced in TCPware 5.4 and > DRIVERS_V533P050. (D/E 5350) >=20 > For TCPware V5.3-3: >=20 > DRIVERS_V533P050 > ------------------ > BGDRIVER - Modify behaviour of IO$_DEACCESS (D/E 2298) > - Modified to allow DCL/Perl scripts to work properly > under the Netscape FastTrack web server. (D/E 3509) > - Provide proper privilege checks under OpenVMS Alpha > V7.2 > and higher. (D/E 5296) >=20 > INETDRIVER - Correct the output of an extra for output from > REXEC (D/E 339) > - Provide proper privilege checks under OpenVMS Alpha > V7.2 and higher. (D/E 5296) >=20 > IPDRIVER - Fix routine which derives largest MTU of all physical > interfaces. This is used by TCP to set the MSS > advertised at connection establishment. (D/E 2213) > - EWA twisted pair Ethernet controllers with the cable > removed would hang TCPware during startup. This > problem > has been corrected. (D/E 2453) > - Provide proper privilege checks under OpenVMS Alpha > V7.2 and higher. (D/E 5296) > > NTDRIVER - Drop any received data when closing. (D/E 3330) > - Permanent NTA /w CLOSE_DASSGN cannot be=20 > deleted. (D/E 1537) > - Provide proper privilege checks under OpenVMS Alpha > V7.2 and higher. (D/E 5296) >=20 > TCPDRIVER - Recognize SYN packets in successive connections when > old > connection is in TIME_WAIT (RLOGIN clients no longer > hang > on successive connections) (D/E 3872) > - Provide proper privilege checks under OpenVMS Alpha > V7.2 and higher. (D/E 5296) >=20 > UDPDRIVER - Provide proper privilege checks under OpenVMS Alpha > V7.2 and higher. (D/E 5296) >=20 > NOTE: You must reboot your system after installing this patch in = order > to load the new driver(s). >=20 > The old versions of the driver(s) will be renamed to *.EXE_OLD. >=20 > Once installed, you may undo this patch by renaming the file(s) = back to: >=20 > TCPWARE_COMMON:[TCPWARE]INETDRIVER.EXE_OLD to > TCPWARE_COMMON:[TCPWARE]INETDRIVER.EXE > TCPWARE_COMMON:[TCPWARE]IPDRIVER.EXE_OLD to > TCPWARE_COMMON:[TCPWARE]IPDRIVER.EXE > TCPWARE_COMMON:[TCPWARE]BGDRIVER.EXE_OLD to > TCPWARE_COMMON:[TCPWARE]BGDRIVER.EXE > TCPWARE_COMMON:[TCPWARE]TCPDRIVER.EXE_OLD to > TCPWARE_COMMON:[TCPWARE]TCPDRIVER.EXE > TCPWARE_COMMON:[TCPWARE]NTDRIVER.EXE_OLD to > TCPWARE_COMMON:[TCPWARE]NTDRIVER.EXE > TCPWARE_COMMON:[TCPWARE]UDPDRIVER.EXE_OLD to > TCPWARE_COMMON:[TCPWARE]UDPDRIVER.EXE >=20 > [End of ECO announcement] >=20 ================================================================================ Archive-Date: Thu, 20 Jul 2000 11:42:18 -0400 Date: Thu, 20 Jul 2000 11:45:34 -0400 (EDT) From: Gary Reynolds Reply-To: Info-TCPware@process.com To: Info-TCPware@process.com Subject: PURVEYOR new installation question ... In-Reply-To: <4.3.2.7.2.20000717144801.00b816c8@pop.clsp.uswest.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hello, I've recently installed the Purveyor web server V2.0, applied the Y2k V2.1 upgrade and successfully displayed the default web page as well as entered the Remote Services Management console. A few days later, in attempting to access either the Default web page or RSM, I am now receiving an error message from my browser that : "The requested URL was not found" My TCPware version is V5.4-3 patched to latest release, DRIVERS_V543_p030 Everything else, Telnet and FTP to my ISP works fine. Are there any methods or tools to test the local setup ? I have changed nothing in the PURVEYOR:CONFIG80.DB since installation and initial successful testing. Also, have done a PURVEYOR:PURVEYOR_SHUTDOWN & PURVEYOR:PURVEYOR_STARTUP to see id that clears the problem. TIA, Gary greynold@waynesburg.edu ================================================================================ Archive-Date: Thu, 20 Jul 2000 12:23:51 -0400 Sender: mehlhop@process.com Date: Thu, 20 Jul 2000 12:21:10 -0400 From: mehlhop@process.com Reply-To: Info-TCPware@process.com To: Info-TCPware@process.com Message-ID: <009ED5CD.7352CF23.138@process.com> Subject: Auto Reply from Watch_Mail for 19-JUL-2000 20:30 to 2-AUG-2000 06:00 I am on medical leave July 20-21 and vacation from July 24-August 1st. I will be back August 2nd and will answer mail as soon as I can. If you need support please call 800-722-7770. Jim ================================================================================ Archive-Date: Thu, 20 Jul 2000 13:04:12 -0400 Sender: corbett@process.com Date: Thu, 20 Jul 2000 13:01:29 EDT From: Michael Corbett Reply-To: Info-TCPware@process.com To: Info-TCPware@process.com Message-ID: <009ED5D3.15A84D61.12@process.com> Subject: RE: PURVEYOR new installation question ... >Hello, > > I've recently installed the Purveyor web server V2.0, applied the Y2k V2.1 >upgrade and successfully displayed the default web page as well as entered >the Remote Services Management console. > >A few days later, in attempting to access either the Default web page or RSM, >I am now receiving an error message from my browser that : > "The requested URL was not found" > >My TCPware version is V5.4-3 patched to latest release, DRIVERS_V543_p030 >Everything else, Telnet and FTP to my ISP works fine. > >Are there any methods or tools to test the local setup ? I have changed >nothing in the PURVEYOR:CONFIG80.DB since installation and initial >successful testing. Also, have done a PURVEYOR:PURVEYOR_SHUTDOWN & >PURVEYOR:PURVEYOR_STARTUP to see id that clears the problem. Are there any opcom mesages generated when the problem occurs? regards Mike ================================================================================ Archive-Date: Thu, 20 Jul 2000 14:26:30 -0400 Sender: schreiber@process.com Date: Thu, 20 Jul 2000 14:23:48 -0400 From: Jeff Schreiber Reply-To: Info-TCPware@process.com To: Info-TCPware@process.com CC: schreiber@process.com Message-ID: <009ED5DE.959D69BA.92@process.com> Subject: RE: PURVEYOR new installation question ... Michael Corbett writes: >> >>A few days later, in attempting to access either the Default web page or RSM, >>I am now receiving an error message from my browser that : >> "The requested URL was not found" >> Check if the welcome.html file still exists in the web directory. If it does, do a "$dir/security welcome.html" and see if it's something the Purveyor Worker Process can access. -Jeff -- Jeff Schreiber, Process Software Corp. schreiber@mx.process.com http://www.process.com TCPware & MultiNet: Stronger than Ever ================================================================================ Archive-Date: Tue, 25 Jul 2000 06:10:49 -0400 Message-ID: From: Peter De La Cour Reply-To: Info-TCPware@process.com To: Info-TCPware@process.com Subject: Compaq Apache Webserver install Date: Tue, 25 Jul 2000 11:07:09 +0100 MIME-Version: 1.0 Content-Type: text/plain Hi, Has anyone tried and succeeded in installing Apache with TCPWare V5.4. I have installed apache without any problems. When I start Apache it doesn't start. Looking in the Apache$server.log I get the following output: APACHE$WWW (*) DSA1:[APACHE] dsa1:[000000.apache.][000000]apache_httpd.exe_alpha;1: cannot determine local ho st name. Use the ServerName directive to set it manually. APACHE$WWW job terminated at 25-JUL-2000 11:02:31.88 I'm assuming that I still need to configure something in TCPware?? Regards Peter *********************************************************************** Any views expressed in this message are those of the individual sender, except where the sender states them to be the views of Itex Limited. This e-mail is intended only for the individual or entity to which it is addressed and contains information that is private and confidential. If you are not the intended recipient you are hereby notified that any dissemination, distribution or copying is strictly prohibited. If you have received this e-mail in error please delete it immediately and advise us by return e-mail to administrator@itexjsy.com. *********************************************************************** ================================================================================ Archive-Date: Tue, 25 Jul 2000 06:22:11 -0400 Date: Tue, 25 Jul 2000 11:21:48 +0100 From: David.Raymond@essential.co.uk Reply-To: Info-TCPware@process.com Subject: RE: Compaq Apache Webserver install To: Info-TCPware@process.com Message-ID: MIME-Version: 1.0 Content-Type: text/plain Peter, Just a guess, since I don't know Apache, but it might be that you did not define a loop back device when you configured TCPware. Do a "$ NETCU SH NET" to check - there should be a LPB-0 line. Regards, David > -----Original Message----- > From: Peter De La Cour [mailto:PeterD@ITEXJSY.com] > Sent: 25 July 2000 11:07 > To: Info-TCPware@process.com > Subject: Compaq Apache Webserver install > > > Hi, > > Has anyone tried and succeeded in installing Apache with > TCPWare V5.4. I > have installed apache without any problems. When I start > Apache it doesn't > start. Looking in the Apache$server.log I get the following output: > > APACHE$WWW (*) > DSA1:[APACHE] > dsa1:[000000.apache.][000000]apache_httpd.exe_alpha;1: cannot > determine > local ho > st name. > Use the ServerName directive to set it manually. > APACHE$WWW job terminated at 25-JUL-2000 11:02:31.88 > > I'm assuming that I still need to configure something in TCPware?? > > Regards Peter > > > ************************************************************** > ********* > Any views expressed in this message are those of the > individual sender, > except where the sender states them to be the views of Itex Limited. > > This e-mail is intended only for the individual or entity to > which it is > addressed and contains information that is private and > confidential. If > you are not the intended recipient you are hereby notified that any > dissemination, distribution or copying is strictly prohibited. If you > have received this e-mail in error please delete it immediately and > advise us by return e-mail to administrator@itexjsy.com. > > ************************************************************** > ********* > ================================================================================ Archive-Date: Tue, 25 Jul 2000 14:06:09 -0400 Date: Tue, 25 Jul 2000 13:00:45 -0500 (CDT) From: Drew Shelton Reply-To: Info-TCPware@process.com Subject: Re: Compaq Apache Webserver install To: Info-TCPware@process.com CC: drew@sematech.org Message-ID: <01JS6OA7YRJG0018CH@SEMATECH.Org> MIME-Version: 1.0 Content-Type: text/plain; CHARSET=US-ASCII Peter, >Has anyone tried and succeeded in installing Apache with TCPWare V5.4. I >have installed apache without any problems. When I start Apache it doesn't >start. Looking in the Apache$server.log I get the following output: > APACHE$WWW (*) > DSA1:[APACHE] >dsa1:[000000.apache.][000000]apache_httpd.exe_alpha;1: cannot determine >local ho >st name. >Use the ServerName directive to set it manually. > APACHE$WWW job terminated at 25-JUL-2000 11:02:31.88 Yes, I just got Apache 1.3.12 up and running last week with TCPware 5.4-3 and OpenVMS 7.2-1. I didn't see the message you're getting, though. Hopefully the previous post will help, but I can tell you that it does work. Drew ============================================================================ Drew Shelton drew@sematech.org VMS Systems Manager office: 512-356-7575 Sematech fax: 512-356-7600 2706 Montopolis Drive Austin, TX 78741-6499 I speak for myself only, not Sematech. "OpenVMS is today what Microsoft wants Windows NT v8.0 to be!" - Compaq, 9/22/98 ============================================================================ ================================================================================ Archive-Date: Tue, 25 Jul 2000 15:04:34 -0400 Date: Tue, 25 Jul 2000 15:07:28 -0400 (EDT) From: Gary Reynolds Reply-To: Info-TCPware@process.com To: Info-TCPware@process.com CC: greynold@waynesburg.edu Subject: XDM Server and EXCURSION/DecWindows client Ethernet timed-out error In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hello, Has anyone encountered problems related either to TCPware upgrade from V5.2 to V5.4-3 or from DecWindows 1.2-3 to 1.2-4 ? [ Since beginning this message, I've discovered a couple of related items ] [ 1. SYS$SYSTEM:PCX$SERVER.COM was missing - have replaced with copy. ] [ 2. In DECW$PRIVATE_APPS_SETUP.COM, have global defined - DECW$START_NEW_] [ DESKTOP "FALSE"; so that old DecWindows CDE starts. At one point I ] [ did get the DecWindows login screen to appear on my PC; but it locked] [ up on me. ] On a few PC's I have eXcursion installed to enable DecWindows session. The exact error message on activation of PC client eXcursion V3.0.571 is: [ This error is still being encountered ... ] "The following error occurred while attempting to start 'create/term/detach on myhost.edu over TCP/IP (rexec) Network routine connect() failed error = ETIMEDOUT" On restart of DecWindows, DECW$SERVER_0_ERROR.LOG indicates a problem with LAT transport attachment as follows: %failed to attach transport LAT, shareable images must be installed to run priviledged image Not sure if this is related as the TCP/IP transport is correctly loaded immediately afterwards. In V5.4 Reference manual pg. 27-5 - I've worked through the troubleshooting steps and in the entry indicating : "Use NETCU SHOW CONNECTIONS ..." "You should see an entry for *.6000 in the Local Address column, in the LISTEN state ... Double-check configuration steps above ..." if not there. I have an entry for *.6000 in LISTEN mode and an *.xdmcp entry listed as well. The only other related thing would be the - $create/display/tranport= tcpware or tcpip ... Thanks for your consideration and reply. gary ================================================================================ Archive-Date: Wed, 26 Jul 2000 08:52:27 -0400 Date: Wed, 26 Jul 2000 08:55:27 -0400 (EDT) From: Gary Reynolds Reply-To: Info-TCPware@process.com To: Info-TCPware@process.com Subject: Re: XDM Server and EXCURSION/DecWindows client Ethernet timed-out error In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hello again, After posting the following message, I found my notes on initial installation and the problem ... The PCX$SERVER.COM provided for by eXcursion was not correctly found in SYS$SYSTEM account where it needed to be. I found, what I believe was a backup copy in SYS$SYSROOT:[SYSEXEl. The other issue revolved around DECW$START_APPS.COM requiring the $CREATE/DISPLAY/TRANSPORT=tcpware (not tcpip). Once these two changes were made, eXcursion came up properly. I have not yet examined the effect of the "new desktop" environment update that came with the DecWindows Motif 1.2-4 upgrade on eXcursion. The only question remaining is the error from DecWindows startup about the LAT transport ... Anywar, thanks again, gary On Tue, 25 Jul 2000, Gary Reynolds wrote: > Hello, > > Has anyone encountered problems related either to TCPware upgrade from > V5.2 to V5.4-3 or from DecWindows 1.2-3 to 1.2-4 ? > > [ Since beginning this message, I've discovered a couple of related items ] > [ 1. SYS$SYSTEM:PCX$SERVER.COM was missing - have replaced with copy. ] > [ 2. In DECW$PRIVATE_APPS_SETUP.COM, have global defined - DECW$START_NEW_] > [ DESKTOP "FALSE"; so that old DecWindows CDE starts. At one point I ] > [ did get the DecWindows login screen to appear on my PC; but it locked] > [ up on me. ] > > On a few PC's I have eXcursion installed to enable DecWindows session. > The exact error message on activation of PC client eXcursion V3.0.571 is: > > [ This error is still being encountered ... ] > > "The following error occurred while attempting to start 'create/term/detach > on myhost.edu over TCP/IP (rexec) > > Network routine connect() failed error = ETIMEDOUT" > > On restart of DecWindows, DECW$SERVER_0_ERROR.LOG indicates a problem with > LAT transport attachment as follows: > > %failed to attach transport LAT, shareable images must be installed > to run priviledged image > > Not sure if this is related as the TCP/IP transport is correctly loaded > immediately afterwards. > ================================================================================ Archive-Date: Sat, 29 Jul 2000 14:38:11 -0400 Return-Path: From: martin@radiogaga.harz.de (Martin Vorlaender) Subject: Re: Support for NIC DE600 via device EIA-0 Message-ID: <39831c43.524144494f47414741@radiogaga.harz.de> Date: Sat, 29 Jul 2000 20:02:43 +0200 Reply-To: Info-TCPware@process.com To: Info-TCPware@PROCESS.COM SR (d@s.com) wrote: : We run VMS 7.1-2 with TCPware 5.3-3 on a DS20. : We just received a DE600, which replaces the old DE500 NIC. I have upgraded : VMS with the MUP 300. The line EIA0: is visible after "show device" : If I want to start that line: : : NETCU> start/ip eia-0 1.1.1.1 : %TCPWARE_NETCU-E-IVLINE, invalid line specification : : You can see the error message yourself. In a similar case I received the following advice from Process support: $ DEFINE/SYSTEM EWA0 EIA0: and configure your system to use EWA0. cu, Martin -- One OS to rule them all | Martin Vorlaender | VMS & WNT programmer One OS to find them | work: mv@pdv-systeme.de One OS to bring them all | http://www.pdv-systeme.de/users/martinv/ And in the Darkness bind them.| home: martin@radiogaga.harz.de