Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 9 replies
  • Subscribers 1 subscriber
  • Views 1250 views
  • Users 0 members are here
Options
Suggested
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

routing problem to dmz of second firewall

toette
hello everybody,

i have to solve the following problem:

in our environment we have two firewalls which are connected to an internal lan (192.168.0.0/255.255.252.0). over fw1 (192.168.3.20) we get a roadwarrior connection (vpn) to the internal lan. the roadwarrior clients use the ip adress range 10.171.131.0/255.255.255.0. 
the second firewall, fw2, has a DMZ (192.168.12.48/255.255.255.248) and we want to reach systems there over special services (i. e. remote desktop client). 

we have already tried different routing rules on the fw1:

- static routing
- policy based routing
- to add a route manually at the connected client


can anybody help me please?

thanks 
toette


This thread was automatically locked due to age.
Parents Reply
  • 0 in reply to ClausP
    hello claus,

    i made the settings. now it is possible to ping from fw2 the virtual vpn ip 10.171.131.x.

    but i cannot connect to the dmz. i already tried to change the tunnel endpoint from "internal network" to "Any" but no success. the autopacket filter is turned on. do you have another idea?


    thanks toette
Children
  • 0 in reply to toette
    hello everybody,

    i changed the subnet definition (optional): local subnet from internal network to any. after i was able to ping the device of the dmz i want to reach (192.168.12.49). 
    To get a remote desktop connection to the system standing in the dmz i created a dnat-rule. now everything works fine.

    thanks for your help clausp.

    cu
    toette
Cookie Information Banner