×
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.
All,
Thank you all for being patient with me. I have achieved the goal, and
network 2 can now see the firewall, ping it, and get to the internet. The
key was that there needed to be a route to get back to the 2nd network. I
added a route from the firewall pointing all traffic for 172.22.***.*** to
the 172.24.1.1 address of the 400. The 400 then passes the traffic on to
the correct network.
The point I was not getting (until it was pounded into my brain) was that
the traffic had to have a route back. You would think that if it know how
to get there, it would be able to come back the same way!
Anyway, the issue is resolved, and I thank you all for your input.
Signed, a now more network knowledgeable COBOL programmer.
----------------------------------------------------------
Jim Essinger
Senior Programmer/Analyst
Student Loan Fund of Idaho
6905 Highway 95
Fruitland ID 83619
or
PO Box 730
Fruitland, ID 83619
208-452-4058 Extension 133
esinger@xxxxxxxx
------------------------------------------------------------
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.
midrange.com
