Mcafee Unknown Error Contacting Agent
Contents |
on and reload this page. All Places > Business > ePolicy Orchestrator (ePO) > Discussions Please enter a title. You can not post a blank message. Please type your message and try server failed to wake up detailed error again. This discussion is archived 7 Replies Latest reply on Dec 10, mcafee agent failed to communicate with epo server 2010 10:59 AM by Tristan Can't execute Client Tasks from ePO weak_pig Nov 16, 2010 2:22 AM My mcafee network error was 10061 ePO 4.5 has a Client Task "Remove Old Version of Site Advisor 1.7" which will run Once.I have 6 Windows 7 clients and 1 Windows XP client, all of mcafee error 10060 which I need this Task deployed.I used the command Wake Up Agents and set the configuration to "Force Complete policy and task update" but after several attempts, the software is still in the client machines.Anyone can help ?I understand Windows 7 may have some communication issues with ePO, but based on KB67347, the issue is resolved with McAfee Agent 4.5
Mcafee Epo Error Code 10060
Patch1, which I've installed in my ePO.Also, ICMP echo request ping can't seem to reach any of the Windows 7 clients. Any idea why? Is this part of the reason why my clients can't execute my Tasks? 12148Views Tags: none (add) This content has been marked as final. Show 7 replies 1. Re: Can't execute Client Tasks from ePO weak_pig Nov 16, 2010 2:35 AM (in response to weak_pig) In addition, I also faced another issue....I am trying to add more Windows XP based clients to my ePO System Tree. It was able to find the system and I have since added this single machine into my tree.However, this system is in Unmanaged state. I choose to Deploy Agents to this system, but the task failed.Error was "Failed to authenticate with remote system, system error: The network path was not found."At this new client system, it is running Windows XP with SP 3 and with Firewall turned on.After turning off the Firewall, I was able to deploy the agent to this system..Does this mean for ev
Support Home © 2003-2016 McAfee, Inc.
Support Home © 2003-2016 McAfee, Inc.
on and reload this page. All Places > Business > ePolicy Orchestrator (ePO) > Discussions Please enter a title. You can not post a blank message. Please type your message and try again. This discussion is archived 4 Replies Latest reply on Nov 15, 2010 4:01 PM by andymease Linux wakeup port andymease Nov 11, 2010 8:50 AM Has anyone else used the Linux agent (4.5.0.1470) with a non-standard wakeup port? It seems the agent doesn't ever report that port back and it stays at 8081. All wakeups from ePO then fail...Andrew I have the same question Show 0 Likes(0) 1785Views Tags: none (add) This content has been marked as final. Show 4 replies 1. Re: Linux wakeup port sprairie Nov 11, 2010 4:02 PM (in response to andymease) We're using 4.5.0.1470 with a non-standard port. The port [incorrectly] shows up in ePO as 8081, but the wakeup call works fine. Like Show 0 Likes(0) Actions 2. Re: Linux wakeup port andymease Nov 11, 2010 4:28 PM (in response to sprairie) Unfortunately this is what happens when I send one (name and IP replaced):11/11/10 5:13:15 PMStarting agent wakeup for SERVER11/11/10 5:13:15 PMWaking up agent SERVER using DNS name11/11/10 5:13:15 PMUnknown error contacting agent11/11/10 5:13:15 PMWaking up agent SERVER using NetBIOS11/11/10 5:13:15 PMUnknown error contacting agent11/11/10 5:13:15 PMWaking up agent at IP address X.X.X.X11/11/10 5:13:15 PMUnknown error contacting agent11/11/10 5:13:15 PMWakeup agent failed11/11/10 5:14:33 PMExpiredThe DNS name of the server is resolvable as well...Andrew Like Show 0 Likes(0) Actions 3. Re: Linux wakeup port sprairie Nov 11, 2010 4:44 PM (in response to andymease) Can you telnet from the ePO server to the agent over the wakeup port? You should get back a blank screen or garbled text (anything but "Connect failed"). If not, it could be a firewall issue -- or the agent isn't really listening on the port that you think it is.Else, I'd look for any sign in the agent log that it's receiving communication (default at /opt/McAfee/cma/scratch/etc/log). Like Show 0 Likes(0)