You may have a perfectly valid http web publishing rule that TMG seems to be ignoring and denying processing with Rule “None – see Result Code” and Result Code logged is 0xc0040050 FWX_E_TCPIP_DROP_IP_NOT_LOCALLY_DESINED and applying default rule to
Denied Connection
Log type: Firewall service
Status: An ingoing packet was dropped because its destination address does not exist on the system, and no appropriate forwarding interface exists.
Rule: None - see Result Code
Protocol: HTTP
Destination Port: 80
Additional information
Number of bytes sent: 0 Number of bytes received: 0
Processing time: 0ms Original Client IP: <IP Address>
You will notice port is 80 but request is not going anywhere (denied). For a published site on default port (80) with a host header (most SharePoint implementation), you may wonder if host header info is being wiped out or rewritten.
Examining the Windows Application Event Log, you will notice following warnings as well.
Log Name: Application
Source: Microsoft Forefront TMG Web Proxy
Event ID: 14148
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: TMGFWHost.example.com
Description:
The Web Proxy filter failed to bind its socket to <Internal NIC IP> port 443. This may have been caused by another service that is already using the same port or by a network adapter that is not functional. To resolve this issue, restart the Microsoft Firewall service. The error code specified in the data area of the event properties indicates the cause of the failure.
Description:
The Web Proxy filter failed to bind its socket to <Internal NIC IP> port 80. This may have been caused by another service that is already using the same port or by a network adapter that is not functional. To resolve this issue, restart the Microsoft Firewall service. The error code specified in the data area of the event properties indicates the cause of the failure.
CAUSE
TMG stopped processing http rule when Web Server running on port 80 on the TMG Server. In other words, the ports used by TMG Web Proxy Filter (Web Listener) must not be used by IIS running. The error messages you will get include:
SOLUTION:
Stop the IIS on TMG Host (iisreset /stop).
Restart “Microsoft Forefront TMG Firewall”
It’s not a good idea to host the Web Sites on the same server where you running TMG.