PacketShaper unable to connect to Threatpulse through Microsoft Forefront TMG

book

Article ID: 168490

calendar_today

Updated On:

Products

PacketShaper

Issue/Introduction

When trying to use Threatpulse on the PacketShaper via a Microsoft Forefront TMG, the connection is failing.

Cause

By default, Microsoft Forefront TMG will not accept a CONNECT request on port 80.

You can confirm this is the same issue by performing a packet capture on the localhost on PacketShaper. The response from the TMG will be non-standard SSL request not accepted (even though this is not a non-standard SSL request — an HTTP CONNECT request does correctly use port 80.) 

Resolution

There are workaround solutions created by Microsoft on the Microsoft TechNet pages.