November 1995

There is one message totalling 31 lines in this issue. Topics of the day: 1. NETServer Security and Accounting Server

Soon we will be releasing the NETServer Security and Accounting Server for Solaris 2.x. If you're using the NETServer and are interested in beta testing this product, please email me for more information. Thanks, John Received: by ccmail from usr.com >From ROOT@usr.com X-Envelope-From: ROOT@usr.com Received: from listserv.syr.edu by usr.com (4.1/3.1.090690-US Robotics ) id AA06531; Wed, 1 Nov 95 13:11:30 CST Received: from localhost (localhost) by listserv.syr.edu (8.7/8.7) with internal id OAA14136; Wed, 1 Nov 1995 14:12:38 -0500 (EST) >From: Mail Delivery Subsystem <Mailer-Daemon@listserv.syr.edu> Message-Id: <199511011912.OAA14136@listserv.syr.edu> Mime-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; boundary="OAA14136.815253158/listserv.syr.edu" Auto-Submitted: auto-generated (failure) End of USRTC Digest - 11 Oct 1995 to 1 Nov 1995 *********************************************** From POP3server Wed Nov 7 05:19:05 GMT 1995 Return-Path: owner-USRTC@LISTSERV.SYR.EDU Received: from listserv.syr.edu (root@listserv.syr.edu [128.230.1.252]) by mailbox.syr.edu (8.7/8.7) with ESMTP id AAA28548 for <rjkopp@MAILBOX.SYR.EDU>; Tue, 7 Nov 1995 00:00:19 -0500 (EST) Received: from listserv.syr.edu (listserv@listserv.syr.edu [128.230.1.252]) by listserv.syr.edu (8.7/8.7) with SMTP id AAA01580; Tue, 7 Nov 1995 00:00:33 -0500 (EST) Message-Id: <199511070500.AAA01580@listserv.syr.edu> Reply-To: US Robotics Total Control Product <USRTC@LISTSERV.SYR.EDU> Sender: US Robotics Total Control Product <USRTC@LISTSERV.SYR.EDU>

There is one message totalling 22 lines in this issue. Topics of the day: 1. AS5100's net mgmt card lock up

We've been experiencing problems with our net mgmt card locking up on our AS5100's. Typically the cards won't respondto ping packets. When I use the SNMP manager, it seems to correct the problem. Sometimes I have to try a couple times within the SNMP manager to open the chassis, but after I do this, the cards will respond to pings for awhile until the problem repeats. This is happening on all three of our chassis's. Any comments, suggestions?? Michael Rykowski Northwestern University NSG - Network Planning Analyst Phone - (312) 503-2605 Fax - (312) 503-8189 End of USRTC Digest - 1 Nov 1995 to 6 Nov 1995 ********************************************** From POP3server Thu Nov 8 13:55:05 GMT 1995 Return-Path: owner-USRTC@LISTSERV.SYR.EDU Received: from tnt.syr.edu (tnt.syr.edu [128.230.4.245]) by mailbox.syr.edu (8.7/8.7) with ESMTP id IAA21548 for <rjkopp@MAILBOX.SYR.EDU>; Wed, 8 Nov 1995 08:48:36 -0500 (EST) Message-Id: <199511081348.IAA21548@mailbox.syr.edu> Received: from listserv.syr.edu (128.230.1.252) by tnt.syr.edu (LSMTP for Windows NT v1.0a) with SMTP id EADA2D10 ; Wed, 8 Nov 1995 8:48:04 -0500 Reply-To: US Robotics Total Control Product <USRTC@LISTSERV.SYR.EDU> Sender: US Robotics Total Control Product <USRTC@LISTSERV.SYR.EDU>

There is one message totalling 26 lines in this issue. Topics of the day: 1. AS5100's net mgmt card lock up

