Hi
On Thu, Feb 13, 2014 at 11:03:07PM +0800, lina wrote:
> Hi,
>
> When I tried to use rdesktop, it showed me
>
> ERROR: getaddrinfo: No address associated with hostname
As others have already mentioned: This is a DNS Name -> IP address
resolution problem. Not rdesktop.
It could be as simple as needing to use the fully qualified domain
name, if your /etc/resolv.conf has a different "search" path that the
equivalent on windows.
>
> I was advised by our admin that "It is something to do with the RDP
> version on Linux. It has some compatibility issues with the more recent
> version of MS-RDP. "
Yeah right. Not. Whoever claimed that: Make a mental note to avoid
letting this person solve problems in the future. It will probably
save you both time and frustration. Or that person didn't understand
your problem in the first place. Both is bad news.
But there is *some* truth to this: I have found that servers with NLA
(Network Level Authentication) enabled, rdesktop doesn't work. But the
symptoms for this are very different: it will exit with some error
code, essentially saying "booh-hooh: The other end closed the
connection on me!!".
> Further, I was told to try use windows to connect to that window machine
> in order to access some software.
Well - I suspect that the person you talked to prefers/advocates
windows? Or (in)corporate policy or somesuch arguments.
> I checked the debian package, seems currently the one I use is the
> latest version, any suggestion about how to resolve it without resorting
> to the Windows.
Depending on your local network and the hostname you're using: It may
actually work from a windows machine. If [1] you were given a windows
server NETBIOS name, it may not be resolvable unless you have
libnss-winbind installed[2]. Such names are usually recognizable by:
- No more than 8 characters
- Usually specified in ALL UPPER CASE
- Sometimes specified with leading '\\'
The litmus test for this is to try to ping the name from a windows
box. (Whether it actually *responds* to pings is irrelevant - what
matters is whether ping can resolve the name to an IP address). If it
works there, but not from linux, then lack of libnss-winbind *may* be
your problem.
[1] ... and this is a BIG if on my part. I'm at the limits of my
knowledge and experience here.
[2] I'm not even 100% sure of the package name. But bear with me.
Hope this helps
--
Karl E. Jorgensen
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20140213202046.GD2934@hawking
