Hi All,

Hoping someone can help me solve this problem as my TMG knowledge isn't the best and I'm struggling with this problem. I'll try my best to explain as it's quite a complicated setup.

I have a hyper-V host which has 3 NICS in. The first NIC has the IP 192.168.0.20 and is used for RDP management of the Hyper-V host. The other 2 NICS are teamed with the IP 192.168.0.21 and are used for my iSCSI LUN's which reside on my NAS.

I have a test Domain which has the IP range 192.168.2.1 - 192.168.2.254. I also have a stand alone workgroup member VM which runs TMG 2010 and is used to forward on traffic from the 192.168.0.1 to the 192.168.2.1 subnet. The TMG server has a NIC which sits on 192.168.0.23 and another which is the Gateway for all the test Domain Servers (192.168.2.1)

I am currently testing Veeam. Veeam is installed as a virtual machine on the test Domain with a 192.168.2.* address. I need to be able to resolve machines on the 192.168.0.* from this vm so I can add the Hyper-V box into Veeam to backup the vm's.

I can browse both the 192.168.0.* and 192.168.2.* networks from the TMG server. However I cannot browse the 192.168.0.* network from the Veeam Server. I have tried creating a network through TMG for 192.168.0.1 - 192.168.0.254, also a network rule to route traffic from the 192.168.2.* network to 192.168.0.*. I have then created a Firewall Rule to allow all traffic from the Internal Network to the Network created earlier. However this has not worked. Can anyone advise where I can going wrong?

Regards,

Matt

Hi,

What's the error in TMG logging?

Please use network monitoring tool to capture the traffic on Veearm Server and TMG server and analyze the trace.

Joyce