|
![]() |
|
| Author |
|
|||||||
|
TicMan
Posts: 2056
Location: Brisbane, Queensland
|
f*** I hate this piece of s*** product but alas I have to use it because IT management in the US want us to have a "follow-the-sun" approach to supporting our infrastructure so here I am lumped with this f*** up of a product trying to get it to do something *insanely* basic.
I have a DMZ (10.10.10.0/24) which is routable via 192.168.1.254 and the ISA server is on 192.168.1.1. The second NIC on the ISA box is connected to an internet service and this is set as the default gateway. I've created a static route for 10.10.10.0/24 to route via 192.168.1.254, created an ISA rule to allow traffic between "Local Host" and "DMZ" (DMZ defined as 10.10.10.0 -> 10.10.10.255) for all protocols yet the piece of s*** firewall f*** is blocking the traffic. ISA monitoring reports the error as "0xC004002D FWX_E_UNREACHABLE_ADDRESS" and I've googled around but can't find anything useful. No traffic ever hits the router (192.168.1.254) so the data isn't even leaving ISA. To add to how mentally f***ed ISA is as a product, if I add the 10.10.10.0/24 range to the "Internal" network then everything runs peachy.. unfortunately since it's a DMZ I can't leave it in this network as that's just no cricket. Any ISA gurus able to lend a hand? |
|||||||
| #0 11:29am 18/05/07 |
|
|||||||
|
system
|
--
|
|||||||
| #0 |
|
|||||||
|
system
|
--
|
|||||||
| #0 |
|
|||||||
|
| ||||||||