Cygwin

[yesthattom]

I have a Win2k system at home. It constantly drops TCP connections. For some reason I believe it is more likely to happen when I'm running Cygwin and doing network-related stuff with Cygwin.

Here's the problem. I'm not doing a LOT of network stuff with Cygwin SSH. I basically lose my connections every couple minutes.

I've verified that this problem happens when I remove my home firewall (a D-LINK DI-714) and talk directly to my cable modem. So that eliminates potential buggy firmware on my D-LINK.

I've been suffering with this problem for ages but now its really bad. I hate to start doing the "keep changing one thing and see if it goes away" drill, but it looks like I'm finally going to have to do that. Now, which thing should I change first?

--tal

Comments

[airshipjones.livejournal.com]

Try the NIC first. Or even try updating the driver, especially if you have installed the latest win2k SP. That seems to cause a lot of issues with drivers. MS seems to write their SPs to force driver updates.

Also, is this an issue you only have with the WIn2k machine? I finally had to have AT&T come out and replace my cable modem with a newer one. The older one was appearently a problematic model with limited diagnostic features. That would be my second place to look. And of course the obligatory check of the cables and connections. Good luck with it.

[yesthattom.livejournal.com]

Dang, that really got my hopes up. It turns out I upgraded the driver to the latest one that Dell provides ages ago. I wonder if that's the problem :-)

Anyway, I've turned off Autosense and hardcoded it to 10M half-duplex. My theory is that autosense tends to be flakey on other products, maybe the D-Link isn't good at it either.