lina 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 usi
On Fri, Feb 14, 2014 at 10:26:07AM +0800, lina wrote:
>
> > 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 ping and used
> 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 ping and used IP, it was the same issue
>
>
>> I was advised by our admin that
>
> Which versions? I'm using rdesktop 1.7.1-1 to reach Server2008 and Win7
> servers with no problem. I'm using tsclient, which is no longer
> developed or in Debian, but the front end shouldn't affect things.
> Remmina doesn't seem to depend on rdesktop and may be worth a try to
> eliminate the
On Thursday 13,February,2014 11:03 PM, lina wrote:
> ERROR: getaddrinfo: No address associated with hostname
>
> 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. "
Right now I tested
On Thursday 13,February,2014 11:14 PM, Alberto Luaces wrote:
> lina writes:
>
>> 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. "
>
> Try with xfreerdp.
>
You mean the freerdp p
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 th
I seem to have an issue as well and my cdn error
Scottrocc
roccVegas ent.Inc
> On Feb 13, 2014, at 12:21 PM, "Karl E. Jorgensen"
> wrote:
>
> 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 a
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 a
On 02/13/2014 04:55 PM, Reco wrote:
> 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
> That means that you've tried to connect to a non-resolvable hostn
Hi,
On Thu, February 13, 2014 16:03, lina wrote:
> Hi,
>
> When I tried to use rdesktop, it showed me
>
> ERROR: getaddrinfo: No address associated with hostname
Looks like a DNS issue to me, getaddrinfo is the part where the hostname
is resolved to an IP. Try to ping the remote host and see if i
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
That means that you've tried to connect to a non-resolvable hostname
(i.e. no hostname → IP association). No more, no less.
On Thu, 13 Feb 2014 23:03:07 +0800
lina wrote:
> Hi,
>
> When I tried to use rdesktop, it showed me
>
> ERROR: getaddrinfo: No address associated with hostname
>
> 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
lina writes:
> 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. "
Try with xfreerdp.
--
Alberto
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject o
Curtis Vaughan wrote:
> Basically, when I try to connect to a Terminal Server (whether I use
> 1.2.x or 1.3.0) I get the error that it cannot connect.
Saw your email on rdesktop-users, but I didn't know of any such switch. But a
few simple thoughts:
Windows 2000 or 2003? If the latter, are the
Rens wrote:
Curtis Vaughan wrote:
I've put this question on the rdesktop list, but there seems to be
only a post every couple of days (in other words, no reply).
Anyhow, I have a problem using rdesktop. I know I have read a
solution for this problem before, but now I can't find it.
Basically,
Curtis Vaughan wrote:
I've put this question on the rdesktop list, but there seems to be only
a post every couple of days (in other words, no reply).
Anyhow, I have a problem using rdesktop. I know I have read a solution
for this problem before, but now I can't find it.
Basically, when I try t
On Sun, 2004-01-04 at 16:50, Curtis Vaughan wrote:
> Basically, when I try to connect to a Terminal Server (whether I use
> 1.2.x or 1.3.0) I get the error that it cannot connect. As I recall it
> had something to do with forcing the Terminal Server to think the
> client had a built in license.
you need to at least provide the IP address of your server; i.e.:
./rdesktop 10.0.0.1
However, whereas i prefer the full desktop, I include the option -i; i.e.:
./rdesktop -f 10.0.0.1
Due to a licensing issue that has arisen in my environment, however, I now
have to include the -n option; i.e.:
19 matches
Mail list logo
