Error 10013 An Attempt Was Made
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Mon, 10 Oct 2016 07:17:36 GMT by s_ac15 (squid/3.5.20)
ASP.NET Community Standup Forums Help Home/ASP.NET Forums/General ASP.NET/Web Forms/A TCP error (10013: An attempt was made to access a socket in a way f... A TCP error (10013: An attempt was
Socket Error 10013 Windows Live Mail
made to access a socket in a way forbidden by its access permissions) socket error 10013 error number 0x800ccc0e occurred while listening on IP Endpoint=0.0.0.0:8080 [Answered]RSS 3 replies Last post Jan 21, 2013 06:52 AM by geniusvishal ‹ bind error 10013 tftpd32 Previous Thread|Next Thread › Print Share Twitter Facebook Email Shortcuts Active Threads Unanswered Threads Unresolved Threads Support Options Advanced Search Related Links GuidanceSamplesVideos Reply nypahe None 0 Points 2 Posts A TCP error http://answers.microsoft.com/en-us/windows/forum/windows_7-networking/socket-10013-error-when-trying-to-connect-some/2cc71cb6-24b2-4b63-8f60-32bb444eb8fd (10013: An attempt was made to access a socket in a way forbidden by its access permi... Jan 20, 2013 01:20 AM|nypahe|LINK Hi I am learning WCF I wrote a simple code and got this error A TCP error (10013: An attempt was made to access a socket in a way forbidden by its access permissions) occurred while listening on IP Endpoint=0.0.0.0:8080. PLease, How can I http://forums.asp.net/t/1876474.aspx?A+TCP+error+10013+An+attempt+was+made+to+access+a+socket+in+a+way+forbidden+by+its+access+permissions+occurred+while+listening+on+IP+Endpoint+0+0+0+0+8080 fix that error? Thanks Reply Ruchira All-Star 52756 Points 9675 Posts MVP Re: A TCP error (10013: An attempt was made to access a socket in a way forbidden by its access p... Jan 20, 2013 03:10 AM|Ruchira|LINK Hello, May be your firewall/Antivirus software is blocking that port. Try disabling them or adding exception rules for port 8080. Please 'Mark as Answer' if this post helps youDeveloper Tools Download | Windows 10 Videos | My Tech Blog Reply Pengzhen Son... Star 9897 Points 1291 Posts Microsoft Re: A TCP error (10013: An attempt was made to access a socket in a way forbidden by its access p... Jan 21, 2013 06:29 AM|Pengzhen Song - MSFT|LINK Hi, Most likely the socket is held by some process. You can try changing the port number in the endpoint. Please refer http://stackoverflow.com/questions/10461257/an-attempt-was-made-to-access-a-socket-in-a-way-forbbiden-by-its-access-permiss http://lucatarrini.net/?p=341 Hope it can help you. We are trying to better understand customer views on social support experience. ClickHERE to participate the survey. Thanks! Reply geniusvishal Star 12372 Points 3305 Posts Re: A TCP error (10013: An attempt was made to access a socket in a way forbidden by its access p... Jan 21, 2013 06:52
here for a quick overview of the site Help Center Detailed answers to any questions you might http://superuser.com/questions/635498/socket-error-errno-10013-port-forbidden-access-permissions have Meta Discuss the workings and policies of this site About http://bugs.python.org/issue15779 Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is a question and answer site for computer enthusiasts and power users. Join them; error 10013 it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top socket.error: [Errno 10013] Port forbidden access permissions up vote 4 down vote favorite 1 When trying to use a Python script I get this error: socket.error: 10013 an attempt [Errno 10013] An attempt was made to access a socket in a way forbidden by its access permissions I put the post on Stackoverflow and I have been guided to come here and follow up with why I get the error. http://stackoverflow.com/questions/18370235/socket-error-sending-email-using-gmail As the post on stackoverflow suggests, the issue is not with Python, but my computer. I can even telnet to smtp.gmail.com Can anyone provide any suggestions? EDIT: SOLVED The problem was McAfee Antivirus. It was blocking the socket connection. From McAfee Access Protection Log 23/08/2013 10:23:54 a.m. Blocked by port blocking rule C:\Program Files (x86)\Python26\python.exe Anti-virus Standard Protection:Prevent mass mailing worms from sending mail 74.125.25.108:25 I disabled McAfee completely and it worked fine after that. Thanks port sockets share|improve this question edited Aug 22 '13 at 22:36 asked Aug 22 '13 at 22:17 user1494941 21114 What OS are you using. Maybe you need to open firewall or router ports. –Doktoro Reichard Aug 22 '13 at 22:21 My OS is Win
User List Committer List Help Tracker Documentation Tracker Development Report Tracker Problem Issue15779 classification Title: socket error [Errno 10013] when creating SMTP object Type: behavior Stage: Components: Library (Lib), Windows Versions: Python 3.2 process Status: closed Resolution: works for me Dependencies: Superseder: Assigned To: Nosy List: Jimbofbx, loewis, pitrou, tim.golden Priority: normal Keywords: Created on 2012-08-24 17:42 by Jimbofbx, last changed 2012-08-25 00:22 by pitrou. This issue is now closed. Messages (15) msg169055 - (view) Author: James Hutchison (Jimbofbx) Date: 2012-08-24 17:42 Windows 7 64-bit, Python 3.2.3 This is a very odd issue and I haven't figured out what caused it. I have a python script that runs continuously. When it receives a request to do a task, it creates a new thread (not a new process), does the task, then sends out an e-mail to indicate it was done. It doesn't do this a lot (maybe 10 - 30 times a day). This is all the script does. Well today, it randomly broke. It was working fine, then suddenly I was getting the following error when it would create an SMTP object: socket.error: [Errno 10013] An attempt was made to access a socket in a way forbidden by its access permissions What I found was, even after trying a different script that did nothing but create a simple SMTP connection to localhost, running with admin privileges, and even after rebooting the machine, I was getting this error. I checked my firewall and didn't see any changes (I share a group policy so I do not have full control). I also tried the script on a different machine and found no issue. The issue also persisted between IDLE and simply running python.exe When I tried to debug the issue, I discovered the following piece of code made the issue go away: s = socket.socket() s.bind(('',50007)) s.listen(1); s.close(); And it hasn't come back since. I've tried to reproduce the circumstances that my script was running by creating SMTP instances in a loop but haven't been able to recreate the error. Checking my log, there isn't anything abnormal that occurred just before this issue (like attempting to do the task several times at once or something). msg169061 - (view) Author: Martin v. Löwis (loewis) * Date: 2012-08-24 17:58 As this is an error reported by Windows, it *very* unlikely is an issue with Python. Instead, it's a reaction that Windows produced to some sequence of events. My guess is that another process had the address in use, apparently, Windows then reports WSAEACCESS in certain