We have about 10 chassis and have this problem only on one of them. I thought it was probably bad hardware. If there is a cure for this problem (other than getting a new management card), I'd like to know about it too. David At 11:00 AM 11/6/95, Michael Rykowski wrote: >We've been experiencing problems with our net mgmt card locking up on our >AS5100's. Typically the cards won't respondto ping packets. When I use >the SNMP manager, it seems to correct the problem. Sometimes I have to try >a couple times within the SNMP manager to open the chassis, but after I do >this, the cards will respond to pings for awhile until the problem repeats. >This is happening on all three of our chassis's. Any comments, >suggestions?? -- David L. Leach | (208) 368-5336 Internet Services Manager | dleach@micron.net Micron Internet Services | http://www.micron.net/~dleach/ End of USRTC Digest - 6 Nov 1995 to 7 Nov 1995 ********************************************** From POP3server Tue Nov 13 14:38:55 GMT 1995 X-UIDL: e39e074a621a5090d03a4683e2de020b Received: from tnt.syr.edu (tnt.syr.edu [128.230.4.245]) by mailbox.syr.edu (8.7/8.7) with ESMTP id XAA11103 for <RJKOPP@MAILBOX.SYR.EDU>; Fri, 10 Nov 1995 23:06:16 -0500 (EST) Message-Id: <199511110406.XAA11103@mailbox.syr.edu> Received: from listserv.syr.edu (128.230.1.252) by tnt.syr.edu (LSMTP for Windows NT v1.0a) with SMTP id D7DF7430 ; Fri, 10 Nov 1995 22:57:00 -0500

An error was detected while processing the enclosed message. A list of the affected recipient follows. This list is in a special format that allows software like LISTSERV to automatically take action on incorrect addresses; you can safely ignore the numeric codes. --> Error description: Error-for: brice@MAXWELL.IIA3.ORG Error-Code: 3 Error-Text: Domain "MAXWELL.IIA3.ORG" doesn't exist. Error-End: One error reported. Received: from listserv.syr.edu (128.230.1.252) by tnt.syr.edu (LSMTP for Windows NT v1.0a) with SMTP id D724FDD0 ; Fri, 10 Nov 1995 22:56:58 -0500

There is no information file for the USRTC list. Here is a copy of the list "header", which usually contains a short description of the purpose of the list, although its main purpose is to define various list configuration options, also called "keywords". If you have any question about the USRTC list, write to the list owners at the generic address: USRTC-Request@LISTSERV.SYR.EDU * * US Robotics Total Control Product * * Review= Public Subscription= Open Send= Public * Notify= Yes Reply-to= Sender,Respect Files= No * Validate= Yes, Confirm * Confidential= No Ack= No * Default-Options= ShortBSMTP * Digest= Yes,Same,Daily * X-tags= Yes Errors-To= Owner * Service=* * * Owner= rjkopp@mailbox.syr.edu (Ray Kopp) * * From POP3server Sat Nov 17 05:28:25 GMT 1995 X-UIDL: 087aa2f535ecd309ac28f234efac5cb9 Received: from tnt.syr.edu (tnt.syr.edu [128.230.4.245]) by mailbox.syr.edu (8.7/8.7) with ESMTP id AAA17685 for <rjkopp@MAILBOX.SYR.EDU>; Fri, 17 Nov 1995 00:04:55 -0500 (EST) Message-Id: <199511170504.AAA17685@mailbox.syr.edu> Received: from listserv.syr.edu (128.230.1.252) by tnt.syr.edu (LSMTP for Windows NT v1.0a) with SMTP id 64EA9A20 ; Fri, 17 Nov 1995 0:05:24 -0500 Reply-To: US Robotics Total Control Product <USRTC@LISTSERV.SYR.EDU> Sender: US Robotics Total Control Product <USRTC@LISTSERV.SYR.EDU>

