-------- Original Message -------- Subject: rdesktop woes From: "Kevin J. Cummings" <cummings@xxxxxxxxxxxxxxxxxx> To: For users of Fedora <fedora-list@xxxxxxxxxx> Date: 01/15/2008 12:26 PM
Paul Lemmons wrote:-------- Original Message -------- Subject: rdesktop woes From: "Kevin J. Cummings" <cummings@xxxxxxxxxxxxxxxxxx> To: For users of Fedora <fedora-list@xxxxxxxxxx> Date: 01/15/2008 11:22 AMPaul 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 me:rdesktop -u "Janet Cummings" -g 1024x768 -d JMCPC 192.168.6.102:3389rdesktop -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 size.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: /etc/hosts 192.168.0.100 xphost-nameI'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 ping. 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:
<Snip strace>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:
uname -a rpm -qa | grep rdesktop Here is what I am running: $ uname -aLinux xxxxxx.tmcaz.com 2.6.23.9-85.fc8 #1 SMP Fri Dec 7 15:49:59 EST 2007 i686 i686 i386 GNU/Linux
$ rpm -qa | grep rdesktop rdesktop-1.5.0-4.fc8I 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?
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
-- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list