×
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.
Chris (and all),
I'm not sure I understand your suggestion. The firewall participates as a
host on ring/network 1, along with about 15 PCs and the AS400. The 5 or so
PCs that can't talk to the firewall (or any host on ring/network 1) exist
on ring/network 2, along with the NIC in the AS/400. If the PC's could
ping each other between networks, then I would already have it made.
I seem to remember at V4R5 that I was able to set data gram forwarding by
line, and able to use the AS/400 as a passive router. I have lost that
ability, though I don't know how or why.
Topology looks something like this:
-----------------
| |
| AS/400 | TR Card 1 (172.24.1.1) --> PC's --> Firewall
(172.24.1.10) --> More PCs
| |
| | TR card 2 (172.22.1.1) -------> PC's (172.22.***.***)
------------------
Is there something on the PC that needs to know about the other
network? Something in the hosts file? Or entries in the DNS on the AS/400
to point to the firewall?? I know that TR Cards need to know about each
other and have a path to forward traffic.
I have done this before on this machine at an earlier release. What a pain!
Thanks for your suggestions - any more??
At 01:12 PM 5/23/2003 -0700, you wrote:
Sounds like your default route on the PC that are directly connected to the
firewall side does not have a route back to your second network on the as400
side. So the firewall need to know about the 172.22.x.x subnet with a hop
of your as400 on the 172.24.x.x network.
Chris Bipes
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.