Windows to Linux and vice-versa

cwr at netcom.co.uk cwr at netcom.co.uk
Thu Sep 29 07:37:48 UTC 2011


Quoting Matt Mackall <mpm at selenic.com>:

> On Wed, 2011-09-28 at 20:55 +0100, cwr at netcom.co.uk wrote:
>
> My suspicion is you have something like a personal firewall on your
> Windows box that's quietly refusing outgoing connections by 'weird
> programs' like Mercurial.
>
> Both your browser and the hg client speak HTTP to the same port on
> server. For that to break, something on the client must be
> distinguishing between the two before a packet even leaves your box.
>
> (Crucially, you didn't tell us which host was running Wireshark. I
> assume it's on the Windows side. My theory is that if you run it on the
> Linux side, you'll never see the packets arrive.)

No, Wireshark is on the Linux box. The SYN packets arrive at the Linux
box and are summarily rejected with RST. The Windows setup has the firewall
off, there's no firewall on the router, and the Linux box doesn't have
a firewall (poor Linux box).

And I'm using IP addresses, so it shouldn't be a name resolution problem.
(And in fact both machines know each-others name.)

Hmmm.  Scuffling around in the lower levels of Python/TCPIP does not seem
appealing, or productive.

Will






More information about the Mercurial mailing list