From: "Michael T. Babcock" <mbabcock@fibrespeed.net>
To: devik <devik@cdi.cz>
Cc: linux-kernel@vger.kernel.org, lartc@mailman.ds9a.nl
Subject: Re: [LARTC] TCP probably broken in W2K
Date: Thu, 23 Jan 2003 10:56:26 -0500 [thread overview]
Message-ID: <3E3010AA.4040107@fibrespeed.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0301231309020.518-100000@devix>
devik wrote:
>this is not exactly Linux problem but it is VERY interesting
>and as I'm linux developer I'm posting it here.
>
>
I have Win2k and XP machines and I've had many symptoms of a broken
TCP/IP stack in my TCP programming on those platforms. I communicate
with Linux 2.2.19 and 2.2.21 machines running tcpserver _a lot_ from
these, and I have to do a number of strange things to make it all work.
I don't know if my layer-4 problems would help, but if they would, I
could try and describe them for you.
--
Michael T. Babcock
C.T.O., FibreSpeed Ltd.
http://www.fibrespeed.net/~mbabcock
prev parent reply other threads:[~2003-01-23 15:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 12:12 TCP probably broken in W2K devik
2003-01-23 15:56 ` Michael T. Babcock [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E3010AA.4040107@fibrespeed.net \
--to=mbabcock@fibrespeed.net \
--cc=devik@cdi.cz \
--cc=lartc@mailman.ds9a.nl \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox