×
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.
Yes, I concur with Patrick. There's no route to
yourclientibmilpar.yourclient.com:22 ... the firewall quite reasonably
says, "Direct SSH access from the public internet? Don't make me laugh!"
You need VPN access.
Often when Mordac the Preventer of Information Services *gives* you VPN
access, it's only to a *jump box*.
In that case, you log into the VPN and use ssh port redirects like ssh
-Lyourclientsjumpbox:2022:yourclientsibmlpar:22 you@yourclientsjumpbox
After that, ssh -p2022 you@yourclientsjumpbox gets you to port 22 on the
IBM i LPAR
On Tue, Jul 19, 2022 at 4:12 PM Patrik Schindler <poc@xxxxxxxxxx> wrote:
Hello James,
Am 19.07.2022 um 23:01 schrieb James H. H. Lampert via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx>:
What exactly means "didn't work"? What was the error message you have
been faced with?
It just sat there.
Sounds indeed like a Firewall, just throwing away your requesting packets
and not actively refusing your connection attempt.
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
