If you’re experiencing problems whereby some clients on remote networks are randomly unable to access the Internet, or you’re having other weird problems on your TMG-protected network, you’ll want to check out this great blog post from Yuri Diogenes, titled Side Effect of Wrong Network Configuration on Forefront TMG. He discusses a common configuration mistake that may cause your network to function improperly, and the correct way to set up the environment instead.
About The Author
Deb Shinder
Debra Littlejohn Shinder is a technology and security analyst and author specializing in identity, security and cybercrime, utilizing her past experience as a police officer and police academy/criminal justice instructor. She has written numerous books and articles for web and print publications and has been awarded the Microsoft MVP designation for fourteen years in a row.
Read Next
Last Chance to Sign up for the Webinar Windows 2003 End of Life Risks and Considerations
Windows Server 2003 support ended on July 14, 2015. Now more than ever, you need to be aware of the risk factors and other considerations…
5 Critical Settings Not Available in the Forefront Threat Management Gateway (TMG) 2010 Management Console
In this article I’ll explore 5 important configuration settings not available in the GUI and demonstrate how to view and change them using VBScript and…
Remote SQL Logging for Forefront Threat Management Gateway (TMG) 2010 using Microsoft Azure
In this article I’ll demonstrate how to create and prepare an SQL server virtual machine hosted in Microsoft Azure for TMG logging.
Implementing a CNG HTTPS Inspection Certificate for Forefront Threat Management Gateway (TMG) 2010 (Part 1)
In this article I’ll demonstrate how to configure TMG HTTPS inspection using an internal Windows Server 2008 R2 Enterprise Public Key Infrastructure (PKI) with support…