×
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.
On 4/20/12 4:58 PM, Pete Helgren wrote:
I CANNOT hit the internal address for the HTTP and Tomcat server on the
IBM i. In fact, trace route can't find the host. That pretty much
indicates a routing issue (I think) with the i.
I believe the routing information of the *origin* device is used - not
the destination. i.e. if you can't get *from* the Mac *to* the IBM i -
the Mac's routing information seems suspect, not the IBM i's.
The IBM i's routing information would come into play when you're trying
to get *from* the IBM i *to* the Mac. "ping"ing the Mac's I/P address
from the IBM i might be a useful datapoint... Be aware in the Mac
Firewall settings there is a "stealth mode" that, if enabled, will
prevent the Mac from responding to a ping - so you'd want that off when
you try to ping the Mac.
From the Mac, can you ping the *router* in between the Mac and the IBM i?
You're sure there isn't a firewall in front of the IBM i that
blocks/allows incoming traffic based on source I/P addresses?
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
