This is the mail archive of the
mailing list for the Cygwin project.
Re: Problem with accept(2) on the 1003.20.0.0 release
- From: "Elfyn McBratney" <elfyn-cygwin at exposure dot org dot uk>
- To: "cygwin" <cygwin at cygwin dot com>,<jeff_burch at agilent dot com>
- Date: Fri, 14 Feb 2003 21:16:53 -0000
- Subject: Re: Problem with accept(2) on the 1003.20.0.0 release
- References: <FC0B9DA2600ED4118F76009027AA5DDD0485B369@ALEX2>
- Reply-to: "Elfyn McBratney" <cygwin at cygwin dot com>
> Cheers to Elfyn!
> > Do you by any chance have any firewall software running on the
> > machine? ZoneAlaram perhaps?
> > Regards,
> > Elfyn McBratney
> > firstname.lastname@example.org
> > www.exposure.org.uk
> I had version 3.21 of Aventail's connect SW installed on the problem
machine. I removed it, reinstalled the lastest cygwin, tested!, re-installed
version 4.1.2 of Avantail, tested again, and now all is well...
> Accept(2) now works as expected with this version of Aventail...
> If anyone has a clue as to what was going wrong, I'd love to know.
Remember, the problem only occurred with the latest cygwin and this older
version of Avantail. The same code compiled with Visual Studio always ran
fine. So, there is some interaction between cygwin1.dll and Aventail...
It may be, well I know NIS and ZoneAlarm do it, that some firewall software
install their own versions of winsock and maybe other dll's so they can
enhance their firewall code and intrusion detection. Don't know what
Aventail is but it may have done the same. Maybe just something else...but
who knows :-)
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html