Run now tasks /agent wake ups

[rbenson09]

What ports so run now tasks and agent wake ups use? we have an issue where a group of clients check in normally but we cannot do an agent wake-up or run now task on them. I had out network team check traffic from the ePO server to the clients on port 8081 but they don't see the server communicating over that port at all.

[aguevara]

By default indeed is 8081 but this can be changed on your environment on Server Settings> ports 

does a telnet work from the server to those machines IP:8080 ? 

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

[rbenson09]

how would i test that?

[aguevara]

from the ePO server on cmd use the telnet command with the target IP and port, for example:

telnet 192.168.0.35 8081

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

[cdinet]

Are these clients on the internal network or connected via vpn, or external?  If not using dxl, you can only send wakeups to internal clients not natted.  Run client task now also relies on wakeup functionality.

[rbenson09]

These are on a different domain and the DXL status says not available. Is there a way to use DXL on clients on a different domain? Apologies - I am unsure what DXL is.

[aguevara · Accepted solution]

lets go back one step.

even if the machines are on different domain a telnet test could work and subsequently the ePO server (or Remote Agent Handler) could send a wake up call or a run client task now (as both relay on por 8081), it all comes down on how the network topology works and if the server can reach those machines on that port.

Wake ups and run client task now do not work if the end nodes are behind a NAT network or VPN as the server doesn't see then machines IP and this is expected.

When working with Mcafee DXL its not important where the machines are located as that technology allows you to send wake ups, run client task now anywhere on your organization, even if you have machines communicating over NAT, VPN or even over the internet (the server must have a public IP) 

Recent versions of MA include a DXL client, but if you use ePO Onprem you need to deploy the server side of DXL for this to work, that we call it a DXL broker, more info on the DXL install guide:

https://docs.mcafee.com/bundle/data-exchange-layer-5.0.x-installation-guide/page/GUID-E48337F3-738B-...

If all you need is assign task to a machine and wake ups or run client task now dont work because of network restrictions then we have another way which is preferred and thats called "Client task assignment" , how it works is documented on the ePO guide below:

https://docs.mcafee.com/bundle/epolicy-orchestrator-5.10.0-product-guide/page/GUID-BD964765-1773-4FF...

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?