The enclosed message, found in the USRTC mailbox and shown under the spool ID 126656 in the system log, has been identified as a possible delivery error notice for the following reason: "X-Report-Type:" field found in mail header. ------------------------ Message in error (59 lines) -------------------------- Received: from tnt.syr.edu (tnt.syr.edu [128.230.4.245]) by listserv.syr.edu (8.7/8.7) with ESMTP id WAA02221 for <USRTC@LISTSERV.SYR.EDU>; Fri, 10 Nov 1995 22:57:11 -0500 (EST) Received: from listserv.syr.edu (128.230.1.252) by tnt.syr.edu (LSMTP for Windows NT v1.0a) with SMTP id D7917B40 ; Fri, 10 Nov 1995 22:56:59 -0500 Received: from tnt.syr.edu (tnt.syr.edu [128.230.4.245]) by listserv.syr.edu (8.7/8.7) with ESMTP id WAA02216 for <owner-USRTC@LISTSERV.SYR.EDU>; Fri, 10 Nov 1995 22:57:11 -0500 (EST) Message-Id: <199511110357.WAA02216@listserv.syr.edu> Reply-to: Mailer-Daemon@tnt.syr.edu

There is one message totalling 25 lines in this issue. Topics of the day: 1. MP16.

Is anyone currently using the MP16 boxes? We switched from a local modem brand to USR Robotics, and we currently use about 7 MP 16 boxes, with about 1 a month coming up from now on. But i'm starting to get worried about the stability of these racks. We have had 3 of them die on us sofar. They go into a mode where either all top 8 modems go 'red' or all bottom 8 go 'red'. Those modems are then totally unusable. Is this a known problem? I read some responses on the Livingston list where people had the same problems. I have 3 MP16's on order currently, but im thinking about cancelling for the moment. Regards, Cor Bosman ps: im new to this list, so I hope this is the right place for this. | Cor Bosman | ____Xs4all Public Access____ | tel: +31-(0)20-622-2885 | | cor@xs4all.net | Network Administrator | fax: +31-(0)20-622-2753 | ------------------The net routes around censorship---------------------SP5---- End of USRTC Digest - 7 Nov 1995 to 16 Nov 1995 *********************************************** From POP3server Wed Nov 28 15:11:51 GMT 1995 X-UIDL: 42e22dde0f348bc93bd1751f2cea941d Return-Path: owner-USRTC@LISTSERV.SYR.EDU Received: from tnt.syr.edu (tnt.syr.edu [128.230.4.245]) by mailbox.syr.edu (8.7.1/8.7.1) with ESMTP id AAA19549 for <rjkopp@MAILBOX.SYR.EDU>; Tue, 28 Nov 1995 00:03:28 -0500 (EST) Message-Id: <199511280503.AAA19549@mailbox.syr.edu> Received: from listserv.syr.edu (128.230.1.252) by tnt.syr.edu (LSMTP for Windows NT v1.0a) with SMTP id 0CBC3310 ; Tue, 28 Nov 1995 0:04:13 -0500 Reply-To: US Robotics Total Control Product <USRTC@LISTSERV.SYR.EDU> Sender: US Robotics Total Control Product <USRTC@LISTSERV.SYR.EDU>

There is one message totalling 27 lines in this issue. Topics of the day: 1. Software Download, the next generation...

We're investigating an improved SDL procedure and would be interested in feedback from users. Please send me email with any comments you have. In particular, we'd like to get feedback on: - direct serial protocol to use for SDL (Zmodem? Kermit? ASCII?) - network protocol to use (ftp, tftp, fsp, other?) - whether non 7 bit clean connections are important; ie if serial type connection takes a path over a telnet connection, should we be prepared to handle this, or is this a non-issue. Theres a trade off of speed and code space in order to support this sort of thing. - what do you dislike about the current implementation? Thanks alot. -John jlacour@usr.com End of USRTC Digest - 18 Nov 1995 to 27 Nov 1995 ************************************************ From POP3server Thu Nov 29 19:47:26 GMT 1995 X-UIDL: 4a3cbaa75c495da9098edc0e73e69d6d Return-Path: rjkopp@mailbox.syr.edu Received: from syr.edu (syr.EDU [128.230.1.49]) by mailbox.syr.edu (8.7.1/8.7.1) with SMTP id OAA28599 for <rjkopp@mailbox.syr.edu>; Wed, 29 Nov 1995 14:43:43 -0500 (EST) Received: from mailbox.syr.edu by syr.edu (8.6.9/CNS) id OAA26258; Wed, 29 Nov 1995 14:44:07 -0500 Received: from wraith.syr.edu (rjkopp@wraith.syr.edu [128.230.4.44]) by mailbox.syr.edu (8.7.1/8.7.1) with SMTP id OAA28586 for <rjkopp@syr.edu>; Wed, 29 Nov 1995 14:43:41 -0500 (EST) Received: by wraith.syr.edu (5.x/Spike-2.0) id AA27807; Wed, 29 Nov 1995 14:43:08 -0500

