Failed To Connect Error 11001
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 again. This discussion is archived 4 Replies Latest reply on Jan 12, 2010 11:42 AM by csteels epo mcafee network error was 10060 4.5 distributed repository replication failing on one server csteels Jan 12, 2010 10:45 AM I server failed to wake up detailed error have just about finished installing epo 4.5 and have set up the superagents/distributed repositories of which there are 35 in total.34 of them
Failed To Connect Error 10060 Mcafee
have replicated fully and with no problems, one server however is not replicating at all and I am not sure where to start troubleshooting.Looking at the task log information after the failure it is saying 'Failed to connect,
Failed To Connect, Error 11004 Mcafee
error 11001 ( No such host is known. )' Another thing I have spotted that is different to the other distributed repositories is the location is showing as 'nav260/Software' rather than 'servername/Software'Has anybody else had a similar problem or could anyone give me advice on how to troubleshoot this one?Thanks I have the same question Show 0 Likes(0) 7598Views Tags: none (add) epoContent tagged with epo, 4.5Content tagged with 4.5, distributedContent tagged with distributed, repositoryContent tagged with failed to connect error 10060 epo repository, superagentContent tagged with superagent, replicationContent tagged with replication This content has been marked as final. Show 4 replies 1. Re: epo 4.5 distributed repository replication failing on one server jstanley Jan 12, 2010 11:10 AM (in response to csteels) Re-replicate to the repository and after it fails grab a copy of the epoapsvr.log and the agent log from the client and post them here. Also post the name of the distributed repository you are failing to replicate to.The error posted indicates it could be a DNS issue. On the ePO server try running "nslookup
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 1 2 Previous Next 14 Replies Latest reply on Feb 20, 2012
Mcafee Error 10060
3:41 AM by swamy2785 Go to original post This content has been marked as final. mcafee network error was 10061 Show 14 replies 10. Re: EPO 4.5 Failed to Replicate to Repository Mr_Security Oct 25, 2010 8:16 AM (in response to mohan.mcafee) Mohan,My mcafee super agent distributed repository problem was an entry in the host file being incorrect, but it did coincidently happen after the ePO upgrade from 4.0 to 4.5. Like Show 0 Likes(0) Actions 11. Re: EPO 4.5 Failed to Replicate to Repository kmcin11 https://community.mcafee.com/thread/20813?start=0&tstart=0 Mar 13, 2011 11:42 PM (in response to hramos) I was able to get rid of these problems by a) adding all repositories including their FQDM to the host file, and b) deleting the repository folders on the super agents so that they would get recreated during the next repository push Like Show 0 Likes(0) Actions 12. Re: EPO 4.5 Failed to Replicate to Repository butchcassidy May 30, 2011 2:18 PM (in response to kmcin11) Hi,I'm https://mcafee-external-v8.hosted.jivesoftware.com/thread/21353?start=10&tstart=0 having the same message too "Failed to connect, error 11001 ( No such host is known. )", when I'm trying to update the SuperAgents, from ePO. I detected that there are more than one SuperAgent with this error, and I realized that the agents had been erased. And here is the problem, because I don't know where I can remove those wrong servers from the update list. They aren't in the ePO Server list. Like Show 0 Likes(0) Actions 13. Re: EPO 4.5 Failed to Replicate to Repository JoeBidgood May 31, 2011 10:00 AM (in response to butchcassidy) Locate the machines in the ePO system tree, and then delete them: then restart the ePO services. This should be enough to make ePO remove the offending entries from the repository list.HTH -Joe Like Show 0 Likes(0) Actions 14. Re: EPO 4.5 Failed to Replicate to Repository swamy2785 Feb 20, 2012 3:41 AM (in response to hramos) Hi team,Where has the entry to be done (epo server or the client machine ie sadr client machine)Thanks & RegardsVijay NarayanaswamyMessage was edited by: swamy2785 on 2/20/12 3:41:10 AM CST Like Show 0 Likes(0) Actions 1 2 Previous Next Go to original post Actions Remove from profile Feature on your profile More Like This Retrieving data ... © 2007-2016 Jive Software | Powered by Home | Top of page | HelpJive Software
SyncBackFree,use a different FTP engine and so return less cryptic error messages. Article Detail When testing an FTP connection you may receive one of the following errors: http://support.2brightsparks.com/knowledgebase/articles/213469-common-ftp-errors-and-socket-error-messages Socket Error # 11001, Host not found: Check that the hostname or IP address has been entered correctly. Socket Error # 11004, Unable to connect: Check to make sure there isn't a trailing or leading space character on the FTP hostname. Also, enter the hostname or IP address, not a URL, e.g. if you have entered something like ftp://my.hostname.com/ then failed to change it to my.hostname.com Socket Error # 10061, Connection refused: The hostname is correct, but either the FTP server is not listening on the port, there is no FTP server running, or a firewall is blocking the connection. Socket Error # 10093: This can happen when the network connection goes down, e.g. the FTP server is no longer connected to the failed to connect network. Socket Error # 10038: If you are using Serv-U modify your FTP server settings so that the following are unticked: “Block anti time-out schemes”, “Block FTP_bounce attacks and FXP”, and “Block users who connect more than 6 times within 60 seconds for 30 minutes.”. You may also want to be sure you are using a passive connection. Socket Error # 10039: There may be a problem getting the IP address for the hostname. Socket Error # 10052: The host you were connected to crashed and rebooted. Try reconnecting at a later time. Unable to connect: Connection time out: The hostname may be incorrect or the FTP server may be behind a firewall. Unable to connect. Not logged in: The username and/or password is not correct. Unable to connect. Error connecting with SSL: The FTP server does not support SSL, or you are using implicit SSL and it only supports explicit, or the wrong port number is being used. If you are using implicit SSL then you probably need to use port 990 instead of port 21. When running a p