Article View: borland.public.cppbuilder.internet.socket
Article #725Re: 'could not bind socket' error
From: Dennis Jones
Date: Wed, 21 Nov 2007 01:08
Date: Wed, 21 Nov 2007 01:08
40 lines
2253 bytes
2253 bytes
"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message news:474377e3$1@newsgroups.borland.com... > Are you sure you are looking for the port that you are actually using in > your code? Of course. > What exactly are you setting for the IP/Port of your server? The address is "" (an empty string). In this particular case, the port number was 5018. > Please show your actual code. I *did* show my actual code -- see my second post in this thread. >> So, being certain that netstat does not show the port in use, and >> being certain that the app is not already running, what would you >> suggest I do the next time this occurs? > > The error is not possible under those conditions. Bound sockets can't > hide from netstat. So you say, but there are only two possibilities: 1) The port number is listed but I fail to see it every single time I look for it 2) The port number is not listed I don't know which it is, but it's not #1! :-) The next time this happens (I'll try to induce it), I'll post netstat's output for you. - Dennis
Technical Details
Message-ID:
<474384f3$1@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!feeder1-2.proxad.net!proxad.net!feeder1-1.proxad.net!feeder.news-service.com!newsfeed.freenet.de!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mailReferences:
<47431d9f$1@newsgroups.borland.com> <474342ce@newsgroups.borland.com> <47434723$1@newsgroups.borland.com> <474358f3@newsgroups.borland.com> <47436c88$1@newsgroups.borland.com> <474377e3$1@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 11508e,128d041863311899 X-Google-Attributes: gid11508e,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit From: "Dennis Jones" <nospam@nospam.com> Newsgroups: borland.public.cppbuilder.internet.socket References: <47431d9f$1@newsgroups.borland.com> <474342ce@newsgroups.borland.com> <47434723$1@newsgroups.borland.com> <474358f3@newsgroups.borland.com> <47436c88$1@newsgroups.borland.com> <474377e3$1@newsgroups.borland.com> Subject: Re: 'could not bind socket' error Date: Tue, 20 Nov 2007 17:08:05 -0800 Lines: 42 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.3138 X-RFC2646: Format=Flowed; Response X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 NNTP-Posting-Host: 71.245.109.58 Message-ID: <474384f3$1@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1195607283 71.245.109.58 (20 Nov 2007 17:08:03 -0700) Path: arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!feeder1-2.proxad.net!proxad.net!feeder1-1.proxad.net!feeder.news-service.com!newsfeed.freenet.de!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail