locked
FCS client trying to communicate with WRONG source IP RRS feed

  • Question

  • Hi all, i have one TMG beta 3 with FCS client installed and managed from our FCS server and correctly updating with WSUS.

    Since it has three NICs, it choose to connect to the server on port 1270 sometimes with source IP of the internal (correct) and sometimes with source IP of the external NIC...

    (i saw that in the TMG logs)


    is there a way to bind agent communications to one NIC?


    Thanks
    Diego Castelli
    Tuesday, August 4, 2009 8:54 AM

All replies

  • Hi,

     

    Thank you for your post.

     

    Based on my experience, by default TMG will block the traffic from external to internal. I suspect that external nic is just attempt to connect FCS not really communicate to the FCS. Would you please pick up the TMG logs?

     

    Regards,


    Nick Gu - MSFT
    • Proposed as answer by Nick Gu - MSFT Tuesday, August 11, 2009 2:59 AM
    • Marked as answer by Nick Gu - MSFT Wednesday, August 12, 2009 9:28 AM
    • Unmarked as answer by Diego Castelli Monday, August 24, 2009 9:51 AM
    Wednesday, August 5, 2009 8:18 AM
  • as stated the issue is NOT the communication, but how to bind the communication to a single NIC. Thank you anyway.

    Diego Castelli
    Monday, August 24, 2009 9:51 AM