🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: borland.public.cppbuilder.internet.socket
Article #719

Re: 'could not bind socket' error

#719
From: Dennis Jones
Date: Tue, 20 Nov 2007 20:48
23 lines
2086 bytes
"Dennis Jones" <nospam@nospam.com> wrote in message 
news:47434723$1@newsgroups.borland.com...

>>> I have checked "netstat -a" for any indication that the port is in
>>> use, but am never able to find anything.
>>
>> Why not?
>
> If I knew the answer to that, I wouldn't be asking the question in the 
> first place!!  That's the whole point..."netstat -a" does not show any 
> application instances that reference the port number I am trying to open 
> in my server. So if netstat does *not* show the port is in use, why would 
> the server socket complain that it *is* in use?  That's the essence of my 
> question.  I can find no indication whatsoever that the port is in use, 
> yet the server complains.  How can that be?

Oh, by the way, when the application is running normally, I *can* find the 
port number listed with "netstat -a".  So it is only strange cases when the 
application gives the error and I cannot find the port number listed with 
"netstat -a" that I am trying to understand.

- Dennis 
Technical Details
Message-ID: <4743480a$1@newsgroups.borland.com>
Path: arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!feeder3.cambrium.nl!feeder6.cambrium.nl!feed.tweaknews.nl!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
References: <47431d9f$1@newsgroups.borland.com> <474342ce@newsgroups.borland.com> <47434723$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>
Subject: Re: 'could not bind socket' error
Date: Tue, 20 Nov 2007 12:48:12 -0800
Lines: 25
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: <4743480a$1@newsgroups.borland.com>
X-Trace: newsgroups.borland.com 1195591690 71.245.109.58 (20 Nov 2007 12:48:10 -0700)
Path: arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!feeder3.cambrium.nl!feeder6.cambrium.nl!feed.tweaknews.nl!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