Newsgroups : Borland : borland.public.delphi.internet.winsock : 2008 Jul : RE: Could not bind socket error

www.cryer.info
Managed Newsgroup Archive

RE: Could not bind socket error

Subject:RE: Could not bind socket error
Posted by:"Hannes Gouws" (hannes.gou..@bcx.co.za)
Date:Thu, 31 Jul 2008 09:43:51

Hi Remy

Thanks for your comments.

But like I said "I have tried checking with "netstat -a -b -n"  but nowhere
can I find which
other app / service is using that ip / port combination....."

Turns out, indy throws this exception when the IP does not "exist". i.e. My
network adpater's IP is 192.168.1.1, when I call active := true, it works,
however when I set the IP to some IP that does not "exist" on my system i.e.
156.0.1.2 it throws the exception.

Is this how it is supposed to work?


I'm using D7 and the Indy snapshot for from 14/07/2008


Regards
Hannes

Replies:

www.cryer.info
Managed Newsgroup Archive