Browse by Tags

Related Posts
  • Blog Post: TMG Logging to LLQ

    One of the problems causing TMG to log to LLQ instead of the database is the presence of orphaned databases in the local SQL Server instance. In other words you may have some databases that are registered on the local SQL Server but the corresponding .mdf and .ldf files are missing from the disk. This...
  • Blog Post: How to View TMG Logs when using SQL Server Express for Logging

    1. Introduction By default Forefront TMG 2010 will store the Firewall and Web Proxy Logging in Microsoft SQL Server 2008 Express databases. . Many Forefront TMG administrators need access to much older data than can be easily maintained on the firewall itself, so these administrators need a simple...
  • Blog Post: Issue with TMG remote SQL logging

    We recently received a case from a customer reporting that the TMG log data were not being properly stored in a remote SQL database but was accumulated in the Large Logging Queue (LLQ). The LLQ is an improvement added in TMG, particularly useful in scenarios where logging to a remote SQL Server is involved...
  • Blog Post: How to configure the TMG Service Account to avoid problem with logging on SQL Server

    One of the features introduced with TMG Service Pack 2 is to run the Firewall Service with a Domain account, this allow users to authenticate with Kerberos when using NLB. Find more information about this feature here: http://technet.microsoft.com/en-us/library/hh454304.aspx However you should pay attention...
  • Blog Post: Expect the unexpected… Failed Connection 995 and 64 with SSL Traffic

    When speaking with customers, we hear a lot of questions around “unexpected” errors like “Failed Connection Error 995 Operation Aborted” and “Failed Connection Error 64 Net name Deleted” in the ISA/TMG logs. The main concern here is always if these errors are real errors and how to prevent them. These...