Rdesktop Autoselected Keyboard Map En-us Error Unable To Connect
Install and set-up one of the vnc server flavors on the windows side. Then you can use vinagre (just one of several vnc viewers available) on the linux side (i don't think it's installed by default in mint, check package manager) to remotely access your windows desktop across the LAN.
Hey, Recent Windows Server release (like 2012) seems to require some additional feature the good old “rdesktop” tools do not handle. Here is what happens when connecting: Autoselected keyboard map en-us ERROR: CredSSP: Initialize failed, do you have correct kerberos tgt initialized? Failed to connect, CredSSP required by server.
Many people around Internet suggest disabling something on the server but it means disabling some security feature. Hara hara mahadeva serial in kannada. Moreover, you might need to use RDP to disable this (ZeroDivisionError) and you may not be allowed to do so. Anyway, shitty answser. Here is the proper one: This client just works but has the same issue as rdesktop: it’s highly stupid. For instance, look at the error message above and notice “Autoselected keyboard map en-us”.
It’s not because I’m using en_US locale that I’m actually staying in the United States and using a regular ANSI QWERTY keyboard. In fact, I’m not, not at all. Another issue is the screen size setting which seems to be always set to 1024×768 which is a pitty nowadays, everybody uses at least “FullHD” screen. So I made a shell wrapper script implementing dynamic screen size selection to 90% of your current display (configurable) and setting the right keymap according to your keyboard layout and variant (layout=ch, variant=fr for me, which is a french oriented QWERTZU layout used in Luxembourg and called by Windows “Swiss French”). It also feature a configuration file to override defaults and some handy default options to share clipboard and home disk with the remote target. All you have to do is to put saner-xfreerdp in /usr/local/bin/ and use it instead of the real binary. Get the script here: Here is an very simple usage example: user@host:~$ saner-xfreerdp -u username -a some-srv-01.domain.lan INFO: Detected active screen on monitor DVI-0 with width=1920 and height=1200 INFO: Will use resized resolution of 1728×1080 INFO: Running xfreerdp +clipboard +home-drive /u:”username” /v:”some-srv-01.domain.lan” /kbd:”Swiss French” /w:1728 /h:1080 [xrdp logs] Password: This entry was posted in.
Bookmark the.
Hameau wrote:You have to use the host IP address, as I recall. If you need to connect to more than one guest, set them to different ports. Hi hameau, I tried both host and guest ip without result. Only one guest is running. On VirtualBox 'rdesktop 192.168.0.10:3389' works without problem.
192.168.0.10 is the host ip. If there are more than one VM (on VBox) use 3390/3391 etc. However after having spent several hours I can't make rdesktop to work. I also tried 'ssh -X 192.168.0.30' but I can't start X on the workstation. Satimis Posts: 500 Joined: 2004-09-11 11:50 Location: Hong Kong.
Gychang wrote:this is how I connect to my office XP machine from debian: rdesktop -u -p -f -a 16 Hi gychang, The same mistake. On host $ rdesktop 192.168.0.30 -u satimis -p mypasswd -f -a 16 Code: Autoselected keyboard map en-us ERROR: 192.168.0.30: unable to connect 192.168.0.30 = guest ip address On a workstation on LAN I performed following steps running ssh to connect the guest; $ sudo /etc/init.d/gdm stop close X windows $ ssh -X 192.168.0.30 guest connected $ export DISPLAY=:0.0 $ xterm failed. I can't start xterm Having tried many ways to export Display without success. IIRC I did that before several years back. On xterm I started X of the guest.