×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Have you tried basic networking tasks? Is the PC on the same subnet as
the server? If not, is there a firewall or ACL's on the router between
the client and server? Is the iSeries in your DNS/WINS servers? Have
you tried to just ping your iSeries and use a basic telnet client to
connect? On the iSeries, verify what IP address and port your Telnet
server is listening on and did you configure SSL for telnet. Perhaps
your PC client is trying SSL and that is not running on port 992
Chris Bipes
Director of Information Services
CrossCheck, Inc.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Massiello
Sent: Wednesday, August 12, 2009 8:19 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Client Access Connectivity and Telenet
Rob,
All good info like the others, but no. There were no messages
in
QSYSOPR. QINTER is running, and I can telnet on the console back to
itself,
and the new device does come up in QINTER.
CRTDEVDSP is on the machine, and I can prompt the command.
As an Amazon Associate we earn from qualifying purchases.
This thread ...
Re: Client Access Connectivity and Telenet, (continued)
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.
midrange.com
