Or...Crazy as it sounds, there was an attempt to bind to "valid
looking" address perhaps derived from a host file entry or some such.
One thing tcpdump could do for you is tell you whether there was an
attempt to use something unreasonable (like 127.0.0.0), or maybe a
non-routable address.
===
Gregory Woodhouse
[EMAIL PROTECTED]
"The most incomprehensible thing about
the world is that it is at all comprehensible."
--Albert Einstein (1879-1955)
On Aug 3, 2005, at 7:02 PM, Darren Coolidge wrote:
Unless something is already bound to that address...
On 8/3/05, Greg Woodhouse <[EMAIL PROTECTED]> wrote:
Of course you are right. what confuses me is these old-fashioned
winsock errors. Under the scenario you derscribe, I'd expect a
connection reset, but instead we're getting an error suggesting that
the local(?) socket couldn't be bound to an address. That just
doesn't
make sense.
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
