public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk> To: cygwin-xfree@cygwin.com Cc: hoes.maarten@gmail.com Subject: Re: Cygwin/X XDMCP Issue Date: Sun, 22 Feb 2015 13:55:00 -0000 [thread overview] Message-ID: <54E9DFCF.9050209@dronecode.org.uk> (raw) In-Reply-To: <54E77EC0.2060702@gmail.com> On 20/02/2015 18:36, Maarten Hoes wrote: > I am (again) experiencing some issues when running Cygwin/X in > combination with XDMCP. Opening a cygwin prompt and running 'startxwin' > works as expected. But when I try to connect to my remote Linux system > with the command 'xwin -query 192.168.0.21' (or with the 'XLaunch' > program and choose XDMCP) the screen stays black. Things used to work, > but apparently something broke my setup. > > Im running the latest Cygwin/X, and applied all current updates on my > Fedora 21 Linux system. Im running KDM. > > Any and all ideas are more than welcome, as I have no idea whats going > on here. > Package: version 1.16.3-1 built 2014-12-30 > xwin -query 192.168.0.21 -logverbose 3 > 1 0.000000 192.168.0.20 -> 192.168.0.21 XDMCP 49 Query > 2 0.013254 192.168.0.21 -> 192.168.0.20 XDMCP 100 Willing > 3 0.227426 192.168.0.20 -> 192.168.0.21 XDMCP 360 Request > 4 0.227831 192.168.0.21 -> 192.168.0.20 XDMCP 94 Accept > 5 0.227968 192.168.0.20 -> 192.168.0.21 XDMCP 71 Manage Assuming your wireshark filter includes X11, you should be seeing a X11 connection request from 192.168.0.21 to the X server here. Since the same X server version was working for you before (to a different IP address), I can only suggest you examine what else has changed. You might want to check your firewall/network configuration. > 6 2.225721 192.168.0.20 -> 192.168.0.21 XDMCP 71 Manage > 7 6.229538 192.168.0.20 -> 192.168.0.21 XDMCP 71 Manage > 8 14.230544 192.168.0.20 -> 192.168.0.21 XDMCP 71 Manage > 9 30.228625 192.168.0.20 -> 192.168.0.21 XDMCP 71 Manage -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/
next prev parent reply other threads:[~2015-02-22 13:55 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-20 18:36 Maarten Hoes 2015-02-21 8:15 ` Maarten Hoes 2015-02-22 13:55 ` Jon TURNEY [this message] 2015-02-22 21:09 ` Maarten Hoes 2015-02-22 21:39 ` Maarten Hoes 2015-02-23 13:01 ` Michael DePaulo [not found] ` <54EB431C.3010000@gmail.com> [not found] ` <54EB4848.3070607@gmail.com> 2015-02-23 15:55 ` Maarten Hoes -- strict thread matches above, loose matches on Subject: below -- 2015-01-17 11:49 Maarten Hoes 2015-01-17 21:06 ` Maarten Hoes 2015-01-18 8:57 ` Maarten Hoes 2015-01-22 7:46 ` Maarten Hoes 2015-02-02 15:21 ` Jon TURNEY 2015-02-02 15:26 ` Maarten Hoes 2015-02-13 7:24 ` Maarten Hoes 2015-02-13 16:13 ` Jon TURNEY
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=54E9DFCF.9050209@dronecode.org.uk \ --to=jon.turney@dronecode.org.uk \ --cc=cygwin-xfree@cygwin.com \ --cc=hoes.maarten@gmail.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).