Re: TCP/IP Security Limits - WinXP and XWIN.exe

2006-08-16 Thread Alexander Gottwald
René Berber wrote: XWin only opens a couple of connections, with ssh -X it's only one connection. XWin opens no connection (except for xdmcp). It's a server and will only react on incoming connections. The error results from a program which tries to open many connections at a time (SYN

Re: TCP/IP Security Limits - WinXP and XWIN.exe

2006-08-16 Thread René Berber
Alexander Gottwald wrote: René Berber wrote: XWin only opens a couple of connections, with ssh -X it's only one connection. XWin opens no connection (except for xdmcp). It's a server and will only react on incoming connections. To clarify, and I knew when I wrote the above it wasn't quite

Re: TCP/IP Security Limits - WinXP and XWIN.exe

2006-08-15 Thread René Berber
Mark Edwards wrote: I am using cygwin on winXPSP2 to run a linux-hosted tk application. The application is invoked using a batch file which uses ssh to invoke the application remotely on a linux box and cause it to display its GUI on the windows desktop. Unfortunately, once I close the

Re: TCP/IP Security Limits - WinXP and XWIN.exe

2006-08-15 Thread Mark Edwards
On 8/16/06, René Berber [EMAIL PROTECTED] wrote: Mark Edwards wrote: I am using cygwin on winXPSP2 to run a linux-hosted tk application. The application is invoked using a batch file which uses ssh to invoke the application remotely on a linux box and cause it to display its GUI on the

Re: TCP/IP Security Limits - WinXP and XWIN.exe

2006-08-15 Thread René Berber
Mark Edwards wrote: On 8/16/06, René Berber wrote: [snip] netstat -nb (and a lot of patience) or netstat -anb (which of course will take a long time). Thanks for the comments René, however my point was that it is XWin.exe that seems to be invoking this behaviour. What is not clear to me is

Re: TCP/IP Security Limits - WinXP and XWIN.exe

2006-08-15 Thread Mark Edwards
On 8/16/06, René Berber [EMAIL PROTECTED] wrote: Mark Edwards wrote: On 8/16/06, René Berber wrote: [snip] netstat -nb (and a lot of patience) or netstat -anb (which of course will take a long time). Thanks for the comments René, however my point was that it is XWin.exe that seems to be

Re: TCP/IP Security Limits - WinXP and XWIN.exe

2006-08-15 Thread Larry Hall (Cygwin X)
Mark Edwards wrote: On 8/16/06, René Berber [EMAIL PROTECTED] wrote: Mark Edwards wrote: On 8/16/06, René Berber wrote: [snip] netstat -nb (and a lot of patience) or netstat -anb (which of course will take a long time). Thanks for the comments René, however my point was that it is

Re: TCP/IP Security Limits - WinXP and XWIN.exe

2006-08-15 Thread René Berber
Mark Edwards wrote: On 8/16/06, René Berber wrote: Mark Edwards wrote: [snip] My point was that you need to run netstat to make sure it is XWin... saying seems will not encourage anybody to look into this. FWIW I don't think XWin is going to come out as the problem, as I said I haven't