2 Replies Latest reply on Dec 21, 2011 9:22 AM by adionne

    EEGO Data Channels specifications

    adionne

      What exactly are the Data Channels for EEGo? in this situation are they the ports used by the ePO agent to send along data information to the ePO server i.e the Agent-to-server communication port and the Agent-to-server communication port? this is based on EEPC 6.1.2

       

      Most of the systems that we have deployed EEGo to in this environment have Data Channel Failures (client to server) and Data Channel Failure (Server to client)

        • 1. Re: EEGO Data Channels specifications

          As you say, they are the way some McAfee products talk to EPO. It's tcpip traffic as you say. There's lots of information on EEPC/Data Channels on kc.mcafee.com - what version of EPO you need to be on before they are supported over NAC/Firewalls etc.

           

          The usual problem is that the EPO server can't directly resolve the IP of the host.

          1 of 1 people found this helpful
          • 2. Re: EEGO Data Channels specifications
            adionne

            Fantastic! took a look through the KB's and after conferring with Platinum, we seem to have an answer as to why the systems that stay inactive also have EEGo Data Channel failures.

             

            For people who may look at this thread- KB68628 talks about the need for the Agent wakup port to be available. when the client creates the events and sends them to ePO, ePO has no way to communicate back without that port.

             

            Thanks again!