🚀 go-pugleaf

"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:4743c58d$1@newsgroups.borland.com...
>
> "Dennis Jones" <nospam@nospam.com> wrote in message
> news:474384f3$1@newsgroups.borland.com...
>
>> The address is "" (an empty string).
>
> That will bind the server to all available IP addresses on the machine.

Yes, because that's exactly what I want.  The application allows the user to 
choose from one or more specific adapters (if desired), or "Any Available" 
adapter, in which case "" (empty string) is used to allow client connections 
from any adapter, regardless of its IP address.


>> In this particular case, the port number was 5018.
>
> And port 5018 does not appear anywhere in netstat -a or -b for any IP
> address or hostname while the error is occuring?

Yes, that is correct.  That's what's so frustrating about the whole thing. 
If netstat -a showed me that the port was in use, then at least I would know 
where to start looking.  But since it doesn't, I don't know if the problem 
is due to my application (failing to close the socket correctly in some 
unusual circumstance), or the OS doing something funky, or if it is 
something else entirely.

It seems reasonable that it could be caused by me killing the application 
since I do that on occasion via the debugger, but the error usually occurs 
when there has been such a long period of time since I last ran the 
application, that any memory of what I was doing at the time (or of how I 
closed it) has long since been forgotten.

I guess all I can do now is wait until it happens again and then see if I 
can find some way to figure out what's causing it.  Any suggestions on how 
to go about doing would be most welcome.  In the meantime, do you know of 
any way to clear the socket so that the IP/port can be used without having 
to reboot the machine?

Thanks for your time, Remy.

- Dennis