This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Policy Routing With Dual WANs

support@computer-ss.com over 16 years ago

I followed the instructions in this KB article 236926. My problem is that my DMZ cant talk to my internal network and my internal network cant talk to my DMZ. What do I need to do to fix that? Other than that the article works as advertised. Any input would be appreciated.

Thanks

This thread was automatically locked due to age.

Parents

0 BAlfson over 16 years ago

The article doesn't address the issue of enabling access by the internal network to the DMZ. You probably don't want the DMZ to have free access to your internal network - otherwise, why have a DMZ at all?

Try How to access a webserver in the DMZ from the internal network via the public IP or hostname (215522)

Good luck - Bob
Cancel
Vote Up 0 Vote Down

Cancel
0 support@computer-ss.com over 16 years ago in reply to BAlfson

otherwise, why have a DMZ at all? agree, I just need to allow SSL access to a database, I don't intend on opening up all ports.

I don't really care if my DMZ uses WAN1 as its gateway, as long as it can answer requests from WAN2 and send those reply's back out WAN2. But from what I read it cant do this without an additional policy route.
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 support@computer-ss.com over 16 years ago in reply to BAlfson

otherwise, why have a DMZ at all? agree, I just need to allow SSL access to a database, I don't intend on opening up all ports.

I don't really care if my DMZ uses WAN1 as its gateway, as long as it can answer requests from WAN2 and send those reply's back out WAN2. But from what I read it cant do this without an additional policy route.
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data