Connection Error From Notification Server Windows Socket Error #10013
years ago Closed 7 years ago #11296 closed defect Pidgin will not connect to any of my accounts; error #10013 Reported by: mtj9488 Owned by: datallah Milestone: Component: winpidgin (gtk) Version: 2.6.5 Keywords: connection error #10013 Cc: Description (last windows socket error 10013 pidgin modified by darkrain42) My pidgin isn't crashing, but it won't connect to socket error 10013 windows 7 any of my accounts. I've tried uninstalling and reinstalling and I've tried playing with the ports as recommended by various online troubleshooters, but nothing has helped or changed the status of my pidgin problem. I found the tickets seeming to report the same error, but neither gave me a hint on how to fix it. Here's a copy of 20 seconds of the debug window report: (12:58:26) proxy: Error connecting to messenger.hotmail.com:1863 (Windows socket error #10013). (12:58:26) proxy: Connection attempt failed: Windows socket error #10013 (12:58:26) msn: Connection error: Windows socket error #10013 (12:58:26) msn: Connection error from Notification server (messenger.hotmail.com): Windows socket error #10013 (12:58:35) proxy: Error connecting to login.messaging.aol.com:80 (Windows socket error #10013). (12:58:35) proxy: Connection attempt failed: Windows socket error #10013 (12:58:35) oscar: unable to connect to FLAP server of type 0x0017 (12:58:43) proxy: Error connecting to talk.l.google.com:5222 (Windows socket error #10013). (12:58:43) proxy: Connection attempt failed: Windows socket error #10013 (12:58:43) jabber: Unable to connect to server: Windows socket error #10013. Trying next SRV record. (12:58:43) proxy: Error connecting to talk4.l.google.com:5222 (Windows socket error #10013). (12:58:43) proxy: Connection attempt failed: Windows socket error #10013 (12:58:43) jabber: Unable to connect to server: Windows socket error #10013. Trying next SRV record. (12:58:43) proxy: Error connecting to talk1.l.google.com:5222 (Windows socket error #10013). (12:58:43) proxy: Connection attempt failed: Windows socket error #10013 (12:58:43) jabber: Unable to connect to server: Windows socket error #10013. Trying next SRV record. (12:58:43) proxy: Error connecting to talk2.l.google.com:5222 (Windows socket error #10013). (12:58:43) proxy: Connection attempt failed: Windows socket error #10013 (12:58:43) jabber: Unable to connect to server: Windows socket error #10013. Trying next SRV record. (12:58:43) proxy: Error connecting to talk3.l.google.com:5222 (Windows socket error #10013). (12:58:43) proxy: Connection attempt failed: Windows so
be down. Please try the request again. Your cache administrator is webmaster. Generated Wed, 05 Oct 2016 02:26:49 GMT by s_hv987 (squid/3.5.20)
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows 10Windows 10 MobilePrevious versionsMDOPSurfaceSurface HubLibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered https://social.technet.microsoft.com/Forums/windows/en-US/43fce83f-4b5c-4104-bcd0-9e8e77593069/error-10013?forum=w7itproappcompat by: error 10013 Windows 7 IT Pro > Windows 7 Application Compatibility Question 0 Sign in to vote I can receive my emails but I cannot https://www.experts-exchange.com/questions/24586995/Socket-error-10013-access-denied.html send them. I get the following message:The connection to the server has failed. Subject 'test of parchment 'Server: 'smtp.aol.com'Windows Live Mail Error ID: 0x800CCC0EProtocol: SMTPPort: 25Secure(SSL): socket error NoSocket Error: 10013Any suggestions for a solution? Thanks Monday, February 15, 2010 2:42 AM Reply | Quote Answers 1 Sign in to vote Hi,The error indicate: Cannot connect to server. Refer to http://support.microsoft.com/kb/942495. When did this issue first occur? Did you install any newsoftware?With the account settings open, go to the Advance tab, windows socket error and change the SMTP port to 587. Make sure Authenticationis enabled. Close widnows live mail and re-open it. If no go, change the SMTP back to the original data(25 usually) from 587. This port varies according different cases. For more information, visit http://messenger-support.spaces.live.com/ Marked as answer by Dale QiaoModerator Monday, February 22, 2010 8:01 AM Tuesday, February 16, 2010 9:50 AM Reply | Quote All replies 1 Sign in to vote Hi,The error indicate: Cannot connect to server. Refer to http://support.microsoft.com/kb/942495. When did this issue first occur? Did you install any newsoftware?With the account settings open, go to the Advance tab, and change the SMTP port to 587. Make sure Authenticationis enabled. Close widnows live mail and re-open it. If no go, change the SMTP back to the original data(25 usually) from 587. This port varies according different cases. For more information, visit http://messenger-support.spaces.live.com/ Marked as answer by Dale QiaoModerator Monday, February 22, 2010 8:01 AM Tues
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Socket error 10013 access denied Want to Advertise Here? Solved Socket error 10013 access denied Posted on 2009-07-21 Windows OS 1 Verified Solution 10 Comments 3,559 Views Last Modified: 2013-11-05 Hi I have a program that listens to port 1234 on my server machine which is windows small business server. This program worked fine up until this morning and I am now getting a socket error 10013 acess denied. Please can you tell me what could be causing this? Perhaps someone has made some network changes i don't know about. How can i see what sockets are being used on the server and what permissions they have. I don't really know anything about sockets. I've never really had a problem before. thanks 0 Question by:andieje Facebook Twitter LinkedIn Google LVL 2 Best Solution bydabernathy It may be that something else is listening on that port. Did you install or patch something else on the server recently? 1. Open a command prompt and do the following: netstat -ano | findstr 0.0:1234 Go to Solution 10 Comments LVL 2 Overall: Level 2 Windows OS 1 Message Accepted Solution by:dabernathy2009-07-21 It may be that something else is listening on that port. Did you install or patch something else on the server recently? 1. Open a command prompt and do the following: netstat -ano | findstr 0.0:1234 If you get a result, make a note of the process ID, it's the number on the far right. 2. CTRL-ALT-DEL and open the Task List. Switch to the Processes tab. Add the PID column by selecting View...Select Columns...PID (Process Identifier). Click the column header to sort by PID and find the process number from step 1. Note the name of the program that has port 1234 in use. 0 Message Author Comment by:andieje2009-07-21 Hi Thanks very much for your reply. I ran that command and nothing came back so i ran netstat -ano and looked at all of the items in the list and none of them were associated with port 1234 Help! :) 0 Message Author Comment by:andieje2009-07-21 Also, nothing ha