Delphi Socket Error 10013
Contents |
windows XP and 2000 on normal user rights. Hi all I'm using Indy component IdIcmpClient to ping server. This is kind of weird that that ping works on
Socket Error 10013 Windows Live Mail
administrator rights on windows XP or 2000 but when trying same as normal socket error 10013 error number 0x800ccc0e user it gives exception: Socket Error # 10013 Access denied. I've noticed that this happens with IdFTP component too
Windows Socket Error 10013 Pidgin
when trying to connect remote server. I'm using Delphi 7 and Indy components that came with it. Any help/suggestions greatly appreciated. --Vesa Slas Delphi Developer Tue, 01 Nov 2005 23:56:44 GMT unexpected socket error 10013 Re:IdIcmpClient: Socket Error # 10013 Access denied. On windows XP and 2000 on normal user rights. I think that you should not use TIdIOTServer and TIdIOTClient(Indy) QuoteVesa
van GoogleInloggenVerborgen veldenZoeken naar groepen of berichten
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 http://stackoverflow.com/questions/3314656/what-causes-tcplistener-socket-error-10013 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 http://wiki-errors.com/dealing-with-socket-error-10013/ a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up What causes TcpListener Socket Error 10013? up vote 0 down vote favorite 1 I socket error get error 10013. msdn says its a permission denied error. An attempt was made to access a socket in a way forbidden by its access permissions My app ran fine. I then made a code change and restarted it. I got that error. I suspected i have to reuse ports so i wrote this in and still had no luck server.Server.SetSocketOption(SocketOptionLevel.Socket, SocketOptionName.ReuseAddress, 1); How do i solve this error? -edit- socket error 10013 I did notice if i close FireFox (with its many tabs) and run the program it works... Maybe it has something to do with a connection? (i had ajax communicate with it). I wonder what did it. .net sockets windows-7 tcplistener share|improve this question asked Jul 23 '10 at 1:01 acidzombie24 42.7k137454814 Perhaps firefox was using the port that your app was trying to grab. –AndrewS Jul 23 '10 at 1:23 add a comment| 3 Answers 3 active oldest votes up vote 4 down vote This error code is caused by attempting to bind to a port that is exclusively in use by another process. The most common cause is accidentally starting the same service twice. If in doubt, a quick check of netstat -a TCPView should reveal which process has the port open. share|improve this answer edited Jul 23 '10 at 10:41 answered Jul 23 '10 at 1:37 Stephen Cleary 181k19303387 I see the list of local/remote ips and ports (along with state) but i dont see any process name. –acidzombie24 Jul 23 '10 at 1:58 I still cant tell what is happening. It feels like my winform app still is binding the address but it shouldnt be. NOTE: half the
Symptoms Whenever a Socket Error 10013 is present you will know it. Usually this error means that you cannot access your Windows mail messages. You will be able to open the e-mail program itself, but you will not be able to send or receive any e-mail messages rendering your program useless. Socket Error 10013 Causes A Socket Error 10013 can and will occur if there are settings on your computer that are not properly configured. In many instances it is an anti-virus software that will either not scan the e-mails properly or will take too long to scan them and thus prompt the error. Other possible causes can be a corrupt registry, misconfigured files with your firewall protection, or possibly a virus. Socket Error 10013 Fixes The easiest way to deal with a Socket Error 10013 is to disable the anti-virus scanning capabilities. Mostly speaking, a scan of your e-mails is an unnecessary step that can eat up CPU usage and cause a slowing and/or timing out of your PC which will cause the Socket Error 10013 to occur. Steps: Uninstall your anti-virus program. Restart your computer. Reinstall you anti-virus program in “Custom Mode.” When offered the choice for “E-mail Scanning” select no or uncheck the box. Complete setup. Restart your computer to allow effects to take hold. See Also Personal tools Namespaces Article Search Our Products Main Page Applications .Net Framework Error AOL Browser Errors Installer Errors Internet Explorer Macro Errors Media Player MS Outlook Network Errors Outlook Express Windows Live Articles DLL Errors Exe Errors Ocx Errors Operating Systems Windows 7 Windows Others Windows Vista Windows XP TuneUp Tips Browser Tuneup Computer Tuneup Pages About Us Cat List Support Contact Us Help Center How to Uninstall Refund Policy Legal Disclaimers Privacy policy End User License Agreement (EULA) Terms of use Copyright©2012wiki-errors.com.All rights reserved. Disclaimer: This website is not affiliated