Control Socket Error = #10038
Contents |
360 games PC games Windows socket error code 10038 games Windows phone games Entertainment All Entertainment 10038 socket operation on non-socket Movies & TV Music Business & Education Business Students & educators Developers
Socket Error 10054
Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet
What Is A Socket Error
Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Band Microsoft Lumia socket error codes linux All Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
360 games PC games Windows
Socket Error 10053
games Windows phone games Entertainment All Entertainment socket error 10054 connection reset by peer Movies & TV Music Business & Education Business Students & educators Developers socket error 11004 Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet https://support.microsoft.com/en-us/kb/819124 Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Band Microsoft Lumia https://support.microsoft.com/en-us/kb/155738 All Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn http://stackoverflow.com/questions/100074/winsock-10038-error-win2k3-server-baffling-behaviour more about Stack Overflow the company Business Learn more about hiring developers or http://support.2brightsparks.com/knowledgebase/articles/213469-common-ftp-errors-and-socket-error-messages posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Winsock - 10038 Error - Win2K3 Server - baffling socket error behaviour up vote 0 down vote favorite Attempt to send a message through a socket failed with WinSock error 10038. After around 40 seconds, messages are received successfully from the same socket and subsequently the send() is also succeeding in the same socket. This behaviour has been witnessed in Windows Server 2003. Is this any known behaviour with WinSock and Windows Server 2003? windows-server-2003 winsock share|improve this question socket error code asked Sep 19 '08 at 6:37 SentliSh Have you tried on another platform (XP for example)? –paxdiablo Sep 19 '08 at 6:45 Is there an asynchronous create call that hasn't finished before you try to access the socket? –Brad Bruce Sep 19 '08 at 10:49 add a comment| 3 Answers 3 active oldest votes up vote 3 down vote accepted Winsock error 10038 means "An operation was attempted on something that is not a socket". Little trick to find info about error codes (usefull for all sorts of windows error codes): Open a command prompt Type "net helpmsg 10038" What language is your application written in? If it's C/C++, could it be that you are using an invalid socket handle? share|improve this answer answered Sep 19 '08 at 12:46 Otherside 2,2561318 add a comment| up vote 0 down vote Not a platform issue, I can guarantee that. Most likely, whatever variable you are using to access the socket handle is not thread-safe and is being used in the send() call before the actual socket is created. Another possible cause is the presence of layered winsock providers. "netsh winsock show" at a cmd prompt will show you th
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 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 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 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 t