Thanks Chris and Rob for your help.
Finally got back to this and your suggestions were helpful.
Got everything setup correctly but still had issues.
After another day messing with it and by chance found that
someone had placed (restored) a program compiled four years
ago into QGPL Augghhhh!
The program has been changed numerous times in the past 4
years, deleted it and works like a champ.
Of course nobody will claim credit for this great idea!!
Looking through QGPL found other application programs in
QGPL, what's with people putting application programs in
Now time to go clean up QGPL
From: Chris Bipes [mailto:chris.bipes@xxxxxxxxxxxxxxx]
Sent: Wednesday, August 20, 2014 6:46 PM
Subject: RE: Getting error A Route to the Remote Host is Not
You have not told your iSeries how to get from 192.168.99.x
to the 10.x.x.x subnet. You need to add the router that
sits on the 192.168.99.x network and connects to the
When you manually telnet are you doing from your PC or from
a Telnet session on the iSeries?
Best to look at your PC. From a command prompt type
ipconfig and see if your IP is on the 192.168.99.x subnet.
If it is, the default gateway from your PC should be entered
into your iSeries.
Director of Information Services
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On
Behalf Of John Allen
Sent: Wednesday, August 20, 2014 3:37 PM
Subject: Getting error A Route to the Remote Host is Not
We have been running this program for a long time and it has
been working fine
We just installed a new system with 7.1
I think I have configured everything on the new machine the
same as the old machine
When I run the program and it tries to connect tour Exchange
Server on port 25 I get CPE3429 "Route to Remote Host is Not
I thought this had to do with the
I reviewed the setting for CFGTCP
1. TCP Interfaces has 127.0.0.1 255.0.0.0
192.168.99.1 255.255.255.0 ETHEG *ELAN
(The line ETHEG is active)
2. TCP/Routes has *DFTROUTE *NONE
where 10.0.0.xxx is our Layer 3 switch which all our clients
and servers connect to and 10.0.0.xxx also has the necessary
routes to all interfaces internal and external
What am I missing here?
Any help would be greatly appreciated
Also, I can manually telnet to the exchange server fine
This is the Midrange Systems Technical Discussion
(MIDRANGE-L) mailing list To post a message email:
MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting,
please take a moment to review the archives at