paul.lemmons at tmcaz.com
Tue Jan 15 19:59:29 UTC 2008
-------- Original Message --------
Subject: rdesktop woes
From: "Kevin J. Cummings" <cummings at kjchome.homeip.net>
To: For users of Fedora <fedora-list at redhat.com>
Date: 01/15/2008 12:26 PM
> Paul Lemmons wrote:
>> -------- Original Message --------
>> Subject: rdesktop woes
>> From: "Kevin J. Cummings" <cummings at kjchome.homeip.net>
>> To: For users of Fedora <fedora-list at redhat.com>
>> Date: 01/15/2008 11:22 AM
>>> Paul Lemmons wrote:
>>>> Can you share the rdesktop command you are using? Also here is an
>>>> rdesktop command that I use all of the time that works flawlessly for
>>> rdesktop -u "Janet Cummings" -g 1024x768 -d JMCPC 192.168.6.102:3389
>>>> rdesktop -Txyznbu1 -nmybox -g1270x950 -a24 -rsound -b -4 xyznbu1
>>>> This connect to a box named "xyznbu1". It gives the window a title of
>>>> the same name. Other options determine color depth, protocol and screen
>>> for me, I'm trying to connect to my wife's computer, specified by IP
>>> address and Remote Desktop port number. I'm using the user name listed
>>> by the RAIncident file that was created by Windows Remote Desktop. For
>>> my testing purposes, there is no password, and the computer has its own
>>> domain name (same as its windows network name).
>>>> If your command options differ, try the ones above and see if you have
>>>> any success.
>>>> Other things to consider:
>>>> The host name must be resolvable. To check this out:
>>>> $ host xphost-name
>>>> if it resolves, great. If not try
>>>> $ ping xphost-IP-address
>>>> If you can ping it try adding a line in:
>>>> 192.168.0.100 xphost-name
>>> I'm using the IP address. Is rdesktop not smart enough to know the
>>> difference? (I hadn't thought about this before....)
>>>> Where the address above is replaced with the actual address of the
>>>> computer running XP.
>>>> If it does not respond to ping, make sure you have the right address and
>>>> get ping working before you do anything further.
>>>> Then try the host and ping using the name. If both are successful, then
>>>> try the rdesktop command again.
>>> Like I said, I can connect from windows running in VMWare on the same
>>> computer. The network is fine.
>> If you are doing it by IP address you will not need to worry about the
>> /etc/hosts file. It is just a convenience. Just make sure it responds to
>> What happens if we use the simplest possible command line.
>> rdesktop 192.168.6.102
>> This takes the defaults for everything. If this works we can add
>> options. If it fails, we can look for something else more complicated.
> It fails in exactly the same fashion:
> it prints 1 message:
> Autoselected keyboard map en-us
> a windows appears, and quickly disappears. No other messages.
> strace below:
I have run an strace on my working version and compared it to yours.
Amazingly enough they compare fairly well. I do see different IO calls
being made though. Can you issue the following two commands:
rpm -qa | grep rdesktop
Here is what I am running:
$ uname -a
Linux xxxxxx.tmcaz.com 126.96.36.199-85.fc8 #1 SMP Fri Dec 7 15:49:59 EST
2007 i686 i686 i386 GNU/Linux
$ rpm -qa | grep rdesktop
I am assuming that you are also using XP Professional, because you can
RDP from Windows to Windows. When you use Windows are you using the
"Remote Desktop Connection" client?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 3257 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.fedoraproject.org/pipermail/users/attachments/20080115/5feba22e/attachment-0001.bin
More information about the users