Error 10013 (WSAEACCES) is perfectly legitimate.
"Another possible reason for the WSAEACCES error is that when the bind
function is called (on Windows NT 4.0 with SP4 and later), another
application, service, or kernel mode driver is bound to the same address
with exclusive access"
10048 (WSAEADDRINUSE) says:
"Typically, only one usage of each socket address (protocol/IP
address/port) is permitted. This error occurs if an application attempts
to bind a socket to an IP address/port that has already been used for an
existing socket, or a socket that was not closed properly, or one that
is still in the process of closing"
Reference :
http://msdn.microsoft.com/en-us/library/windows/desktop/ms740668%28v=vs.85%29.aspx
Perhaps the binding to actual IP address (127.0.01, or local interface)
you use will result in one of the errors, and binding to 0.0.0.0 would
result in the other (depending of course on the conflicting bind)
Regardless though, Graham found his victim :)
Lester
On 15/11/2012 12:52, Graham Powell wrote:
Error attached.
Graham
-----Original Message-----
From: twsocket-boun...@elists.org [mailto:twsocket-boun...@elists.org] On
Behalf Of François Piette
Sent: 14 November 2012 19:54
To: 'ICS support mailing'
Subject: Re: [twsocket] ICS WebServer Demo
The problem was that the "World Wide Web Publishing Services" was running.
You should have got the error 10048 Socket already in use. You reported
error 10013. Strange.
--
francois.pie...@overbyte.be
Embarcadero MVP
http://www.overbyte.be
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
