Re: rdesktop

[Chris Davies <chris@roaima.co.uk>]

lina <lina.lastname@gmail.com> wrote:
> On Thursday 13,February,2014 11:55 PM, Reco wrote:
>>> ERROR: getaddrinfo: No address associated with hostname
>> That means that you've tried to connect to a non-resolvable hostname
>> (i.e. no hostname → IP association). No more, no less.
>> Quick-and-dirty solution for that is using IP address of the host
>> instead.

> I tried IP, it is the same issue.


A little investigation with Windows 2012 servers, which default to
mandating NLA. (Server names changed consistently to protect our
infrastructure details.)


1. Rdesktop to a wrongly named host

    rdesktop -u chris -p "$PASS" -d example NOSUCHSERVER.example.net
    Autoselected keyboard map en-gb
    ERROR: getaddrinfo: Name or service not known

You can see that rdesktop reports that it doesn't know how to resolve
the name to an IP address. Slightly puzzlingly, the error I get is
different the o OP's error. The "No address associated with hostname"
is from EAI_NODATA, but without digging further I can't see how that
can get triggered. (I wondered about a DNS entry that didn't have an A
record, but I don't have the time to set one up and experiment. Is this
an IPv4 vs IPv6 issue, perhaps?)


2. Rdesktop to a correctly named host that does not offer remote desktop
service at all

    rdesktop -u chris -p "$PASS" -d example PRIVATESERVER.example.net
    Autoselected keyboard map en-gb
    ERROR: PRIVATESERVER.example.net: unable to connect

Rdesktop has successfully resolved the name, attempted to connect,
but been rejected at the TCP/IP level.


3. Rdesktop to a correctly named host that requires NLA

    rdesktop -u chris -p "$PASS" -d example SERVER.example.net
    Autoselected keyboard map en-gb
    ERROR: recv: Connection reset by peer

Rdesktop has successfully resolved the name, attempted to connect,
but been rejected at an application level.


4. FreeRDP to a correctly named host that requires NLA

    xfreerdp -u chris -p "$PASS" -d example SERVER.example.net
    connected to SERVER.example.net:3389
    Certificate details:
	    Subject: CN = SERVER.example.net
	    Issuer: CN = SERVER.example.net
	    Thumbprint: 39:0b:4b:09:fa:a3:ae:95:91:fe:84:...
    The above X.509 certificate could not be verified [...]
    Do you trust the above certificate? (Y/N) 

If I accept the certificate then the connection is created and I have
a remote desktop session.


Chris