I've never posted this issue before but I thought I really needed to. I've not handled too many lists before and I've never handled the mail errors before, at least not successfully. With any list, periodically mail problems develop, they create alot of problems for the listserv manager, for the listserv group manager (me) and sometimes system administrators, particularly if they happen to be the same people who manage listserv. So these people don't like it when listowners such as myself let these go too long. My policy on these is that I will delete you from the list, but using the address you are subscribed with I will also try to advise you in case the listserv system is having problem but mail protocols aren't. Sometimes unknown to you, your system manager may change the way mail is handled, or you may not know it but your mailer puts your machine address in the mail message and then when your system is shutdown it cannot reach you. There are many reasons some of which unfortunatly are beyond me. That is why I will try to send you something. If I get a reply back from you and the address is the same I will try to re-instate you, in case it was a temporary problem. If it recurs I will probably send you copies of the messages I get and ask you to forward it to your postmaster at your site and ask you to work with him to find the error in it. So if one day you realize you are not getting messages (I know this list is not real active, so see later on), email me and ask me if I could re-subscribe you and tell me that you used to be on but all of a sudden stopped getting mail. If you want to find out if you are still subscribed, send email to listserv@listserv.syr.edu and put the following line in the body. And don't put anything else: review usrtc It will return two messages, one telling you how much time it took to process your request and in a separate message it will give a list of the subscribers, you should find your name in this, if not, chances are some problem has occured and I had to delete you and my mail to you to let you know failed. So you may want to hold on to this message to find out what to do, how to tell and for my email address. I know this can be a real pain, but I don't know any easier way. Thanks, Ray Kopp Syracuse University CMS, Network Systems rjkopp@mailbox.syr.edu OWNER: USRTC@listserv.syr.edu (US Robotics Total Control Product)

John, Thanks for asking for comments. I use a Macintosh portable so I would like something that would work with it. The network protocol does not help since my modems are not managed. If you implement the update using a standard protocol like zmodem or kermit, then I think the Macintosh is covered. It is pc only. The solution should also include Macintosh and UNIX. Again, thanks for the opportunity to comment. Butch At 15:56 11/27/95, John LaCour wrote: * We're investigating an improved SDL procedure and would be interested in * feedback from users. * * Please send me email with any comments you have. * * In particular, we'd like to get feedback on: * * - direct serial protocol to use for SDL (Zmodem? Kermit? ASCII?) * - network protocol to use (ftp, tftp, fsp, other?) * - whether non 7 bit clean connections are important; ie if serial type * connection takes a path over a telnet connection, should we be prepared to * handle this, or is this a non-issue. Theres a trade off of speed and code * space in order to support this sort of thing. * - what do you dislike about the current implementation? * * * Thanks alot. * * -John * jlacour@usr.com Butch Kemper | Free sound advice available Brazos Information Highway Services | "95% sound and 5% advice" 409-693-9336 | Refunds cheerfully provided

