Welcome to ISAserver.org

Problems with Perimeter access

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2004 Firewall] >> DMZ >> Problems with Perimeter access

Page: [1]

Message

<< Older Topic Newer Topic >>

Problems with Perimeter access - 1.Sep.2006 12:29:29 AM

cgonzaleznts

Posts: 5
Joined: 31.Aug.2006
Status: offline

Hi ,

I am having many difficulties putting to work my Perimeter.

I followed Tom’s article about Front-end and Back-end in a trihomed system.

Configurations:

ISA – Internal             10.44.56.6       255.255.254.0
            Perimeter          172.16.0.1       255.255.0.0
            External            x.x.x.x              x.x.x.x             GW x.x.x.x

Perimeter PC – 172.16.0.2      255.255.0.0     GW-172.16.0.1

Internal PC – 10.44.56.2          255.255.254.0

I have created my perimeter network and my internal network in my ISA under the configuration ( Network)
Authenticated DMZ = 172.16.0.0 – 172.16.255.255
Internal Network = 10.44.56.0 – 10.44.57.255

I also have created the network rule in my ISA under the configuration (Network Rules)
Source Network = Authenticated DMZ
Destination Network = Internal
Route

Source Network = DMZ
Destination Network = External
Nat

After creating all this, I wanted to verify the connectivity between networks. I proceed to ping my external, internal and perimeter from my ISA server and everything went just fine. As result of that I wanted to test the communication between the perimeter computer and the internal network. So, I created an access rule allowing the ping protocol.
Protocol = Ping
Source Network = Perimeter
Destination Network = Internal

However, when I tried to do the ping with the perimeter computer I could not ping any of my internal network.

Am I doing something wrong? Please I need help ASAP. I would appreciated.