Ftp Error 2000
to server xxx.xxx.x.xx (ip= xxx.xxx.x.xx)... ERROR:> Can't connect to remote server. Socket error = #2000. ERROR:> Timeout (60000ms). STATUS:> Waiting 30 seconds...... To avoid this error, open port 21 to inbound and outbound traffic. Most often a firewall (such as those from MacAfee, Norton or the built-in Windows XP firewall) is blocking inbound or outbound TCP traffic on port 21. For more error code information, refer to Knowledge Base article 10140 at http://kb.globalscape.com. Did this topic solve your problem/answer your question? * For the most up-to-date information regarding CuteFTP, * To view version history, updates, and activation instructions, * To download a PDF of this user guide, * To search the Knowledgebase and User Forum, Visit the GlobalSCAPE Support Center, http://www.globalscape.com/support. Copyright © 1996-2011 GlobalSCAPE, Inc. All rights reserved. Based on the original by Alex Kunadze. Last modified: 2012-01-25
CPanel and Site Maintenance Javascript Disabled Detected You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality. Unable To Connect Via Ftp Started by bryghtrose, Dec 09 2004 10:25 AM Please log in to reply 3 replies to this topic #1 bryghtrose bryghtrose Members 1 posts Posted 09 December 2004 - 10:25 AM Hi, I'm a bloghosts refugee, and I'm trying to set up my site here. I want to switch from MT to Wordpress, and I need to upload the WP files to http://help.globalscape.com/help/cuteftp8/Socket_Error_2000.htm my home directory. I could do this using the file manager in cpanel, but that is very slow, and it doesn't allow for directory uploads. I have both Cute-FTP and WS-FTP on my home machine, and I've tried to upload with both...and neither will work. I'm using my superuser username and passowrd, and I get the following errors:STATUS:> Getting listing ""...STATUS:> Resolving host name https://forums.totalchoicehosting.com/index.php?showtopic=14936 ftp.roseread.net...STATUS:> Host name ftp.roseread.net resolved: ip = 66.235.180.58.STATUS:> Connecting to FTP server ftp.roseread.net:21 (ip = 66.235.180.58)...ERROR:> Can't connect to remote server. Socket error = #2000.ERROR:> Timeout (30000 ms).I have it set to use Port 21, and I've checked my ftp settings in cpanel. They look ok to me, and this is the first time I've been unable to ftp anywhere with my superuserID. My site is roseread.net.Any suggestions?~Rose Back to top #2 TCH-Dick TCH-Dick General Manager Admins 5,827 posts Posted 09 December 2004 - 10:31 AM Are you behind a router or using a firewall sortware? If you are, try opening up port 21. Dick DeVance General Manager TotalChoice Hosting, Inc dick@totalchoicehosting.com Back to top #3 TCH-Bruce TCH-Bruce Volunteer Moderator Members 20,101 posts Posted 09 December 2004 - 10:39 AM And welcome to the family and forums. Bruce Richards Forum Moderator TotalChoice Hosting, Inc.Webhosting by Total Choice Web Hosting - General Support Forum I am a Forum Moderator. While I can assist in answering most of your hosting related questions, I am unable to answer questions about specifics relating to your account such as billing and server
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: Socket Error # 11001, Host not found: Check that the hostname or IP address http://support.2brightsparks.com/knowledgebase/articles/213469-common-ftp-errors-and-socket-error-messages 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 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 error 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 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 ftp error 2000 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 profile that connects to an FTP server you may receive the following errors in the log file: Scan failed (-1): Read Timeout: The connection to the FTP server was lost, and the attempts to reconnect failed, while trying to scan it for changes. Other common problems are: Can connect to the FTP server but when trying to choose the destination directory nothing happens for a very long time. Eventually the selection window appears but it’s empty: You need to enable Passive mode, or t