Cannot access subnet routed via internal NIC
-
Wednesday, April 11, 2012 9:51 AM
Hi all,
I've TMG with three NICs (External, WiFi, and internal network).
We have additional test subnet accessible via router in internal network. I'd like to access to this subnet from VPN connection, so I created the following:
- new Network with the appropriate network range (192.168.102.0-192.168.102.255) as internal network, and with name 'Test network'
- new Network Rule with VPN Cliens as source and 'Test network' as destination with Route relationship
- new Network Topology Route with 192.168.102.0/255.255.255.0 as destination, 192.168.100.9 (router in internal network) as gateway, and 1 as metric.
- new Subnet (Network Object) for 192.168.102.0/24 with name 'Test subnet'.
- new Access Rule with 'VPN Clients' as From and 'Test subnet' as To.
After applying the changes above the communication to the test subnet is not working with error 0xc004002d (A packet was dropped because its destination IP address is unreachable). There is 'Initiated connection' in log before the error, so I assume the Access Rule is correctly defined, however there is some routing problem.
I know I can add the test subnet to the Internal network and it will be working, however I do not want to do that - we have defined some access rules for Internal network and those must not be applied to the test subnet...
What am I missing?
Thanks!
R.*
- Edited by Radovan Vojtek Wednesday, April 11, 2012 9:52 AM
All Replies
-
Thursday, April 12, 2012 6:38 AMModerator
Hi,
Thank you for the post.
If the subnet is not directly connect to TMG internal NIC, you have to add them to the internal network.
Regards,
Nick Gu - MSFT
- Marked As Answer by Radovan Vojtek Thursday, April 12, 2012 6:50 AM
-
Thursday, April 12, 2012 6:50 AM
Oh, I was afraid of that... :(
However, thanks answer and make me sure!
Ragards,
R.*
- Edited by Radovan Vojtek Thursday, April 12, 2012 6:50 AM

