Re: rdesktop
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 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
--
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/ngf1tax2gk@news.roaima.co.uk
Re: rdesktop
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 IP, it was the same issue Meaning, you've invoked 'rdesktop 10.0.0.1' (or any other IP address), and got the same error: ERROR: getaddrinfo: No address associated with hostname This is VERY strange. Can you please try running rdesktop like this (replace 10.0.0.1 with a real IP): strace -o /tmp/rdesktop rdesktop 10.0.0.1 I like to see what's really goin' on there. Please attach /tmp/rdesktop to your e-mail, or put in on a pastebin. > >> Further, I was told to try use window to connect to that window machine > >> in order to access some software. > > > > And, did it work? > > Right now I checked from a Window, yeah, it worked from windows to > connect to that server Ok. And, this Windoze host, does it use the same DNS settings as yours? Reco -- 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/20140214074413.GA27635@x101h
Re: rdesktop
> 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 "It is something to do with the RDP >> version on Linux. It has some compatibility issues with the more recent >> version of MS-RDP. " > > While there may be such incompatibility (rdesktop is an implementation > of a reverse-engineered protocol, after all), such claim is showing one > of two things: > > a) The person in question have no desire to solve your problem. > > b) The person in question is not qualified enough to solve your problem. > > >> Further, I was told to try use window to connect to that window machine >> in order to access some software. > > And, did it work? Right now I checked from a Window, yeah, it worked from windows to connect to that server > > >> 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. > > You use latest version packaged in the Debian. The latest upstream > version, according to [1] is 1.8.1, which is one minor version above > Debian Unstable. > > Still, given that this problem is with the resolving hostname, not RDP > incompatibility - I doubt that upgrading to the latest upstream version > will solve anything (or, for example, replacing rdesktop with freerdp > will). > > [1] http://www.rdesktop.org/ > > Reco > > -- 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/52fd7ebf.3070...@gmail.com
Re: rdesktop
> > 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 rdesktop component. > I can connect to other Windows server with this rdesktop with no problem. -- 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/52fd7e43.4060...@gmail.com
Re: rdesktop
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 window OS, it can connect to that windows server. -- 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/52fd7dea.7050...@gmail.com
Re: rdesktop
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 package. -- 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/52fd7a90.3070...@gmail.com
Re: rdesktop
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. -- 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/52fd7808.9030...@gmail.com
Re: rdesktop
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 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 > -- 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/snt404-eas96a2bd5a2b85d314b0ce63a7...@phx.gbl
Re: rdesktop
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
Re: rdesktop
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 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. > > 1) as Reco wrote, it looks like a wrong, non-resolvable hostname. check your DNS settings. 2) how does the configuration of the windows-host look like? there are 3 possible options to configure for RDP connections: a) do not accept RDP connections b) accept connections from clients running any RDP version c) only accept clients with a RDP version that supports authentication on network-level you might try option b) when using rdesktop to connect to newer version of windows (Vista, 7, 8, Server2kX). cheers, matthias -- PGP KeyID: 0xF7BEDB94 Fingerprint: 15B1 56D8 8F67 FAAF 3FA2 76DA E072 A32C F7BE DB94 signature.asc Description: OpenPGP digital signature
Re: rdesktop
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 it even resolves the IP. you may need to check your machine's settings to make sure it uses a proper DNS server (I guess you should use the internal one in your company here). Most of the time the correct server is provided automatically using DHCP when you obtain an IP address. > [...] Best regards, Steven -- E-mail as text/plain is preferred. A PGP signature is not available from this computer. -- 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/7bd04df4990367ff74376b0e02709c8d.squir...@stevenleeuw.kwik.to
Re: rdesktop
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. Quick-and-dirty solution for that is using IP address of the host instead. > 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. " While there may be such incompatibility (rdesktop is an implementation of a reverse-engineered protocol, after all), such claim is showing one of two things: a) The person in question have no desire to solve your problem. b) The person in question is not qualified enough to solve your problem. > Further, I was told to try use window to connect to that window machine > in order to access some software. And, did it work? > 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. You use latest version packaged in the Debian. The latest upstream version, according to [1] is 1.8.1, which is one minor version above Debian Unstable. Still, given that this problem is with the resolving hostname, not RDP incompatibility - I doubt that upgrading to the latest upstream version will solve anything (or, for example, replacing rdesktop with freerdp will). [1] http://www.rdesktop.org/ Reco -- 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/20140213155522.GA10762@x101h
Re: rdesktop
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 more > recent version of MS-RDP. " > > Further, I was told to try use window to connect to that window > machine in order to access some software. > > 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. > 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 rdesktop component. -- Joe -- 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/20140213153524.09f88...@jretrading.com
Re: rdesktop
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 of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87d2ir59k4@eps142.cdf.udc.es
rdesktop
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 more recent version of MS-RDP. " Further, I was told to try use window to connect to that window machine in order to access some software. 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. Thanks ahead, -- 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/52fcdeab.3000...@gmail.com
rdesktop segmentation fault
We have found that the Lenny rdestkop-1.6.0-2 package seg faults reliably when using seamlessrdp. In fact, it seg faults on every other access. Apparently this is a known problem. We did apply the known patch. It works and we have packaged internally as rdesktop-1.6.0-2.1. Should we do anything with this package in case others are also using seamlessrdp? What is the Debian protocol? Thanks - John -- 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/1270907956.25675.2.ca...@family.pacifera.com
Re: local disk access problem of rdesktop
On Sat, 12 Jul 2008 08:58:54 +0800, Can-Hua Chen wrote: >> > I am using rdesktop >> > ( rdesktop -f HOST_IP -u USERNAME -p PASSWD -r sound:local >> > -r disk:L=/home/LOCAL_USER) >> > and trying to access local file system on remote XP desktop. >> > However I am reject to access on remote XP, saying that >> > I have no right, although I do be able to see the "L" volume >> >> Is the "L" volume that you see under \\tsclient? >> > Yes. Actually I am able to list the directory of "L" as soon > as I get connected to remote XP, however when I want to go > further deeper, I am denied. Still stranger, when I tried to > list the "L" directory the second time, I was denied from then on. Sorry I can't help here. Maybe raise a bug report or dig further. But I really doubt that the light-weighted rdesktop can incorporate the full samba protocol. I suspect it is related with the Windows domain authentication. Why don't you save yourself from the trouble and take the easy route -- install samba and share out your folder. That's fully documented, and you'll get better luck if stuck. -- Tong (remove underscore(s) to reply) http://xpt.sourceforge.net/techdocs/ http://xpt.sourceforge.net/tools/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: local disk access problem of rdesktop
On Wed, Jul 09, 2008 at 06:40:43PM +, T o n g wrote: > On Wed, 09 Jul 2008 21:09:56 +0800, Can-Hua Chen wrote: > > > I am using rdesktop > > ( rdesktop -f HOST_IP -u USERNAME -p PASSWD -r sound:local > > -r disk:L=/home/LOCAL_USER) > > and trying to access local file system on remote XP desktop. > > However I am reject to access on remote XP, saying that > > I have no right, although I do be able to see the "L" volume > > Is the "L" volume that you see under \\tsclient? > Yes. Actually I am able to list the directory of "L" as soon as I get connected to remote XP, however when I want to go further deeper, I am denied. Still stranger, when I tried to list the "L" directory the second time, I was denied from then on. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: local disk access problem of rdesktop
On Wed, 09 Jul 2008 21:09:56 +0800, Can-Hua Chen wrote: > I am using rdesktop > ( rdesktop -f HOST_IP -u USERNAME -p PASSWD -r sound:local > -r disk:L=/home/LOCAL_USER) > and trying to access local file system on remote XP desktop. > However I am reject to access on remote XP, saying that > I have no right, although I do be able to see the "L" volume Is the "L" volume that you see under \\tsclient? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
local disk access problem of rdesktop
I am using rdesktop ( rdesktop -f HOST_IP -u USERNAME -p PASSWD -r sound:local -r disk:L=/home/LOCAL_USER) and trying to access local file system on remote XP desktop. However I am reject to access on remote XP, saying that I have no right, although I do be able to see the "L" volume -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Rdesktop users?
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 users in the "Remote Desktop Users" group? Can you logon as "administrator" - i.e. is the problem restricted to standard users? If Windows 2000 I seem to recall that there was a licensing problem in early versions...? Is your server licensed by user or device - I seem to recall that there is a problem connecting to Server 2003 from rdesktop with device licensing. 1.3 sounds old - might be worth trying a newer version of rdesktop? Errors in the server event log (a quick Google found http://ts.veranoest.net/ts_logon.htm)? Sorry I cannot be more helpful. Chris. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Rdesktop users?
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, 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. There was a particular option one would add to the rdesktop command to do this. But now I can find no such documentation. Can anyone help? Curtis Vaughan Hi Curtis, You might mean logging on as a console user. That's done by appending the option -0 to the rdesktop command. You're basicly telling the remote desktop client that you are logging on to the Terminal Server for administrative purposes. This comes in handy when some other user has logged on taking up the last license and you need to do administrative maintenance. Hi Curtis, if you are using gnome, i recommend you GNOME-RDP, it´s very stable and a useful tool. Perhaps this tool solve your problems. cheers! Ramiro -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Rdesktop users?
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 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. There was a particular option one would add to the rdesktop command to do this. But now I can find no such documentation. Can anyone help? Curtis Vaughan Hi Curtis, You might mean logging on as a console user. That's done by appending the option -0 to the rdesktop command. You're basicly telling the remote desktop client that you are logging on to the Terminal Server for administrative purposes. This comes in handy when some other user has logged on taking up the last license and you need to do administrative maintenance. -- Rens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
rdesktop - local HDD share problem
I use rdeskop (running on lenny) to connect to my school. I tried to share the debian drive with the "-r disk:bkup=/mnt/backup/ " option. When I connect to my school, I am able to use the local debian HDD for 40 seconds or so. Then an error throws up saying "tsclient://. you do not have permission to access the drive" I am a little puzzled. How come it allows me to access the drive for a couple of seconds and then it throws up the error? Can somebody please help me solve this problem so that I can share my local drive to the remote machine comfortably. Thanks Sesh
rdesktop segmentation fault
Hallo all. at our server I have installed rdesktop_1.5.0-1~bpo.1_i386.deb and the xf86-packeges 4.3.0.dfsg.1-14sarge3. Last week I update it to 4.3.0.dfsg.1-14sarge4. Now the rdesktop has a segmentation fault. The Version 1.4.0-2sarge1of rdesktop run without this error. Is there a patch for this problem? I need the option for setting keymap depending on the current locale. regards Monika -- Monika Strack Institut fuer Tierzucht Bundesforschungsanstalt fuer Landwirtschaft 31535 Neustadt e-mail: [EMAIL PROTECTED] Germany Tel: +49 5034 /871 154 Fax: +49 5034 /871 239 ___ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems with rdesktop
>> > The man page says: >> Note that the colour depth may also be limited by the server configuration. >> > > I suspect the problem may be on the server end of things, but I'm unsure > how you'd configure that. What I forgot to mention. On another machine running Solaris, I can run rdesktop with "-a" without any problems. So the server seems not to be the problem. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems with rdesktop
Christian Christmann wrote: > Hi, > > I'm running rdesktop v1.3.0 on my Debian Sarge box. > > When I try to connect to a Windows XP system, this > works fine with "rdesktop WINPC". However, when I specify > the color depth with "rdesktop -a 16 WINPC", the connection > is not established but I get the rdesktop usage message. > What is wrong? Why is "-a X" not accepted even though it > is explicitly mentioned in the man pages? > The man page says: > Note that the colour depth may also be limited by the server configuration. > I suspect the problem may be on the server end of things, but I'm unsure how you'd configure that. -- Kent West Westing Peacefully <http://kentwest.blogspot.com> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Problems with rdesktop
Hi, I'm running rdesktop v1.3.0 on my Debian Sarge box. When I try to connect to a Windows XP system, this works fine with "rdesktop WINPC". However, when I specify the color depth with "rdesktop -a 16 WINPC", the connection is not established but I get the rdesktop usage message. What is wrong? Why is "-a X" not accepted even though it is explicitly mentioned in the man pages? Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Rdesktop users?
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. There was a particular option one would I think that giving you the answer you want (how to "fake" a license) could be considered a violation of the DMCA ;-) The "correct" answer is: buy a license and set up a license server. -- Mark Roach -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Rdesktop users?
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 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. There was a particular option one would add to the rdesktop command to do this. But now I can find no such documentation. Can anyone help? Curtis Vaughan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: rdesktop error
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.: ./rdesktop -u curtis -f 10.0.0.1 Best of luck. On Thursday 28 February 2002 05:32 am, you wrote: > hi, > > i just downloaded rdesktop-1.1.0. Extracted it, and run 'make'. > but i encountered the error below when i run "./rdesktop" > can anyone explain what the error means and what direction > i should take to make it work. i am running rh7.2. thanks. > > > [EMAIL PROTECTED] rdesktop-1.1.0]# ./rdesktop > rdesktop: A Remote Desktop Protocol client. > Version 1.1.0. Copyright (C) 1999-2001 Matt Chapman. > See http://www.rdesktop.org/ for more information. > > Usage: ./rdesktop [options] server >-u: user name >-d: domain >-s: shell >-c: working directory >-p: password (autologon) >-n: client hostname >-k: keyboard layout (hex) >-g: desktop geometry (WxH) >-f: full-screen mode >-b: force bitmap updates >-e: disable encryption (French TS) >-m: do not send motion events > -l: do not request licence > > [EMAIL PROTECTED] rdesktop-1.1.0]# ./rdesktop 192.168.0.1 > rdesktop: A Remote Desktop Protocol client. > Version 1.1.0. Copyright (C) 1999-2001 Matt Chapman. > See http://www.rdesktop.org/ for more information. > > Xlib: connection to ":0.0" refused by server > Xlib: Client is not authorized to connect to Server > ERROR: Failed to open display > ERROR: send: Socket operation on non-socket
