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

Utm9 Two Dİfferent Ip Pools Doesn't Communİcate

Hi,

I have two different dhcp pools, normally two of them are communicating and there is no problem here. But when I connect to a point outside my 192.168.1.11 ip computer with a different VPN, I can connect to block 192.168.1, but I cannot connect to block 192.168.2.

What am I supposed to do about it? thank you for your help.

This thread was automatically locked due to age.

Parents

0 dirkkotte over 5 years ago

sorry, but i don't understand "But when I connect to a point outside my 192.168.1.11 ip computer with a different VPN".

If you use VPN make sure the Subnet 192.168.2.0/24 is included in Tunnel definition too.

next check the firewall rules.

Dirk

Systema Gesellschaft für angewandte Datentechnik mbH // Sophos Platinum Partner
Sophos Solution Partner since 2003
If a post solves your question, click the 'Verify Answer' link at this post.
Cancel
Vote Up 0 Vote Down

Cancel
0 Kenan ASKUNGU over 5 years ago in reply to dirkkotte

can you watch the video?

https://www.youtube.com/watch?v=wyA7TXN4XxA&feature=youtu.be
Cancel
Vote Up 0 Vote Down

Cancel
0 dirkkotte over 5 years ago in reply to Kenan ASKUNGU

i would think your pc is unable to reach the 192.168.2.x subnet if VPN is established.

possible the VPN use a "catch all" route.

show us the PC routing table while VPN is connected...

"route print"

Dirk

Systema Gesellschaft für angewandte Datentechnik mbH // Sophos Platinum Partner
Sophos Solution Partner since 2003
If a post solves your question, click the 'Verify Answer' link at this post.
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 dirkkotte over 5 years ago in reply to Kenan ASKUNGU

i would think your pc is unable to reach the 192.168.2.x subnet if VPN is established.

possible the VPN use a "catch all" route.

show us the PC routing table while VPN is connected...

"route print"

Dirk

Systema Gesellschaft für angewandte Datentechnik mbH // Sophos Platinum Partner
Sophos Solution Partner since 2003
If a post solves your question, click the 'Verify Answer' link at this post.
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 Kenan ASKUNGU over 5 years ago in reply to dirkkotte
Cancel
Vote Up 0 Vote Down

Cancel
+1 dirkkotte over 5 years ago in reply to Kenan ASKUNGU

With VPN you got a new default gateway (10.20.30.80) with a better metric than the old GW.

So your traffic to 192.168.2.0 is send to the tunnel.

a possible solution is a manual route ...

route add 192.168.2.0 mask 255.255.255.0 192.168.1.1

Dirk

Systema Gesellschaft für angewandte Datentechnik mbH // Sophos Platinum Partner
Sophos Solution Partner since 2003
If a post solves your question, click the 'Verify Answer' link at this post.
Cancel
Vote Up 0 Vote Down

Cancel
0 Kenan ASKUNGU over 5 years ago in reply to dirkkotte

Thank you! this worked!
Cancel
Vote Up 0 Vote Down

Cancel