none
TMG 2010 denying connections RRS feed

  • Question

  • We have a application that is struggling to connect successfully to cloud services for DNS verifications etc. Our TMG server is denying connections when logging is enabled from my local computer.

    I created an access rule allowing all outbound traffic from internal to the specified range. When i launch the app from my pc, i do see successful connections however vast majority are logging the following:

    I noticed that there does not seem to be a rule applicable resulting in the denied connections? Is there any other rule that i need to create to ensure successful connections?

    Denied Connection
    <id id="L_LogPane_LogType">Log type: </id><id id="L_LogPane_FirewallService">Firewall service</id>
    <id id="L_LogPane_Status">Status: </id>A non-SYN packet was dropped because it was sent by a source that does not have an established connection with the Forefront TMG computer.
    <id id="L_LogPane_Rule">Rule: </id>None - see Result Code
    <id id="L_LogPane_Source">Source: </id>Internal (172.20.128.46:47314)
    <id id="L_LogPane_Destination">Destination: </id>External (41.74.203.10:18095)

    <id id="L_LogPane_Protocol">Protocol: </id>Unidentified IP Traffic (TCP:18095)

    Denied Connection
    <id id="L_LogPane_LogType">Log type: </id><id id="L_LogPane_FirewallService">Firewall service</id>
    <id id="L_LogPane_Status">Status: </id>A connection was rejected because the maximum connections rate for a single client host was exceeded.
    <id id="L_LogPane_Rule">Rule: </id>None - see Result Code
    <id id="L_LogPane_Source">Source: </id>Internal (172.20.128.46:49560)
    <id id="L_LogPane_Destination">Destination: </id>External (41.74.203.10:18409)

    • <id id="L_LogPane_BytesSent">Number of bytes sent: </id>0<id id="L_LogPane_BytesReceived">Number of bytes received: </id>0
    • <id id="L_LogPane_ProcessingTime">Processing time: </id>0ms<id id="L_LogPane_OriginalClientIp">Original Client IP: </id>172.20.128.46

    Wednesday, July 10, 2019 10:52 AM

All replies