|
Hey! Now that idea has possibilities! I hadn't even considered that! I'm going to look into this. I'll keep you posted! Shannon O'Donnell ----- Original Message ----- From: "Fritz Hayes" <fhayes@spiritone.com> To: <midrange-l@midrange.com> Sent: Friday, August 31, 2001 11:11 AM Subject: RE: Telnet Server > Hey Shannon, > > Here's a crazy thought: Maybe you can use the AS/400s Network Address > Translation (NAT) to map telnet requests from a known network (say > 172.16.2.0) to use a different IP Port for telnet sessions?! Does this > fit what you are trying to do? > > Best Regards > > Fritz Hayes > Atwater Associates > 503-636-5914 > > > -----Original Message----- > > From: midrange-l-admin@midrange.com > [mailto:midrange-l-admin@midrange.com] > > On Behalf Of Shannon O'Donnell > > Sent: Friday, August 31, 2001 7:32 AM > > To: midrange-l@midrange.com > > Subject: Re: Telnet Server > > > > Thanks Simon! > > > > That's a lot more information than I had when I started down this > road! > > > > I may contact IBM about this, but since I need a solution to a problem > > immediately, it won't be anytime soon. I'll be spending my time now > > looking > > for an alternate way of doing what I need to do. > > > > Thanks for the info! > > > > Shannon O'Donnell > > ----- Original Message ----- > > From: "Simon Coulter" <shc@flybynight.com.au> > > To: <midrange-l@midrange.com> > > Sent: Thursday, August 30, 2001 11:37 PM > > Subject: Re: Telnet Server > > > > > > > M > > > Hello Shannon, > > > > > > I tested the information I sent earlier on VRM440 and found that it > no > > longer > > > works. As part of the architectural change to Telnet that occured > at > > 440 > > the > > > QTGSTART program (which is what gets called by STRTCPSVR *TELNET) > gets > > to > > see > > > if TELNET is currently active. It is not doing that by checking the > > port > > > however I haven't bothered trying to find out what it does check. > > QTGSTART > > > sends TCP1A04 - "Telnet currently active" if it finds Telnet is > already > > > running. > > > > > > The nett result is that on 440 and later releases only one instance > of > > TELNET > > > can be active. That single instance can (and does) listen on > multiple > > ports > > > but they haven't written it to handle more than one port per service > > name. > > > They probably just use getservbyname() which returns the first entry > > with > > the > > > requested name and protocol from the SERVICES table. That approach > is > > > reasonable and consistent with most TCP applications. You could > raise a > > DCR > > > and request they use getservent() and then they could process all > the > > entries > > > in the SERVICES table. I notice that TELNET uses accept() rather > than > > the > > more > > > useful select() so they would have a bit of work to implement > multiple > > servers. > > > > > > Regards, > > > Simon Coulter. > > > > > > <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> > > > <> FlyByNight Software AS/400 Technical Specialists <> > > > <> Eclipse the competition - run your business on an IBM AS/400. <> > > > <> <> > > > <> Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 /"\ <> > > > <> Fax: +61 3 9419 0175 mailto: shc@flybynight.com.au \ / <> > > > <> X <> > > > <> ASCII Ribbon campaign against HTML E-Mail / \ <> > > > <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> > > > _______________________________________________ > > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) > mailing > > list > > > To post a message email: MIDRANGE-L@midrange.com > > > To subscribe, unsubscribe, or change list options, > > > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > > > or email: MIDRANGE-L-request@midrange.com > > > Before posting, please take a moment to review the archives > > > at http://archive.midrange.com/midrange-l. > > > > > > > _______________________________________________ > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > > list > > To post a message email: MIDRANGE-L@midrange.com > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > > or email: MIDRANGE-L-request@midrange.com > > Before posting, please take a moment to review the archives > > at http://archive.midrange.com/midrange-l. > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.