none
Forefront TMG suddently stopped working

    General discussion

  • After being using TMG from the past months today it just stopped providing internet to the clients (web proxy)

    basic config:

    • Interface Internal / External (2 nics) configured as good practice recommends (googled)
    • TMG is EDGE
    • Windows Server 2008 R2 (currently installing updates for troubleshoot)
    • Forefront TMG Std 7.0.9193.575

    Symptoms:

    • All TMG services started and no notable events in logs.
    • connection verifier to the internal dns server is ok.
    • connection verifier to external devices (ISP router, ISP dns, http google and pop/smtp mail) timed out.
    • ping to loopback is ok
    • If i try to ping to the ISP router i get this:

    ---General failure.
    ---General failure.
    ---Reply from xxx.xxx.xxx.xxx: bytes=32 time<1ms TTL=255
    ---Reply from xxx.xxx.xxx.xxx: bytes=32 time<1ms TTL=255
    ---Request timed out.
    ---Request timed out.
    ---Request timed out.
    ---Reply from xxx.xxx.xxx.xxx: bytes=32 time<1ms TTL=255
    ---Reply from xxx.xxx.xxx.xxx: bytes=32 time<1ms TTL=255
    ---Reply from xxx.xxx.xxx.xxx: bytes=32 time<1ms TTL=255
    ---Request timed out.
    ---General failure.
    ---General failure.
    ---Reply from xxx.xxx.xxx.xxx: bytes=32 time<1ms TTL=255

    • if i disable the firewall service, internet connectivity returns, so server hardware is ok

    the actual config was working until today so i tried to reconfigure the interfaces, rebuild the static routes with no luck, currently im updating server2008 just in case, im running out of ideas... any piece of advice??

    thanks

    Tuesday, February 19, 2013 5:30 AM

All replies

  • Hi,

    Thank you for the post.

    Please update your NIC driver and see if it helps, and have you do some change with the TMG server since it was working until today?

    Regards,


    Nick Gu - MSFT

    Monday, February 25, 2013 2:10 AM