Firstly, thanks very much for taking the time to collect so much detailed information about this problem.
On 09/02/2011 15:36, Alexander Pokluda wrote: > Here is an excerpt from /var/log/messages on the VM that I'm trying to > connect to with XWin. > > This is what appears in the log after running > > XWin -from 10.3.20.159 -query 10.3.147.100 > > Feb 8 11:22:08 dev01 gdm[4097]: gdm_xdmcp_decode: Received opcode > QUERY from client 10.3.20.159 > Feb 8 11:22:08 dev01 gdm[4097]: gdm_xdmcp_handle_query: Opcode 2 from > 10.3.20.159 > Feb 8 11:22:08 dev01 gdm[4097]: gdm_xdmcp_host_allow: > client->hostname is ci0000001138531.xxx.net > Feb 8 11:22:08 dev01 gdm[4097]: gdm_xdmcp_send_willing: Sending > WILLING to 10.3.20.159 > Feb 8 11:24:16 dev01 gdm[4097]: gdm_xdmcp_decode: Received opcode > QUERY from client 10.3.20.159 > Feb 8 11:24:16 dev01 gdm[4097]: gdm_xdmcp_handle_query: Opcode 2 from > 10.3.20.159 [snip] > It seems that the "REQUEST" message sent by XWin somehow gets lost. > Although it shows up in the Wireshark trace, it never shows up in the > log on the VM. The other alternative is that the REQUEST arrives at the VM, but gdm doesn't like the contents for some reason. Possibly you could check that by wiresharking at that end. > On Tue, Feb 8, 2011 at 5:00 PM, Alexander Pokluda <[email protected]> wrote: >> Sorry for the delay in my response. >> >> No, I am not runnig the VMs locally. These VMs are being run and >> managed in a lab that I don't have access to, but I am expected to use >> VMs in the lab for development and testing on a new project. >> >> I have one physical network adapter in my computer and several virtual >> adapters since I do have VMware Workstation and Virtual Box installed. >> The IP address of the physical adapter is a static IP address set to >> 10.3.20.159 with /24 subnet mask. The VM that I've been trying to >> connect to has IP address 10.3.147.100 and /24 subnet mask. Running >> >> XWin -from 10.3.20.159 -query 10.3.147.100 >> >> doesn't work. A blank window opens and eventually closes and re-opens. >> This goes on indefinitely. In the attached Wireshark trace, you can >> see a cycle of query-willing-request-request...-query-willing-request-request >> after running this command in Cygwin: >> >> No. Time Source Destination Protocol Info >> 3219 253.037685 10.3.20.159 10.3.147.100 XDMCP Query >> >> No. Time Source Destination Protocol Info >> 3220 253.043332 10.3.147.100 10.3.20.159 XDMCP >> Willing >> >> No. Time Source Destination Protocol Info >> 3331 254.061501 10.3.20.159 10.3.147.100 XDMCP >> Request >> >> No. Time Source Destination Protocol Info >> 3361 257.044353 10.3.20.159 10.3.147.100 XDMCP >> Request >> >> [...] >> >> I've also attached a Wireshark trace capturing when using XLaunch to >> start an XDMCP session using Xming. In this trace, you can see the >> expected query-willing-request-accept sequence: >> >> No. Time Source Destination Protocol Info >> 129 14.553230 10.3.20.159 10.3.147.100 XDMCP Query >> >> No. Time Source Destination Protocol Info >> 130 14.554923 10.3.147.100 10.3.20.159 XDMCP >> Willing >> >> No. Time Source Destination Protocol Info >> 135 15.226412 10.3.20.159 10.3.147.100 XDMCP >> Request >> >> No. Time Source Destination Protocol Info >> 136 15.231235 10.3.147.100 10.3.20.159 XDMCP >> Accept I wonder if you could send me privately the Wireshark .pcap files for these traces, I'd like to examine them further. A significant difference is in the Connections data sent in the REQUEST packet (which is a list of network addresses the requestor knows for itself) Xming 6.9: X Display Manager Control Protocol Version: 1 Opcode: Request (0x0007) Message length: 81 Display number: 0 Connections (1) Authentication name: Authentication data (0 bytes) Authorization names (3) Manufacturer display ID: vs. XWin X Display Manager Control Protocol Version: 1 Opcode: Request (0x0007) Message length: 220 Display number: 0 Connections (9) Authentication name: Authentication data (0 bytes) Authorization names (2) Manufacturer display ID: I could understand 8 (the total number of IPv4 and IPv6 interfaces your host has), if you weren't using -from, but 9 is a bit confusing. I would expect Xming 6.9 to report fewer interfaces, since it was built without IPv6 support, but I'm not sure why it's only reporting 1, if you aren't using -from. It seems likely that IPv6 support in XWin is the difference which prevents things from working correctly. -- 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/
