Re: Can't use XDMCP, "winProcEstablishConnection - ProcEstablishConnection failed, bailing" shows in log
Thanks for all of your work Jon :) On Sat, Mar 5, 2011 at 1:15 PM, Jon TURNEY wrote: > On 15/02/2011 13:16, Alexander Pokluda wrote: >> I don't have any idea why the XDMCP request packets from XWin would be >> dropped by the network either. >> >> What I thought was interesting is that the value of Connection 4 in >> the XDMCP REQUEST packet from XWin in the Wireshark trace is >> fe80::5efe:a03:149f. I'm still familiarizing myself with IPv6, but the >> handy tool at ip-lookup.net shows this for that address: >> >> This IPv6 address contains an IPv4 address: > > Oh yes, this appears to be an ISATAP address. > >> It seems there are some interesting things going on here, but, the >> modified XWin you link to at the bottom of your email works >> perfectly!! > > Thanks for testing. > > I'll include this change in the next release, since it seems to be doing the > correct thing. > > -- > 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/
Re: Can't use XDMCP, "winProcEstablishConnection - ProcEstablishConnection failed, bailing" shows in log
On 15/02/2011 13:16, Alexander Pokluda wrote: > I don't have any idea why the XDMCP request packets from XWin would be > dropped by the network either. > > What I thought was interesting is that the value of Connection 4 in > the XDMCP REQUEST packet from XWin in the Wireshark trace is > fe80::5efe:a03:149f. I'm still familiarizing myself with IPv6, but the > handy tool at ip-lookup.net shows this for that address: > > This IPv6 address contains an IPv4 address: Oh yes, this appears to be an ISATAP address. > It seems there are some interesting things going on here, but, the > modified XWin you link to at the bottom of your email works > perfectly!! Thanks for testing. I'll include this change in the next release, since it seems to be doing the correct thing. -- 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/
Re: Can't use XDMCP, "winProcEstablishConnection - ProcEstablishConnection failed, bailing" shows in log
Hi Jon, I don't have any idea why the XDMCP request packets from XWin would be dropped by the network either. What I thought was interesting is that the value of Connection 4 in the XDMCP REQUEST packet from XWin in the Wireshark trace is fe80::5efe:a03:149f. I'm still familiarizing myself with IPv6, but the handy tool at ip-lookup.net shows this for that address: This IPv6 address contains an IPv4 address: IPv6 compressed : FE80::5EFE:A03:149F IPv6 uncompressed : FE80:0:0:0:0:5EFE:A03:149F IPv6 fully uncompressed : FE80:::::5EFE:0A03:149F IP v4: decimal : 10.3.20.159 binary : 10100011000101001001 octal : 012.03.024.0237 hexadecimal : 0x0A.0x03.0x14.0x9F long : 167974047 IP v6 : 6 to 4 address : 2002:A03:149F:0:0:0:0:0 : 2002:A03:149F:: IPv4-mapped address : 0:0:0:0:0::10.3.20.159 : :::10.3.20.159 : :::0A03:149F IPv4-compatibility address : 0:0:0:0:0:0:10.3.20.159 : ::10.3.20.159 : ::0A03:149F It seems there are some interesting things going on here, but, the modified XWin you link to at the bottom of your email works perfectly!! Thanks for all of your help :-) On Mon, Feb 14, 2011 at 9:46 AM, Jon TURNEY wrote: > > > On Wed, Feb 9, 2011 at 6:37 PM, Jon TURNEY > > wrote: > >> I wonder if you could send me privately the Wireshark .pcap files for these > >> traces, I'd like to examine them further. > > On 11/02/2011 18:45, Alexander Pokluda wrote: > > I've attached a zip archive containing a number of files. The pcap > > files were created by running Wireshark on both ends while attempting > > to establish an XDMCP session between the hosts. Here is a description > > of the files: > > Thanks very much for these. > > Unfortunately, these seem to show that the XDMCP request packet leaves the > machine running XWin, but doesn't arrive at the VM. > > I've no idea why that might be, but that suggests to me they are being dropped > in your network, or between the host running the VM and the guest VM? > > > After I took the above screenshot, I realized that I had a VirtualBox > > adapter with IPv6 enabled, so I disabled the VirtualBox adapter and > > ran the XWin command again, capturing packets on both ends. These > > files contain the captured packets. One interesting thing to note is > > that the request packet sent from XWin contains my IPv4 address > > converted to an IPv6 address even when IPv6 is disabled on my physical > > adapter. > > These look like link-local IPv6 addresses (prefix fe80::) to me, rather than > IPv6 mapped IPv4 addresses (prefix :::)? > > However, this does look like a bug (or at least the code not doing what it > says it does): when the -from option is used, the XDMCP request contains the > specified address *and* any other addresses we have of different address > families to the specified address (e.g., if we specify an IPv4 address, we get > only that IPv4 address, but all the IPv6 addresses as well) > > I've built a snapshot which contains a change which modifies the behaviour of > -from so only the specified address is included in the XDMCP request, and > uploaded it at [1]. > > With this change, the XDMCP request sent by XWin and XMing should be nearly > identical. Perhaps you could try that out and see if that makes a difference. > > ftp://cygwin.com/pub/cygwinx/XWin.20110214-git-d593beaadac1371e.exe.bz2 -- 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: Can't use XDMCP, "winProcEstablishConnection - ProcEstablishConnection failed, bailing" shows in log
> On Wed, Feb 9, 2011 at 6:37 PM, Jon TURNEY > wrote: >> I wonder if you could send me privately the Wireshark .pcap files for these >> traces, I'd like to examine them further. On 11/02/2011 18:45, Alexander Pokluda wrote: > I've attached a zip archive containing a number of files. The pcap > files were created by running Wireshark on both ends while attempting > to establish an XDMCP session between the hosts. Here is a description > of the files: Thanks very much for these. Unfortunately, these seem to show that the XDMCP request packet leaves the machine running XWin, but doesn't arrive at the VM. I've no idea why that might be, but that suggests to me they are being dropped in your network, or between the host running the VM and the guest VM? > After I took the above screenshot, I realized that I had a VirtualBox > adapter with IPv6 enabled, so I disabled the VirtualBox adapter and > ran the XWin command again, capturing packets on both ends. These > files contain the captured packets. One interesting thing to note is > that the request packet sent from XWin contains my IPv4 address > converted to an IPv6 address even when IPv6 is disabled on my physical > adapter. These look like link-local IPv6 addresses (prefix fe80::) to me, rather than IPv6 mapped IPv4 addresses (prefix :::)? However, this does look like a bug (or at least the code not doing what it says it does): when the -from option is used, the XDMCP request contains the specified address *and* any other addresses we have of different address families to the specified address (e.g., if we specify an IPv4 address, we get only that IPv4 address, but all the IPv6 addresses as well) I've built a snapshot which contains a change which modifies the behaviour of -from so only the specified address is included in the XDMCP request, and uploaded it at [1]. With this change, the XDMCP request sent by XWin and XMing should be nearly identical. Perhaps you could try that out and see if that makes a difference. ftp://cygwin.com/pub/cygwinx/XWin.20110214-git-d593beaadac1371e.exe.bz2 -- 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: Can't use XDMCP, "winProcEstablishConnection - ProcEstablishConnection failed, bailing" shows in log
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 ci001138531.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 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. TimeSourceDestination Protocol Info >> 3219 253.037685 10.3.20.159 10.3.147.100 XDMCPQuery >> >> No. TimeSourceDestination Protocol Info >> 3220 253.043332 10.3.147.100 10.3.20.159 XDMCP >> Willing >> >> No. TimeSourceDestination Protocol Info >> 3331 254.061501 10.3.20.159 10.3.147.100 XDMCP >> Request >> >> No. TimeSourceDestination 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. TimeSourceDestination Protocol Info >>129 14.553230 10.3.20.159 10.3.147.100 XDMCPQuery >> >> No. TimeSourceDestination Protocol Info >>130 14.554923 10.3.147.100 10.3.20.159 XDMCP >> Willing >> >> No. TimeSourceDestination Protocol Info >>135 15.226412 10.3.20.159 10.3.147.100 XDMCP >> Request >> >> No. TimeSourceDestination 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 w
Re: Can't use XDMCP, "winProcEstablishConnection - ProcEstablishConnection failed, bailing" shows in log
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 ci001138531.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 Feb 8 11:24:16 dev01 gdm[4097]: gdm_xdmcp_host_allow: client->hostname is ci001138531.xxx.net Feb 8 11:24:16 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 Feb 8 11:24:16 dev01 gdm[4097]: gdm_xdmcp_host_allow: client->hostname is ci001138531.xxx.net Feb 8 11:24:16 dev01 gdm[4097]: gdm_xdmcp_send_willing: Sending WILLING to 10.3.20.159 Feb 8 11:27:45 dev01 gdm[4097]: gdm_xdmcp_decode: Received opcode QUERY from client 10.3.20.159 Feb 8 11:27:45 dev01 gdm[4097]: gdm_xdmcp_handle_query: Opcode 2 from 10.3.20.159 Feb 8 11:27:45 dev01 gdm[4097]: gdm_xdmcp_host_allow: client->hostname is ci001138531.xxx.net Feb 8 11:27:45 dev01 gdm[4097]: gdm_xdmcp_send_willing: Sending WILLING to 10.3.20.159 [...] 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. By contrast, this is what appears in the log when making a successful connection with XLaunch/Xming: Feb 8 11:28:39 dev01 gdm[4097]: gdm_xdmcp_decode: Received opcode QUERY from client 10.3.20.159 Feb 8 11:28:39 dev01 gdm[4097]: gdm_xdmcp_handle_query: Opcode 2 from 10.3.20.159 Feb 8 11:28:39 dev01 gdm[4097]: gdm_xdmcp_host_allow: client->hostname is ci001138531.xxx.net Feb 8 11:28:39 dev01 gdm[4097]: gdm_xdmcp_send_willing: Sending WILLING to 10.3.20.159 Feb 8 11:28:39 dev01 gdm[4097]: gdm_xdmcp_decode: Received opcode REQUEST from client 10.3.20.159 Feb 8 11:28:39 dev01 gdm[4097]: gdm_xdmcp_handle_request: Got REQUEST from 10.3.20.159 Feb 8 11:28:39 dev01 gdm[4097]: gdm_xdmcp_host_allow: client->hostname is ci001138531.xxx.net Feb 8 11:28:39 dev01 gdm[4097]: gdm_xdmcp_displays_check: Disposing session id 971069010 Feb 8 11:28:39 dev01 gdm[4097]: gdm_display_dispose: Disposing dev01.xxx.net:2 Feb 8 11:28:39 dev01 gdm[4097]: gdm_xdmcp_handle_request: xdmcp_pending=0, MaxPending=4, xdmcp_sessions=0, MaxSessions=16, ManufacturerID= Feb 8 11:28:39 dev01 gdm[4097]: gdm_xdmcp_display_dispose_check (ci001138531.xxx.net:0) Feb 8 11:28:39 dev01 gdm[4097]: gdm_auth_secure_display: Setting up access for ci001138531.xxx.net:0 Feb 8 11:28:39 dev01 gdm[4097]: gdm_auth_secure_display: Setting up access Feb 8 11:28:39 dev01 gdm[4097]: gdm_auth_secure_display: Setting up access for ci001138531.xxx.net:0 - 1 entries Feb 8 11:28:39 dev01 gdm[4097]: gdm_xdmcp_display_alloc: display=ci001138531.xxx.net:0, session id=971069011, xdmcp_pending=1 Feb 8 11:28:39 dev01 gdm[4097]: gdm_xdmcp_send_accept: Sending ACCEPT to 10.3.20.159 with SessionID=971069011 Feb 8 11:28:39 dev01 gdm[4097]: gdm_xdmcp_decode: Received opcode MANAGE from client 10.3.20.159 Feb 8 11:28:39 dev01 gdm[4097]: gdm_xdmcp_handle_manage: Got MANAGE from 10.3.20.159 Feb 8 11:28:39 dev01 gdm[4097]: gdm_xdmcp_host_allow: client->hostname is ci001138531.xxx.net Feb 8 11:28:39 dev01 gdm[4097]: gdm_xdmcp_handle_manage: Got Display=0, SessionID=971069011 Class=MIT-unspecified from 10.3.20.159 Feb 8 11:28:39 dev01 gdm[4097]: gdm_xdmcp_handle_manage: Looked up ci001138531.xxx.net:0 Feb 8 11:28:39 dev01 gdm[4097]: gdm_choose_indirect_lookup: Host 10.3.20.159 not found Feb 8 11:28:39 dev01 gdm[4097]: gdm_forward_query_lookup: Host 10.3.20.159 not found Feb 8 11:28:39 dev01 gdm[4097]: gdm_display_manage: Managing ci001138531.xxx.net:0 Feb 8 11:28:39 dev01 gdm[4097]: loop check: last_start 0, last_loop 0, now: 1297182519, retry_count: 0 Feb 8 11:28:39 dev01 gdm[4097]: Resetting counts for loop of death detection Feb 8 11:28:39 dev01 gdm[4097]: gdm_display_manage: Forked slave: 12208 Feb 8 11:28:39 dev01 gdm[12208]: gdm_slave_start: Starting slave process for ci001138531.xxx.net:0 Feb 8 11:28:39 dev01 gdm[12208]: gdm_slave_start: Loop Thingie Feb 8 11:28:40 dev01 gdm[12208]: gdm_slave_run: Opening display ci001138531.xxx.net:0 Feb 8 11:28:40 dev01 gdm[12208]: gdm_slave_greeter: Running greeter on ci001138531.xxx.net:0 Feb 8 11:28:40 dev01 gdm[12208]: gdm_slave_greeter: Greeter on pid 12218 [...] On Tue, Feb 8, 2011 a
Re: Can't use XDMCP, "winProcEstablishConnection - ProcEstablishConnection failed, bailing" shows in log
On 28/01/2011 20:23, Alexander Pokluda wrote: > The Windows PC that I'm using is on a different subnet from the VMs > that I need to connect to (10.3.20.159/24), so does that mean it's not > possible to use Cygwin/X in this case? (Changing either subnet is not > an option). Ah, I had assumed that you were running the VMs locally with some form of virtual networking. It certainly should be possible to configure XWin to work in your case. If you have multiple network interfaces on your PC, then it's probably just a question of using the -from option to ensure traffic is sent with the correct source address. If that doesn't fix it, perhaps you could provide a wireshark trace of the connection attempt and some more details of the networking configuration (e.g. output of 'ipconfig' and 'route print') > On Fri, Jan 28, 2011 at 3:16 PM, Jon TURNEY > wrote: >> On 28/01/2011 19:19, Alexander Pokluda wrote: >>> I've been trying for a while to get Cygwin/X working with XDMCP for >>> quite a while without any success; however, I am able to conenct >>> without any any problem using Xming 6.9. I'm using a Windows 7 PC to >>> connect to a different Linux VMs running CentOS 5.5. After starting >>> XWin from the command line (either directly or using startxdmcp.bat), >>> a window opens up that contains nothing but black. At first when I >>> move the cursor over the winodow, it just disappears but after a >>> while, the cursor will appear as an X and the following shows up in >>> the log file: >>> >>> [266377.900] winProcEstablishConnection - Hello >>> [266377.900] winProcEstablishConnection - ProcEstablishConnection >>> failed, bailing. >>> [266385.653] winAboutDlgProc - WM_COMMAND - IDOK or IDCANCEL >>> [266489.784] XDM: too many retransmissions, declaring session dead >>> >>> Any help would be greatly appreciated. I've included part of the log >>> from one attempt to connect to one of the CentOS 5.5 VMs that I can >>> connect to with Xming using XDMCP. >> >>> [266616.722] XDM: too many retransmissions, declaring session dead >> >> Possibly you need to use -query 10.3.147.100 -from > for >> the subnet containing that IP address> >> >> Xming has a patch applied which adds some more intelligence to the way the >> local IP address is chosen, but unfortunately that is written to use the >> winsock API directly, so can't be used directly in XWin. -- 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/
Re: Can't use XDMCP, "winProcEstablishConnection - ProcEstablishConnection failed, bailing" shows in log
The Windows PC that I'm using is on a different subnet from the VMs that I need to connect to (10.3.20.159/24), so does that mean it's not possible to use Cygwin/X in this case? (Changing either subnet is not an option). On Fri, Jan 28, 2011 at 3:16 PM, Jon TURNEY wrote: > On 28/01/2011 19:19, Alexander Pokluda wrote: >> I've been trying for a while to get Cygwin/X working with XDMCP for >> quite a while without any success; however, I am able to conenct >> without any any problem using Xming 6.9. I'm using a Windows 7 PC to >> connect to a different Linux VMs running CentOS 5.5. After starting >> XWin from the command line (either directly or using startxdmcp.bat), >> a window opens up that contains nothing but black. At first when I >> move the cursor over the winodow, it just disappears but after a >> while, the cursor will appear as an X and the following shows up in >> the log file: >> >> [266377.900] winProcEstablishConnection - Hello >> [266377.900] winProcEstablishConnection - ProcEstablishConnection >> failed, bailing. >> [266385.653] winAboutDlgProc - WM_COMMAND - IDOK or IDCANCEL >> [266489.784] XDM: too many retransmissions, declaring session dead >> >> Any help would be greatly appreciated. I've included part of the log >> from one attempt to connect to one of the CentOS 5.5 VMs that I can >> connect to with Xming using XDMCP. > >> [266616.722] XDM: too many retransmissions, declaring session dead > > Possibly you need to use -query 10.3.147.100 -from the subnet containing that IP address> > > Xming has a patch applied which adds some more intelligence to the way the > local IP address is chosen, but unfortunately that is written to use the > winsock API directly, so can't be used directly in XWin. > > -- > 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/
Re: Can't use XDMCP, "winProcEstablishConnection - ProcEstablishConnection failed, bailing" shows in log
On 28/01/2011 19:19, Alexander Pokluda wrote: > I've been trying for a while to get Cygwin/X working with XDMCP for > quite a while without any success; however, I am able to conenct > without any any problem using Xming 6.9. I'm using a Windows 7 PC to > connect to a different Linux VMs running CentOS 5.5. After starting > XWin from the command line (either directly or using startxdmcp.bat), > a window opens up that contains nothing but black. At first when I > move the cursor over the winodow, it just disappears but after a > while, the cursor will appear as an X and the following shows up in > the log file: > > [266377.900] winProcEstablishConnection - Hello > [266377.900] winProcEstablishConnection - ProcEstablishConnection > failed, bailing. > [266385.653] winAboutDlgProc - WM_COMMAND - IDOK or IDCANCEL > [266489.784] XDM: too many retransmissions, declaring session dead > > Any help would be greatly appreciated. I've included part of the log > from one attempt to connect to one of the CentOS 5.5 VMs that I can > connect to with Xming using XDMCP. > [266616.722] XDM: too many retransmissions, declaring session dead Possibly you need to use -query 10.3.147.100 -from Xming has a patch applied which adds some more intelligence to the way the local IP address is chosen, but unfortunately that is written to use the winsock API directly, so can't be used directly in XWin. -- 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/
Can't use XDMCP, "winProcEstablishConnection - ProcEstablishConnection failed, bailing" shows in log
Hi, I've been trying for a while to get Cygwin/X working with XDMCP for quite a while without any success; however, I am able to conenct without any any problem using Xming 6.9. I'm using a Windows 7 PC to connect to a different Linux VMs running CentOS 5.5. After starting XWin from the command line (either directly or using startxdmcp.bat), a window opens up that contains nothing but black. At first when I move the cursor over the winodow, it just disappears but after a while, the cursor will appear as an X and the following shows up in the log file: [266377.900] winProcEstablishConnection - Hello [266377.900] winProcEstablishConnection - ProcEstablishConnection failed, bailing. [266385.653] winAboutDlgProc - WM_COMMAND - IDOK or IDCANCEL [266489.784] XDM: too many retransmissions, declaring session dead Any help would be greatly appreciated. I've included part of the log from one attempt to connect to one of the CentOS 5.5 VMs that I can connect to with Xming using XDMCP. Sincerely, Alexander Pokluda -- -- Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.9.3.0 (10903000) Package version 1.9.3-2 built 2011-01-05 XWin was started with the following command line: xwin -query 10.3.147.100 ddxProcessArgument - Initializing default screens winInitializeScreenDefaults - primary monitor w 1680 h 1050 winInitializeDefaultScreens - native DPI x 96 y 96 [266361.832] winInitializeScreens - 1 [266361.832] winInitializeScreen - 0 [266361.832] (II) xorg.conf is not supported [266361.832] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information [266361.832] LoadPreferences: /cygdrive/c/Users/alpokluda/.XWinrc not found [266361.832] LoadPreferences: Loading /etc/X11/system.XWinrc [266361.832] LoadPreferences: Done parsing the configuration file... [266361.832] winGetDisplay: DISPLAY=:0.0 [266361.832] winDetectSupportedEngines - Windows NT/2000/XP [266361.863] winDetectSupportedEngines - DirectDraw installed [266361.863] winDetectSupportedEngines - Allowing PrimaryDD [266361.863] winDetectSupportedEngines - DirectDraw4 installed [266361.894] winDetectSupportedEngines - Returning, supported engines 001f [266361.894] winSetEngine - Using Shadow DirectDraw NonLocking [266361.894] winScreenInit - Using Windows display depth of 32 bits per pixel [266362.019] winFinishScreenInitFB - Masks: 00ff ff00 00ff [266362.019] Screen 0 added at virtual desktop coordinate (1680,0). [266362.019] MIT-SHM extension disabled due to lack of kernel support [266362.035] XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel [266362.081] (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so [266362.081] (II) GLX: Initialized DRISWRAST GL provider for screen 0 [266362.097] [dix] Could not init font path element /usr/share/fonts/TTF/, removing from list! [266362.097] [dix] Could not init font path element /usr/share/fonts/OTF/, removing from list! [266362.097] [dix] Could not init font path element /usr/share/fonts/Type1/, removing from list! [266362.440] winPointerWarpCursor - Discarding first warp: 837 496 [266362.440] (--) 3 mouse buttons found [266362.440] (--) Setting autorepeat to delay=500, rate=31 [266362.440] (--) Windows keyboard layout: "0409" (0409) "US", type 4 [266362.440] (--) Found matching XKB configuration "English (USA)" [266362.440] (--) Model = "pc105" Layout = "us" Variant = "none" Options = "none" [266362.440] Rules = "base" Model = "pc105" Layout = "us" Variant = "none" Options = "none" [266377.900] winProcEstablishConnection - Hello [266377.900] winProcEstablishConnection - ProcEstablishConnection failed, bailing. [266385.653] winAboutDlgProc - WM_COMMAND - IDOK or IDCANCEL [266489.784] XDM: too many retransmissions, declaring session dead [266489.940] 5 XSELINUXs still allocated at reset [266489.940] SCREEN: 0 objects of 72 bytes = 0 total bytes 0 private allocs [266489.940] DEVICE: 4 objects of 16 bytes = 64 total bytes 0 private allocs [266489.940] CLIENT: 0 objects of 140 bytes = 0 total bytes 0 private allocs [266489.940] WINDOW: 0 objects of 64 bytes = 0 total bytes 0 private allocs [266489.940] PIXMAP: 1 objects of 28 bytes = 28 total bytes 0 private allocs [266489.940] GC: 0 objects of 52 bytes = 0 total bytes 0 private allocs [266489.940] CURSOR: 0 objects of 4 bytes = 0 total bytes 0 private allocs [266489.940] CURSOR_BITS: 0 objects of 4 bytes = 0 total bytes 0 private allocs [266489.940] DBE_WINDOW: 0 objects of 12 bytes = 0 total bytes 0 private allocs [266489.940] TOTAL: 5 objects, 92 bytes, 0 allocs [266489.940] 4 DEVICEs still allocated at reset [266489.940] DEVICE: 4 objects of 16 bytes = 64 total bytes 0 private allocs [266489.940] CLIENT: 0 objects of 140 bytes = 0 total bytes 0 private allocs [266489.940] WINDOW: 0 objects of 64 bytes = 0 total bytes 0 private allocs [266489.940] PIXMAP: 1 objects of 28 bytes = 28 total bytes 0
