Re: 'cygcheck -p' timeout on WinXP (Winsock error 12002)

2010-12-12 Thread Christopher Faylor
On Sat, Dec 11, 2010 at 09:37:07PM -0800, Kenneth Wolcott wrote: >Hi; > >On Sat, Dec 11, 2010 at 17:43, Jeffrey Walton wrote: >> Hi All, >> >> Windows XP, fully patched. Cygwin, latest download from website >> (installed today). >> >> It appears cygcheck times out on Windows XP. The timeout occurs

Re: 'cygcheck -p' timeout on WinXP (Winsock error 12002)

2010-12-12 Thread Kenneth Wolcott
Hi; On Sat, Dec 11, 2010 at 17:43, Jeffrey Walton wrote: > Hi All, > > Windows XP, fully patched. Cygwin, latest download from website > (installed today). > > It appears cygcheck times out on Windows XP. The timeout occurs with > the Windows firewall up and down. Other downloads are function fin

'cygcheck -p' timeout on WinXP (Winsock error 12002)

2010-12-11 Thread Jeffrey Walton
Hi All, Windows XP, fully patched. Cygwin, latest download from website (installed today). It appears cygcheck times out on Windows XP. The timeout occurs with the Windows firewall up and down. Other downloads are function fine. Attached is a Wireshark trace for your enjoyment. Jeff jeff...@de

Re: Using custom Winsock socket functions with Cygwin

2010-06-02 Thread Bruce Cran
On Tue, 1 Jun 2010 20:06:08 +0100 Bruce Cran wrote: > I have a Winsock provider DLL which communicates with a kernel SCTP > stack. I'd like to enable applications built with both Visual Studio > and Cygwin to run because there's lots of code that's been ported from >

Using custom Winsock socket functions with Cygwin

2010-06-01 Thread Bruce Cran
I have a Winsock provider DLL which communicates with a kernel SCTP stack. I'd like to enable applications built with both Visual Studio and Cygwin to run because there's lots of code that's been ported from Linux. However, the problem I've come across is that because I have

Re: can some one please help me fix compiling errors related to winsock and sys/types and fd_set...etc

2009-12-24 Thread Andy Koppe
2009/12/25 Mark Geisert: > Josh writes: > [...a bunch of detailed stuff...] > > If this were really a Cygwin program you likely wouldn't be #include-ing > winsock.h.  Is this a native Windows program you're just trying to build with > gcc?  If so, you likely don't want Cygwin, you want MinGW, a sep

Re: can some one please help me fix compiling errors related to winsock and sys/types and fd_set...etc

2009-12-24 Thread Mark Geisert
les. In any case with Cygwin you don't want to be linking against winsock anyway; Cygwin supplies the network functions itself. You'll need more assistance than I can give, so good luck. Others here may be able to help. Cheers, ..mark -- Problem reports: http://cygwin.co

can some one please help me fix compiling errors related to winsock and sys/types and fd_set...etc

2009-12-24 Thread Josh
I have a 64bit Vista machine. Please help me fix these two errors so I can compile, they seem to be related to winsock in some way PLEASE HELP I'm trying to compile a C program and here is what I'm getting: bash-3.2$ make -f Makefile gcc -O3 -oibsp.exe main.c gl.c string.c physics.

Re: WinSock: Connections/min & MaxUserPort=5000

2009-02-08 Thread Lee
You're right - it's not a cygwin problem; I think nmap has the same problem & suggested fix. here's what I changed the values to: - TCP/IP parameter changes start / run / regedit HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters - increase max ephemerial port number from 5000

WinSock: Connections/min & MaxUserPort=5000

2009-02-08 Thread Uwe Appelt
Dear Cygwin-guys, i'm trying to run a bioinformatic tools suite from UCSC (http://genome.ucsc.edu/) under cygwin and unfortunately there seems to be a incompatibilty with regard to the standard TcpStack-settings in *ix and windows. I hope, this is the right place to discuss this. This is my envi

