This is the mail archive of the cygwin-xfree mailing list for the Cygwin XFree86 project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Can't use XDMCP, "winProcEstablishConnection - ProcEstablishConnection failed, bailing" shows in log


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

Here is the output of ipconfig:

C:\Users\alpokluda>ipconfig

Windows IP Configuration


Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::71ea:6924:9397:cfc5%14
   IPv4 Address. . . . . . . . . . . : 10.3.20.159
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 10.3.20.1

Ethernet adapter VMware Network Adapter VMnet1:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::39b9:7291:332c:73ee%16
   IPv4 Address. . . . . . . . . . . : 192.168.245.1
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

Ethernet adapter VMware Network Adapter VMnet8:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::91b6:e77b:7aef:6d88%18
   IPv4 Address. . . . . . . . . . . : 192.168.127.1
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

Ethernet adapter VirtualBox Host-Only Network:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::7cf6:24ee:7c05:7c06%22
   IPv4 Address. . . . . . . . . . . : 192.168.68.1
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

Tunnel adapter isatap.{9D67124F-C8D9-45C5-9AC5-FCF5D2D8625F}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Tunnel adapter isatap.{D64E1692-0777-4BA9-AD59-6BC4B536D5AB}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Tunnel adapter isatap.{95AFDF32-DF73-4F97-A9E6-122D78033AED}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Tunnel adapter isatap.{31D1B58C-F013-4228-B2B6-C75660B9C6AA}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

and 'route print':

C:\Users\alpokluda>route print
===========================================================================
Interface List
 14...1c c1 de 5d bb 1b ......Intel(R) 82578DM Gigabit Network Connection
 16...00 50 56 c0 00 01 ......VMware Virtual Ethernet Adapter for VMnet1
 18...00 50 56 c0 00 08 ......VMware Virtual Ethernet Adapter for VMnet8
 22...08 00 27 00 58 7b ......VirtualBox Host-Only Ethernet Adapter
  1...........................Software Loopback Interface 1
 24...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
 17...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
 19...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
 21...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #4
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0        10.3.20.1      10.3.20.159    266
        10.3.20.0    255.255.255.0         On-link       10.3.20.159    266
      10.3.20.159  255.255.255.255         On-link       10.3.20.159    266
      10.3.20.255  255.255.255.255         On-link       10.3.20.159    266
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
     192.168.68.0    255.255.255.0         On-link      192.168.68.1    276
     192.168.68.1  255.255.255.255         On-link      192.168.68.1    276
   192.168.68.255  255.255.255.255         On-link      192.168.68.1    276
    192.168.127.0    255.255.255.0         On-link     192.168.127.1    276
    192.168.127.1  255.255.255.255         On-link     192.168.127.1    276
  192.168.127.255  255.255.255.255         On-link     192.168.127.1    276
    192.168.245.0    255.255.255.0         On-link     192.168.245.1    276
    192.168.245.1  255.255.255.255         On-link     192.168.245.1    276
  192.168.245.255  255.255.255.255         On-link     192.168.245.1    276
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link       10.3.20.159    266
        224.0.0.0        240.0.0.0         On-link      192.168.68.1    276
        224.0.0.0        240.0.0.0         On-link     192.168.245.1    276
        224.0.0.0        240.0.0.0         On-link     192.168.127.1    276
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link       10.3.20.159    266
  255.255.255.255  255.255.255.255         On-link      192.168.68.1    276
  255.255.255.255  255.255.255.255         On-link     192.168.245.1    276
  255.255.255.255  255.255.255.255         On-link     192.168.127.1    276
===========================================================================
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
          0.0.0.0          0.0.0.0        10.3.20.1  Default
===========================================================================

IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
  1    306 ::1/128                  On-link
 14    266 fe80::/64                On-link
 22    276 fe80::/64                On-link
 16    276 fe80::/64                On-link
 18    276 fe80::/64                On-link
 16    276 fe80::39b9:7291:332c:73ee/128
                                    On-link
 14    266 fe80::71ea:6924:9397:cfc5/128
                                    On-link
 22    276 fe80::7cf6:24ee:7c05:7c06/128
                                    On-link
 18    276 fe80::91b6:e77b:7aef:6d88/128
                                    On-link
  1    306 ff00::/8                 On-link
 14    266 ff00::/8                 On-link
 22    276 ff00::/8                 On-link
 16    276 ff00::/8                 On-link
 18    276 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None

Please let me know if you need more information.

On Wed, Feb 2, 2011 at 11:00 AM, Jon TURNEY <jon.turney@dronecode.org.uk> wrote:
> 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 <jon.turney@dronecode.org.uk> 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 <corresponding local IP 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
>

Attachment: Xming XDMCP Connection Wireshark Trace.txt
Description: Text document

Attachment: XWin XDMCP Connection Wireshark Trace.txt
Description: Text document

--
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/

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]