|
I fixed the problem. I was connecting but I needed to add a WSE in QINTER for the device descriptions being created. Joel B. Harvell Food Lion, LLC (704) 633-8250 x2709 jbharvell@xxxxxxxxxxxx -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Brian Piotrowski Sent: Wednesday, April 19, 2006 4:46 PM To: Midrange Systems Technical Discussion Subject: RE: Telnet from a PC to Iseries Further to that - you may have reached the maximum amount of devices that can be created on the system (we had that problem last week - I had to go in and clean out all of the old devices). Check that you haven't exceeded that value. Brian. -----Original Message----- From: Tom Jedrzejewicz [mailto:tomjedrz@xxxxxxxxx] Sent: Wednesday, April 19, 2006 4:23 PM To: Midrange Systems Technical Discussion Subject: Re: Telnet from a PC to Iseries Some random thoughts ... -- check the Telnet attributes; perhaps only SSL is allowed -- command CHGTELNETA -- could be that autoconfig of virtual devices is disabled .. that is sometimes done when system admins are paranoid -- system value QAUTOVRT Good luck! On 4/19/06, Harvell, Joel <jbharvell@xxxxxxxxxxxx> wrote: > > A bit of additional information... > > I can see my IP address connect to the Iseries in question using the > NETSTAT command, but I never get a login screen. What am I missing?? > > -- Tom Jedrzejewicz tomjedrz@xxxxxxxxx
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.