×
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.
What is throwing me a curve right now is the access to 10.0.10.230
(ONLY) from the 192.168.1.0 network. There are no rules to allow to it
implicitly. This is a Watchguard Firewall and the 10.0.10.0 network is
defined as "Trusted" and the 192.168.1.0 network is defined as "Trusted"
as well. There is a firewall rule that allows all "Trusted" networks to
access each other on any IP or port. That rule alone should allow the
two networks to communicate (in theory). Why only 10.0.10.230 is
accessible is still a mystery.
Pete Helgren
www.petesworkshop.com
GIAC Secure Software Programmer-Java
On 1/15/2013 3:29 PM, Chris Bipes wrote:
There will need to be access rules on the firewall to allow access to each IP and Port from one firewall interface to another firewall interface. Get your firewall tech involved as all the traffic must flow through the firewall.
-- Chris Bipes Director of Information Services CrossCheck, Inc.
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
