Limiting bandwidth of workstations in MS Forefront TMG

I just had the same problem and found errors in the log that the trust relationship between AD and the TMG host was broken. It turned out to be a DNS problem as I also had DNS entries on the external NIC. Just make sure to have only one DNS entry to the AD server on the internal NIC. That solved the problem for me.

There's no comparison because they're really two totally seperate products that are aimed at two different markets. Kind of how you'll probably never see a comparison of a Ferrari 599 against a Bugatti Veryon. Both crazy fast expensive cars, but aimed at two different markets.

I've used both. In fact our internal office uses TMG, and our remote site uses PFSense, and it really comes down to what you're after in a firewall appliance and your ability to maintain.

I find PFSense a breeze to maintain. Setting up failover links, IPSec tunnels, VPNs, etc very very simple. All of this is much more complicated in TMG, but that's because TMG is very tightly integrated into your Active Directory environment.

TMG can also do host-based HTTP routing, whereas PFSense can't, so you can use one IP address across multiple internal web servers without needing a specific reverse proxy.

One of the best things about TMG is that you can effectively turn off just one person's internet access by disabling their AD account in the firewall. No need to set up any Squid authentication with RADIUS against your AD and then setting up ACLs.

I'd say the TMG is more difficult to learn then PFSense if you're starting from a blank plate.