RE: Winsock

2006-12-08 Thread tbrowder
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Lucas Charron > Sent: Thursday, December 07, 2006 13:21 > To: cygwin@cygwin.com > Subject: Winsock ... > I'm using C::B(http://www.codeblocks.org) over cygwin. I'm &g

RE: Winsock

2006-12-07 Thread Dave Korn
On 07 December 2006 19:21, Lucas Charron wrote: > I can connect to my listening socket from within the > same process and transmit data to and from the "server" and "client", > but, if I try to use a web-browser, I get "This connection was denied" > and the server application has no notification o

Winsock

2006-12-07 Thread Lucas Charron
I'm using C::B(http://www.codeblocks.org) over cygwin. I'm testing a socket stream library of my own creation (using Winsock2). My "server" is currently a simple HTTP server (sends out a blank html page saying "you are here"). I can connect to my listening socket from within the same process an

Re: IP_MULTICAST_IF et. all / Winsock[2] value conflict

2005-09-30 Thread Corinna Vinschen
t; > wouldn't be static values anymore, they would have to be translated > > into function calls to retrieve the right value at runtime. That's > > bound to break building applications which rely on getting constant > > values. > > That wasn't what I was suggest

Re: IP_MULTICAST_IF et. all / Winsock[2] value conflict

2005-09-30 Thread Brian Ford
nction calls to retrieve the right value at runtime. That's > bound to break building applications which rely on getting constant > values. That wasn't what I was suggesting. We can simply translate the current constant Winsock 1 values to Winsock 2 ones when necessary in cygwin_[s

Re: IP_MULTICAST_IF et. all / Winsock[2] value conflict

2005-09-30 Thread Corinna Vinschen
On Sep 29 12:04, Brian Ford wrote: > On Thu, 29 Sep 2005, Corinna Vinschen wrote: > > There's no easy fix right now. We have to drop all traces of Winsock1 > > in Cygwin and change the headers accordingly. > > Can't we just translate these based on a flag indicating what version we > dynamically

Re: IP_MULTICAST_IF et. all / Winsock[2] value conflict

2005-09-29 Thread Brian Ford
p://support.microsoft.com/default.aspx?scid=kb;en-us;257460 > > > > IP_MULTICAST_IF can have two values (2 or 9) depending on whether you're > > linking to Winsock 1 or 2. By preprocessing my source and looking in > > /usr/include/cygwin/socket.h, I see we are using th

Re: IP_MULTICAST_IF et. all / Winsock[2] value conflict

2005-09-29 Thread Corinna Vinschen
_MULTICAST_IF can have two values (2 or 9) depending on whether you're > linking to Winsock 1 or 2. By preprocessing my source and looking in > /usr/include/cygwin/socket.h, I see we are using the value 2 which means > it will only work if we link to Winsock 1? > > IIRC, Cygwin d

IP_MULTICAST_IF et. all / Winsock[2] value conflict

2005-09-29 Thread Brian Ford
re linking to Winsock 1 or 2. By preprocessing my source and looking in /usr/include/cygwin/socket.h, I see we are using the value 2 which means it will only work if we link to Winsock 1? IIRC, Cygwin dynamically loads which ever library is present or version 2 if both are available? I assume we a

Re: linking programs with winsock API - Problems

2004-11-21 Thread Brian Dessent
[EMAIL PROTECTED] wrote: > I am new to using the winsock programs. I am having problem in creating the > runtime binaries using the socket programming with winsock API. > > The error message received on the console is :- cannot find -lwinsock32 If you are compiling a _cygwin_ pro

linking programs with winsock API - Problems

2004-11-21 Thread krishna_unf
Hi, I am new to using the winsock programs. I am having problem in creating the runtime binaries using the socket programming with winsock API. The error message received on the console is :- cannot find -lwinsock32 The command used to compile and like the program: $ gcc -o winclient.exe

Re: Error compiling code using winsock functions

2003-07-04 Thread Brian Dessent
David None wrote: > > Hi there, thanks for the reply, but I've tried the methods suggested (just > using windows.h and #define Win32_Winsock), also as Win32_Winsock is > deprecated, I also tried defining __USE_W32_SOCKETS > but I'm still receiving the same error: > > I get the following error: >

RE: Error compiling code using winsock functions

2003-07-04 Thread David None
Hi there, thanks for the reply, but I've tried the methods suggested (just using windows.h and #define Win32_Winsock), also as Win32_Winsock is deprecated, I also tried defining __USE_W32_SOCKETS but I'm still receiving the same error: I get the following error: "iphdrinc.o(.text+0x820):iphdrinc

RE: Error compiling code using winsock functions

2003-07-04 Thread Hannu E K Nevalainen \(garbage mail\)
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf > Of David None > Hi there, I've recently been trying some programming with sockets in > windows, and I obtained the following code from a microsoft book called > "Network programming for microsoft windows"... > the code is as follows:

Error compiling code using winsock functions

2003-07-03 Thread David None
m(USHORT *buffer, int size) { unsigned long cksum=0; while (size > 1) { cksum += *buffer++; size -= sizeof(USHORT); } if (size) { cksum += *(UCHAR*)buffer; } cksum = (cksum >> 16) + (cksum & 0x); cksum += (cksum >>16); retur

winsock error 10048 (errno 112) from ssh

2003-06-04 Thread Mark Paulus
nection to si->exitsock 0x3E45 91 181643448 [main] ssh 3220 __set_winsock_errno: socket_cleanup:1356 - winsock error 10048 -> errno 112 169 181643617 [main] ssh 3220 socket_cleanup: connect failed 89231 181732848 [ttyin] ssh 3220 fhandler_termios::line_edit: char 0 226 1817330

Re: exim 4.12-3 winsock problem (was Re: 1.3.21)

2003-02-27 Thread Jason Tishler
arting wsock problem, using your specially > instrumented code. Is access to both keys above needed for a > successful start? No, only the winsock2 one is necessary. > Can you also confirm that wsock starts correctly under strace even > when there is no access to the keys above? Y

Re: exim 4.12-3 winsock problem (was Re: 1.3.21)

2003-02-26 Thread Pierre A. Humblet
Jason Tishler wrote: > > Using good old fashioned strings and Andre's suggestion I have isolated > the registry keys requiring read access for Everyone (which did not > already have it) to the following: > > 1. HKLM\System\CurrentControlSet\Services\Winsock\Paramete

Re: exim 4.12-3 winsock problem (was Re: 1.3.21)

2003-02-26 Thread Jason Tishler
suggestion I have isolated the registry keys requiring read access for Everyone (which did not already have it) to the following: 1. HKLM\System\CurrentControlSet\Services\Winsock\Parameters 2. HKLM\System\CurrentControlSet\Services\WinSock2\Parameters I guess that the above is no great su

Re: exim 4.12-3 winsock problem (was Re: 1.3.21)

2003-02-25 Thread Andre Bleau
Pierre, Jason, Sorry to jump in now. A good way to resolve that kind of problem is auditing. As administrator, enable auditing. With regedt32, enable auditing on selected keys and subkeys for read or write failure, as required. You will find results in event viewer, in the security log. Yes,

Re: exim 4.12-3 winsock problem (was Re: 1.3.21)

2003-02-25 Thread Pierre A. Humblet
Jason Tishler wrote: > Bingo! The following key did not have read access for Everyone: > > HKEY_LOCAL_MACHINE\SYSTEM > Great! > After granting access, then exim would start up even though its primary > group is my mail group and not the Users one. > > Do you want me further isolate? If so

Re: exim 4.12-3 winsock problem (was Re: 1.3.21)

2003-02-25 Thread Jason Tishler
Pierre, On Tue, Feb 25, 2003 at 04:19:03PM -0500, Pierre A. Humblet wrote: > Jason Tishler wrote: > > > > > Another possibility is registry access. Is there a way to insure > > > that Everyone has read access to the whole registry? > > > > regedt32 can change permissions. Any particular subtree

Re: exim 4.12-3 winsock problem (was Re: 1.3.21)

2003-02-25 Thread Pierre A. Humblet
Jason Tishler wrote: > > > Another possibility is registry access. Is there a way to insure > > that Everyone has read access to the whole registry? > > regedt32 can change permissions. Any particular subtree that I should > try? Right, I had forgotten. I am still using regedit. First see if any

Re: exim 4.12-3 winsock problem (was Re: 1.3.21)

2003-02-25 Thread Jason Tishler
Pierre, On Tue, Feb 25, 2003 at 03:44:03PM -0500, Pierre A. Humblet wrote: > Jason Tishler wrote: > > I tried adding a group:mail:r-x ACL to the following: > > > > /mnt/c > > [snip] > > Thanks No problem. > > but I still failed in the same way. > > With hindsight it's not surprising be

Re: exim 4.12-3 winsock problem (was Re: 1.3.21)

2003-02-25 Thread Pierre A. Humblet
Christopher Faylor wrote: > > Perhaps this is completely off the wall but I don't recall anyone > answering my question about exim and pthreads. Does exim use threads? > No. Pierre -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.

Re: exim 4.12-3 winsock problem (was Re: 1.3.21)

2003-02-25 Thread Christopher Faylor
On Tue, Feb 25, 2003 at 03:44:03PM -0500, Pierre A. Humblet wrote: >Jason Tishler wrote: >> >> I tried adding a group:mail:r-x ACL to the following: >> >> /mnt/c >> /mnt/c/WINNT >> /mnt/c/WINNT/system32 >> /mnt/c/WINNT/system32/drivers >> /mnt/c/WINNT/system32/drivers/etc >>

Re: exim 4.12-3 winsock problem (was Re: 1.3.21)

2003-02-25 Thread Pierre A. Humblet
Jason Tishler wrote: > > I tried adding a group:mail:r-x ACL to the following: > > /mnt/c > /mnt/c/WINNT > /mnt/c/WINNT/system32 > /mnt/c/WINNT/system32/drivers > /mnt/c/WINNT/system32/drivers/etc > /mnt/c/WINNT/system32/drivers/etc/services > /mnt/c/WINNT/system32/*.dll

Re: exim 4.12-3 winsock problem (was Re: 1.3.21)

2003-02-25 Thread Jason Tishler
Pierre, On Tue, Feb 25, 2003 at 12:43:31PM -0500, Pierre A. Humblet wrote: > Jason Tishler wrote: > > The above fixed the problem. I apologize for not being able to > > figure this out myself. > > Actually I'd rather have you hit this problem than almost anybody > else. Figuring out what was ha

Re: exim 4.12-3 winsock problem (was Re: 1.3.21)

2003-02-25 Thread Pierre A. Humblet
Jason Tishler wrote: > > Pierre, > > On Tue, Feb 25, 2003 at 10:02:49AM -0500, Pierre A. Humblet wrote: > > So I suggest a simple test: edit /etc/passwd and change the gid of the > > exim user to 545, then run again. > > The above fixed the problem. I apologize for not being able to figure > th

Re: exim 4.12-3 winsock problem (was Re: 1.3.21)

2003-02-25 Thread Jason Tishler
Pierre, On Tue, Feb 25, 2003 at 10:02:49AM -0500, Pierre A. Humblet wrote: > So I suggest a simple test: edit /etc/passwd and change the gid of the > exim user to 545, then run again. The above fixed the problem. I apologize for not being able to figure this out myself. > By the way, I am not s

Re: exim 4.12-3 winsock problem (was Re: 1.3.21)

2003-02-25 Thread Pierre A. Humblet
2: changed uid/gid: running as a daemon uid=1008 gid=1009 auxiliary group list: 513 544 545 1009 4.12-3 changed uid/gid: forcing real = effective uid=1008 gid=1009 pid=2024 auxiliary group list: 1009 We see that setgroups is active in 4.12-3 and that supplementary groups were shed. I sus

Re: exim 4.12-3 winsock problem (was Re: 1.3.21)

2003-02-25 Thread Jason Tishler
Earnie, On Mon, Feb 24, 2003 at 03:15:56PM -0500, Earnie Boyd wrote: > Jason Tishler wrote: > >Any further suggestions? Note this is very painful to debug because > >I can't use gdb and I can't send mail when trying to debug. Sigh... > >:,( > > You might try DebugView from sysinternals.com. Th

Re: exim 4.12-3 winsock problem (was Re: 1.3.21)

2003-02-25 Thread Jason Tishler
Pierre, On Mon, Feb 24, 2003 at 05:15:38PM -0500, Pierre A. Humblet wrote: > Jason Tishler wrote: > > On Mon, Feb 24, 2003 at 04:06:01PM -0500, Pierre A. Humblet wrote: > > > If you run with -d you will see that exim sheds all supplementary > > > groups. > > > > I was just following the README: >

Re: exim 4.12-3 winsock problem (was Re: 1.3.21)

2003-02-24 Thread Pierre A. Humblet
Jason Tishler wrote: > > Pierre, > > On Mon, Feb 24, 2003 at 04:06:01PM -0500, Pierre A. Humblet wrote: > > If you run with -d you will see that exim sheds all supplementary > > groups. > > I was just following the README: > >cygrunsrv -I exim -p /usr/bin/exim -e CYGWIN=ntsec \ >

Re: exim 4.12-3 winsock problem (was Re: 1.3.21)

2003-02-24 Thread Jason Tishler
Pierre, On Mon, Feb 24, 2003 at 04:06:01PM -0500, Pierre A. Humblet wrote: > If you run with -d you will see that exim sheds all supplementary > groups. I was just following the README: cygrunsrv -I exim -p /usr/bin/exim -e CYGWIN=ntsec \ -a "-bdf -q15m" -d "Exim Mail Transfer Ag

Re: exim 4.12-3 winsock problem (was Re: 1.3.21)

2003-02-24 Thread Pierre A. Humblet
Jason Tishler wrote: > > Pierre, > > > On Fri, Feb 21, 2003 at 01:22:01PM -0500, Pierre A. Humblet wrote: > > > This reminds me of something similar, possibly last month. Look for > > > "exim", "services", "gerritt" In the end it was because exim was > > > running as a special user who didn't ha

Re: exim 4.12-3 winsock problem (was Re: 1.3.21)

2003-02-24 Thread Earnie Boyd
Jason Tishler wrote: Any further suggestions? Note this is very painful to debug because I can't use gdb and I can't send mail when trying to debug. Sigh... :,( You might try DebugView from sysinternals.com. The strace data will appear in a nice searchable window. This method avoids the it wo

exim 4.12-3 winsock problem (was Re: 1.3.21)

2003-02-24 Thread Jason Tishler
spondence from the previous similar problem. I > had a private debugging conversation involving sending long straces > etc... > > It was a winsock error due to permission problem. winsock didn't init > properly, and cywin went ahead anyway! > > *** >

Cygwin setsockopt calls winsock 1 implementation

2002-04-29 Thread Richard Lewis
clear from this kb article: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q257460 between winsock 1.1 and 2.0 M$ changed their IP_XXX defines. It seems the set/getsockopt functions from wsock32 understand the Winsock 1.1 defines and those from ws2_32.dll understand those for Winsock2.

Cygwin Winsock recv/WSARecv(..., MSG_PEEK) patch

2002-04-29 Thread Jason Tishler
Eric, Attached is a patch (against fetchmail 5.9.11) that works around the Microsoft Winsock recv/WSARecv(..., MSG_PEEK) problem that I originally post to fetchmail-friends in: http://lists.ccil.org/pipermail/fetchmail-friends/2001-August/000906.html This patch is essentially the same as