|
OK...I got the *SAMEPRF working now. The only thing I did differently was to use an internal IP address (direct connect between the V5R2 and V5R1 systems) rather than an external IP address (one that went through our router). Using the internal IP I can do transparent logon's between V5R2 and V5R1. Using the external IP, going through our router, I cannot. So...time to contact our ISP, since they control our router (we don't have access to change it at all), and try to figure out what's going on. Thanks for the responses on this. Shannon O'Donnell ----- Original Message ----- From: "Carsten Flensburg" <flensburg@xxxxxxxxxx> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Friday, April 11, 2003 10:31 AM Subject: Re: V5R2 - QRMTSIGN Problem > Hello Shannon, > > I experience the same behaviour as you do when telnetting from my V5R1 to > V5R2 machine - but as I read the telnet command helptext *SAMEPRF is treated > the same way as *VERIFY - here's what it says: > > "If you are connecting to an AS/400 TELNET server, then the QRMTSIGN system > value must be set to *SAMEPRF or *VERIFY. For TELNET, the *SAMEPRF setting > is treated the same as the *VERIFY setting because the TELNET server only > receives the user profile name specified on the STRTCPTELN command. It does > not receive the user profile name of the job using the STRTCPTELN command > and cannot enforce the profiles being the same on both systems." > > Best regards, > Carsten Flensburg > > ----- Original Message ----- > From: "Shannon O'Donnell" <sodonnell@xxxxxxxxxxxxxxx> > To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> > Sent: Friday, April 11, 2003 4:41 PM > Subject: Re: V5R2 - QRMTSIGN Problem > > > > John, > > > > Both of my systems (V5R1 and V5R2) are set to use 10 character passwords. > > As far as I can tell, both systems have exactly the same settings for > System > > Security Values. > > > > *SAMEPRF still doesn't work.....wonder if this is an undocumented > "feature" > > of V5R2? > > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > 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.