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 request). these connections must be acknowledged by the 
receiving end (SYN,ACK reply). as long as this reply was not received, 
the connection is in a half-open state. Windows XP does only allow 10 of 
these half-open connections. File sharing programs or worms which try to 
send mass mail may cause this problem. I don't see any reason why XWin 
would cause this behaviour.



--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/



problem with keyboard

2006-08-16 Thread Rathi, Priti
Hi,
I am using the cygwin on Windows XP. I am opening the startkde from Linux on 
the Windows system. I am getting the Linux KDE window on Windows XP but there 
is problem with the keyboard. The keyboard does not work.
Please help me out what setting I need to do.
Thanks in advance,
-Priti
Content of /tmp/XWin.log.
 
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
(II) XF86Config is not supported
(II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information
winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel
winAllocateFBShadowGDI - Creating DIB with width: 1600 height: 1200 depth: 32
winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32
null screen fn ReparentWindow
null screen fn RestackWindow
InitQueue - Calling pthread_mutex_init
InitQueue - pthread_mutex_init returned
InitQueue - Calling pthread_cond_init
InitQueue - pthread_cond_init returned
winInitMultiWindowWM - Hello
winMultiWindowXMsgProc - Hello
winInitMultiWindowWM - Calling pthread_mutex_lock ()
winMultiWindowXMsgProc - Calling pthread_mutex_lock ()
MIT-SHM extension disabled due to lack of kernel support
XFree86-Bigfont extension local-client optimization disabled due to lack of shar
ed memory support in the kernel
(--) Setting autorepeat to delay=500, rate=31
(--) winConfigKeyboard - Layout: 0409 (0409) 
(--) Using preset keyboard for English (USA) (409), type 4
(--) 3 mouse buttons found
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from li
st!
winInitMultiWindowWM - pthread_mutex_lock () returned.
winProcEstablishConnection - Hello
winInitClipboard ()
winClipboardProc - Hello
DetectUnicodeSupport - Windows NT/2000/XP
winProcEstablishConnection - winInitClipboard returned.
winInitMultiWindowWM - pthread_mutex_unlock () returned.
winMultiWindowXMsgProc - pthread_mutex_lock () returned.
winClipboardProc - DISPLAY=127.0.0.1:0.0
winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0
winMultiWindowXMsgProc - pthread_mutex_unlock () returned.
winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0
winClipboardProc - XOpenDisplay () returned and successfully opened the display.
winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the disp
lay.
winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the di
splay.
winProcSetSelectionOwner - Clipboard not yet started, aborting.
winProcSetSelectionOwner - Clipboard not yet started, aborting.
 
 

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/



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 correct, XWin
opens many connections but mainly to itself or for listening -- that's what
you'll see with netstat, but to find the cause of the original problem what we
are interested is in connections between the 2 computers, here (if I'm not
wrong) XWin will start a connection on the default xdmcp port then follow on
another port.

 The error results from a program which tries to open many connections at
 a time (SYN request). these connections must be acknowledged by the
 receiving end (SYN,ACK reply). as long as this reply was not received,
 the connection is in a half-open state. Windows XP does only allow 10 of
 these half-open connections. File sharing programs or worms which try to
 send mass mail may cause this problem. I don't see any reason why XWin
 would cause this behaviour.

Exactly.  Thanks for the explanation.
-- 
René Berber


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/