I have a USR TC Rack with V.32bis Dual Analog cards install, some which have been upgraded to V.34. I have a couple of questions: 1. I have acquired two RM V.32bis/2 with ASL cards along with the interface cards. Is there any problem with installing these cards in my existing rack? It appears they can be installed. What is the most current software/hardware level for these cards? 2. What is the status of the V.34+ upgrade for the V.34 Dual Analog Cards? Thanks for any help. Butch Butch Kemper | Free sound advice available Brazos Information Highway Services | "95% sound and 5% advice" 409-693-9336 | Refunds cheerfully provided End of USRTC Digest - 27 Nov 1995 to 28 Nov 1995 ************************************************ From POP3server Tue Dec 4 05:20:27 GMT 1995 X-UIDL: 0fe4f4a99a4665a4debb0ac6712254ff Return-Path: owner-USRTC@LISTSERV.SYR.EDU Received: from tnt.syr.edu (tnt.syr.edu [128.230.4.245]) by mailbox.syr.edu (8.7.1/8.7.1) with ESMTP id AAA10411 for <rjkopp@MAILBOX.SYR.EDU>; Mon, 4 Dec 1995 00:04:18 -0500 (EST) Message-Id: <199512040504.AAA10411@mailbox.syr.edu> Received: from listserv.syr.edu (128.230.1.252) by tnt.syr.edu (LSMTP for Windows NT v1.0a) with SMTP id 3F3DCA90 ; Mon, 4 Dec 1995 0:05:40 -0500 Reply-To: US Robotics Total Control Product <USRTC@LISTSERV.SYR.EDU> Sender: US Robotics Total Control Product <USRTC@LISTSERV.SYR.EDU>

There are 4 messages totalling 192 lines in this issue. Topics of the day: 1. Software Download, the next generation... (2) 2. Mail delivery problems 3. Rack Mount Modem Questions

On Mon, 27 Nov 1995 15:56:04 CST, you wrote: >We're investigating an improved SDL procedure and would be interested in >feedback from users. Fine, that the customers are asked :-) > >Please send me email with any comments you have. > >In particular, we'd like to get feedback on: > >- direct serial protocol to use for SDL (Zmodem? Kermit? ASCII?) ASCII? John!!! That's a joke? Isn't it? What would the programmers say to that? But Kermit and Zmodem would be fine!!! Even for portability for all this other plattforms around. >- network protocol to use (ftp, tftp, fsp, other?) ftp, tftp would be hard for non-managed modems, so it should be ONE sdl for all devices, including the Couriers. Otherwise you will have more software to support.... >- whether non 7 bit clean connections are important; ie if serial type > connection takes a path over a telnet connection, should we be prepared to > handle this, or is this a non-issue. Theres a trade off of speed and code > space in order to support this sort of thing. >- what do you dislike about the current implementation? The only REALLY stupid thing on this SDL is, that it's the PC-SDL :-(, so all we IX-users have to disconnect the modems, and > > >Thanks alot. > >-John >jlacour@usr.com You're welcome! Holger -- Expressed opinions are mine and not necessarily those of MMS. Holger Koepke U.S.Robotics tel.: +49 40 211105-0 Eiffestr.598 Distribution fax : +49 40 21032210 20537 Hamburg holger@mms.de Germany MMS GmbH http://www.mms.de/~holger ->->->->->->->->->->->->->-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-

another tc user or going to be, at least another contact for dialups Rick Masselle from Connecticut State University Presently have 48 ports at each of 4 university locations. Was calling with questions about tacacs authentication and our feelings about it and the USR Total Control Product masselle@csu.sys.ctstateu.edu (203) 832-0127 From POP3server Thu Nov 29 05:14:52 GMT 1995 X-UIDL: be3c1a7d496345101c417e301abd7277 Return-Path: owner-USRTC@LISTSERV.SYR.EDU Received: from tnt.syr.edu (tnt.syr.edu [128.230.4.245]) by mailbox.syr.edu (8.7.1/8.7.1) with ESMTP id AAA04361 for <rjkopp@MAILBOX.SYR.EDU>; Wed, 29 Nov 1995 00:05:36 -0500 (EST) Message-Id: <199511290505.AAA04361@mailbox.syr.edu> Received: from listserv.syr.edu (128.230.1.252) by tnt.syr.edu (LSMTP for Windows NT v1.0a) with SMTP id 8671EFF0 ; Wed, 29 Nov 1995 0:06:26 -0500 Reply-To: US Robotics Total Control Product <USRTC@LISTSERV.SYR.EDU> Sender: US Robotics Total Control Product <USRTC@LISTSERV.SYR.EDU>