Phillip,
Another comment about WatchGuard Firebox.
The I/Fs are a data flow layered protocol that is derived from 'Trusted'
being the center. All I/Fs have to be a subnet. Data flows as follows:
Incoming - external (T1) - eth4 - eth3 - eth2 - eth1 - eth0(trusted) -
outgoing - eth0 - eth1 - eth2 - eth3 - eth4 - external.
By default, the Firebox will NOT allow any data flow incoming. Only
outgoing. The users must add a service to allow any incoming data and specify
'Any' to allow all traffic or customize to specific data flow.
I still have not been able to achieve a secondary domain controller across
the subnets. For those considering WatchGuard, consider these issues and
their support group closely.
Any having any suggestions as to HOW to work across this firewall. Please
advise. Thanks.
"Chappydean" wrote:
> The X2500 I/F's are routed I/Fs.
>
> Secondly, the DNS server on eth1 will be setup as a public web server and
> will be firewall isolated from the trusted network.
>
> The DNS now is working on the eth1 subnet. Still working with the domain
> controller issues.
>
> "Phillip Windell" wrote:
>
> >
> > "Chappydean" <(E-Mail Removed)> wrote in message
> > news:E85C32A9-567D-487C-BB89-(E-Mail Removed)...
> > > Additional to my last post, I would like to set up a secondary DNS server
> > on
> > > the X2500 I/F 'eth1'. But in order to do so I must be able to transfer
> > zones
> > > from the master which is on the main subnet. Can ping only, not access.
> >
> > Why are you making it 10 times harder and more complicated than it needs to
> > be? the Watchgaurd box should not have anything to do with your DNS and how
> > the DNS works.
> >
> > --
> >
> > Phillip Windell [MCP, MVP, CCNA]
> > www.wandtv.com
> >
> >
> >