Re: Back-end network
- From: Muson <Muson@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 25 Jul 2008 01:33:00 -0700
Em,
thanks, i deleted network that i just created, and added 172.16/16 to
internal network IP ranges.
added static route, and it works :)
p.s. i not mentioned but my external nic is connected to internet, and it is
not in same subnet...
--
Muson
"Jim Harrison (ISA SE)" wrote:
The first problem you have is using the same subnet on the internal and.
external NICs (192.168.1/24) .
They *MUST* be on separate subnets or ISA cannot function as a firewall.
The second problem you have is creating a new network to represent the
172.16/16. Delete this.
Have a read here:
http://www.isaserver.org/tutorials/Advanced-ISA-Firewall-Configuration-Network-Behind-Network-Scenarios.html
--
Jim Harrison (ISA SE)
This posting implies no warranty and confers no rights.
http://catb.org/~esr/faqs/smart-questions.html
"Muson" <muson@xxxxxxxx> wrote in message
news:eC93mka7IHA.5024@xxxxxxxxxxxxxxxxxxxxxxx
Hi,
I have ISA 2006, two NICS, external and internal with
(192.168.1.0-192.168.1.255).
In LAN i also have another router with IP 192.168.1.50 and network behind
this router (back-end network) (172.16.0.0-172.16.255.255).
So idea is, if LAN computer ( 192.168.1.20) want to comunicate with
(172.16.1.15) it will forward request to gw 192.168.1.254 (ISA internal IF
IP).
I created new network, network rule and access rule, so i should add static
route to ISA, that
172.16.0.0 mask 255.255.0.0 gw 192.168.1.50 ?
I see in some forums that i should put route gateway 192.168.1.254 and not
192.168.1.50, but i don't understand how will ISA know where to find
172.16.0.0/16 network?
--
Muson
- References:
- Back-end network
- From: Muson
- Back-end network
- Prev by Date: Back-end network
- Next by Date: Re: 995 The I/O operation has been aborted because of either a thr
- Previous by thread: Back-end network
- Index(es):
Relevant Pages
|