Hello everyone,

Again with another TMG2010 problem, actually not a problem , a dilemma .

Attached is our network diagrams, please don't ask why the network design is really stupid but we have to do it like this temporarily (several sites,links and stuff) also the network addresses are just for explanation.

Bottom line, we have a TMG2010 in the same address pool as the Users, who are using the TMG's web proxy to access the internet.
The TMG is set as an EDGE firewall, the internal NIC have an ip in the users ip address space, and the external NIC have a public IP address
I've set the gateway on the external NIC to be the internet gateway, and removed the gateway of the internal NIC (typical EDGE firewall design)  
The problem is that the domain controller is on a third network ( ,so TMG can't reach it to do the users authentication (integrate windows domain authentication).

Simple explanation: When the user opens internet explorer (TMG is set as a proxy in it), the authentication dialog box appears, and of course will not work if i entered my user and password because TMG will not be able to see if they are correct because it can't reach the DC.

so the best way to explain this is how to let TMG reach the domain controller ?

sorry about the crappy diagram and explanation
Thank you in advance.

asked 12/07/2011 10:34

a77's gravatar image

a77 ♦♦

4 Answers:
The default gateway on the TMG extyernal nic needs to be the ip address of your external router (yours or the ISP's router).
On the TMG, add a static route either in the networking - routing tab of the gui or from a DOS/command line.

from your example,

c:\route -p add 10-10.10.0 mask

Also, make sure that the - entry is added to the list of internal IP addresses in the TMG gui
(networking - networks - internal - addresses)


keith_alabaster's gravatar image



Nothing stupid in your network diagram and your case is absolutly common case.
As you have done, the TMG server must have only a default gateway declared on the external NIC, not on the internal one. That's good.

Now, you only have to manually add static IP routes for all your internal networks.
Instead of identify each IP subnet inside your network, and as private IP ranges can never exist on internet, you can declare the 3 static IP routes for the 3 private IP ranges (, and
On your TMG server, open a CMD console (open it as administrator).
In the CMD prompt type the following to add the static IP routes:


Have a good day

answered 2011-12-08 at 10:26:55

PaciB's gravatar image


Thank you very much guys, appreciate it

answered 2011-12-08 at 10:32:55

a77's gravatar image


Welcome :)

answered 2011-12-11 at 00:22:10

keith_alabaster's gravatar image


Your answer
[hide preview]

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments



Asked: 12/07/2011 10:34

Seen: 393 times

Last updated: 12/10/2011 04:22