Connect Error 10054
Contents |
Xively Related Articles What does 'error 10053' mean? What does Error 10061 mean? What does Error 4320 mean? itunes error 10054 What does 'Error Code 10060' mean? What does error 12017 error 10054 tftp mean? Contact Us Give us a call Close X You can reach us at: US Canada: error 10054 logmein 1-866-478-1805 Click here for more phone options Our Support team is available 7:30 PM Sunday to 9 PM Friday (U.S. EST) Submit a help ticket https://msdn.microsoft.com/en-us/library/windows/desktop/ms740668(v=vs.85).aspx Ask the community Welcome to LogMeIn Support! pkb2_lang_de pkb2_lang_en_US pkb2_lang_es pkb2_lang_fr pkb2_lang_it pkb2_lang_ja pkb2_lang_nl_NL pkb2_lang_pt_BR Search the Knowledge Base Reset Search Search Narrow Your Search 1 Select a LogMeIn Product All Products LogMeIn Rescue Rescue Lens LogMeIn Central LogMeIn Pro LogMeIn Backup LogMeIn Hamachi AppGuru Cubby join.me BoldChat RemotelyAnywhere Meldium Xively 2 http://help.logmein.com/articles/en_US/FAQ/What-does-Error-10054-mean Select an Article Type All Article Types FAQ Downloads Product Guide Release Note Video What does Error 10054 mean?Printable View «Go BackInformation AnswerSymptom Connection is lost and you receive a Windows Socket Error 10054. Cause Error 10054 occurs when the connection is reset by the peer application, usually due to an incorrect firewall configuration. Find more information about this error on Microsoft Development Center. Action Check the following items to ensure that your system, firewall and router are configured correctly. Solution 1: Verify that LogMeIn domains are whitelisted in your firewall/router configuration. DomainDescription*.logmein.comLogMeIn main site*.logmeinrescue.comPowers the LogMeIn Rescue service*.logmeinrescue-enterprise.comPowers account-specific Rescue features (not required on normal accounts)*.logme.inLogMeIn common login service allowing login to LogMeIn.com, join.me, and cubby.com*.hamachi.ccPowers the LogMeIn Hamachi service*.internapcdn.netPowers updates to multiple LogMeIn products*.LogMeIn123.comSite to connect to a LogMeIn Rescue technician*.123rescue.comSite to connect to a LogMeIn Rescue technician*.support.meSite to connect to a LogMeIn Rescue technician*.join.meConferencing and screen sharing service by LogMeIn*.cub.byRedirects to Cubby services*.cubby.com
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss http://stackoverflow.com/questions/10997221/irregular-socket-errors-10054-on-windows-application the workings and policies of this site About Us Learn more about http://stackoverflow.com/questions/25485816/openssl-errno-10054-connection-refused-whilst-trying-to-connect-to-our-server Stack Overflow the company Business Learn more about hiring developers or 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 error 10054 other. Join them; it only takes a minute: Sign up Irregular socket errors (10054) on Windows application up vote 1 down vote favorite 1 I am working on a Windows (Microsoft Visual C++ 2005) application that uses several processes running on different hosts in an intranet. Processes communicate with each other using TCP/IP. Different processes can be on the error 10054 connection same host or on different hosts (i.e. the communication can be both within the same host or between different hosts). We have currently a bug that appears irregularly. The communication seems to work for a while, then it stops working. Then it works again for some time. When the communication does not work, we get an error (apparently while a process was trying to send data). The call looks like this: send(socket, (char *) data, (int) data_size, 0); By inspecting the error code we get from WSAGetLastError() we see that it is an error 10054. Here is what I found in the Microsoft documentation (see here): WSAECONNRESET 10054 Connection reset by peer. An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, the host or remote network interface is disabled, or the remote host uses a hard close (see setsockopt for more information on the SO_LINGER option on the remote socket). This error may also
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 more about Stack Overflow the company Business Learn more about hiring developers or 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 OpenSSL errno 10054,connection refused, whilst trying to connect to our server up vote 0 down vote favorite We are running a git server over https and didn't have any trouble connecting because we all used visual studio to do so. Now someone wants to use the standard git bash and it fails to connect with the following error output. fatal: unable to access 'https://server/Repo.git/': Unknown SSL protocol error in connection to server:443 I tried some different ciphersuites, nothing worked. Then it came to me that it might be that git doesn't support ECDSA certificates yet. So I exchanged the ECDSA certificate for one with RSA. That also didn't work. Then I tried connecting with OpenSSL s_client with the following command: OpenSSL> s_client -connect server:443 This is the output from running the command: CONNECTED(0000018C) write:errno=10054 --- no peer certificate available --- No client certificate CA names sent --- SSL handshake has read 0 bytes and written 307 bytes --- New, (NONE), Cipher is (NONE) Secure Renegotiation IS NOT supported Compression: NONE Expansion: NONE --- I searched google for the error number 10054 and found it means connection refused. We use IIS 8.5 to supply the https endpoint for the git server. I can connect to the web environment through all webbrowsers and we can use the git server through the visual studio git interface. So I don't think it's a firewall issue. I'd like to know if anyone has experienced this problem before and if they could help us out here? git iis https openssl share|improve this question asked Aug 25 '14 at 12:20 Feanaro 3611023 1 Possibly related: An application may receive the "10054" error when the application receives data from a connection on a computer that is running Windows 7 or Windows Server 2008 R2 if a TDI filter driver is installed. –jww Aug 25 '14 at 12:36 We are running windows server 2012 R2. The hotfix doesn't apply to our version of windows server. But thanks for the suggestion. And the computer running the openssl client is a windows 8.1 pro computer running the x64 version of openssl. –Feanaro Au