From: San Francisco
I have a three legged TMG with an Internal network, and external network and a perimeter network all on separate network interfaces. Very normal.
I have servers in the perimeter network and layer 3 works to all these servers; Exchange mailboxes are accessible using Outlook everything works EXCEPT webservers!
Users located on the Internal can access resources Exterior web sites but can't access servers located in the perimeter.
Using the FWC it doesnít work Not using the FWC it doesnít work
It looks like TMG tries to send all HTTP out no matter if I tell it on the internal interface to bypass TMG
But I donít really want to bypass TMG right? I need TMG to ďrouteĒ the http traffic request from Internal clients through the perimeter Interface just like it does when a trace or a ping (remember Layer 3 works).
I understand that in a TMG that has only and Internal and an External how to configure the Internal Network to handle local servers, but what settings do I place on the perimeter network config in TMG so a three legged TMG understands how to forward all HTTP traffic from the Internal and through the perimeter to reach the web servers?
I don't need to publish them do I?
Thanks for responding
< Message edited by Stevenrlong -- 7.Mar.2012 5:22:14 PM >
Why you must configure 25 IP addresses on same NIC? I don't know in what you host your web applications, but I think you can deal this with web servers? There is no need to set 25 different IP's... and if you didn't believe me, try to publish one site and if this work - this is the right way :) Other thing you must pay attention - Internal <-> DMZ must be set on Routing, because if you set to NAT, you may have some troubles, if your servers are part of same domain etc.