LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 02-28-2013, 12:39 PM   #1
Ook
Member
 
Registered: Apr 2004
Location: Hell, Arizona
Distribution: Slackware 14.1
Posts: 359

Rep: Reputation: 32
Caps stuck on when I vnc into linux box from windows VM


This is a problem that has plagued me for a while now, and I have not yet found a solution. I'm not even 100% certain it is a linux problem.

I'm using Slackware 14 64 bit.

I run VirtualBox, XP 32. In this VM I use Cisco AnyConnect VPN Client (cause I can't get it to work under linux, so I use it in the VM - been doing this for years, works great). Once the VPN connection is established, I can access the remote network fine. The problem is that when I remote into a linux box, the capslock is stuck on. I remote into a XP box, no problem, it is just when I remote into the linux box that the capslock is stuck. I can't for the life of me figure out how to get this to work. Anyone have any ideas/suggestions on what would cause the capslock to be stuck on only when I remote into linux boxes?
 
Old 03-01-2013, 11:03 AM   #2
Ook
Member
 
Registered: Apr 2004
Location: Hell, Arizona
Distribution: Slackware 14.1
Posts: 359

Original Poster
Rep: Reputation: 32
In case my posts don't make sense, here is the current config.

Host machine: Slackware 14 64 bit.
Guest machine: Windows XP running in VirtualBox on the slackware host.

If I remote into the Slackware box via tightvnc, and then start up the guest vm and start working in the vm, sometimes the caps lock and sometimes control key stick, and can't be unstuck. This makes it impossible to control the VM. Outside of the VM everything is fine, but at this point I can't use the VM. Rebooting the VM doesn't help. Rebooting the linux box does.

If I'm at my desk instead of remoting in via tightvnc, it works great, I work like this all the time. But if I remote into the linux box via tightvnc, sometimes the caps and ctrl stick when using the VM.

So there is some weird combination of using tightvnc to get into the linux box, and from there running the vm. The only solution so far has been to reboot the linux box.
 
Old 03-01-2013, 12:19 PM   #3
burdi01
Member
 
Registered: Dec 2010
Location: The Netherlands
Distribution: Slackware, Xubuntu, PartedMagic
Posts: 72

Rep: Reputation: 7
What about using an other VNC such as TigerVNC?
And what about accessing the VM via VB's RDP?
Just my 2 cents.
 
Old 03-01-2013, 03:51 PM   #4
Ook
Member
 
Registered: Apr 2004
Location: Hell, Arizona
Distribution: Slackware 14.1
Posts: 359

Original Poster
Rep: Reputation: 32
Quote:
Originally Posted by burdi01 View Post
What about using an other VNC such as TigerVNC?
And what about accessing the VM via VB's RDP?
Just my 2 cents.
Trying another VNC is next on the trouble shooting list, as this only happens when I VNC in. If it's the tightvnc client and not the KDE desktop sharing server (which I'm currently using), this might work. I'm also wondering if tightvnc's own server might help instead.

Hmm...never thought of using RDP to get into the VM instead of going through the linux box. I have the network on the VM set to NAT, I may have to set it to bridged so it is accessible from outside of the host. I wonder if I can forward the rdp port from the VM to the host instead? I currently have ports 1433 (mssql) forwarded to the host so I can access mssql from other machines on the network, and that works fine. Definitely going to give this some thought and play with it, that is a most excellent idea!
 
Old 03-02-2013, 04:35 AM   #5
burdi01
Member
 
Registered: Dec 2010
Location: The Netherlands
Distribution: Slackware, Xubuntu, PartedMagic
Posts: 72

Rep: Reputation: 7
VB's RDP works via a port on the host, not the VM. So whether or not the VM has NAT is irrelevant.
Actually you do not need VNC at all in this scenario. I would telnet/ssh into the remove box and issue a vboxheadless for the VM therein. And then I would use VB's RDP to access the VM.
As an alternative you could start an RDP or a VNC server *in* the VM. Of course that VM should not be NAT then.

Last edited by burdi01; 03-02-2013 at 09:04 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Stuck on file sharing cant auth with windows box problemchild200 Linux - Server 2 09-13-2008 02:09 AM
No able to VNC from windows to Linux box but iam able to vnc from linux to windows. vinaykori Linux - Software 1 01-20-2008 10:46 AM
VNC from a Windows box to Linux abneru Suse/Novell 18 07-08-2005 10:59 PM
vnc to linux box from windows N_A_J_M Linux - General 6 10-04-2004 12:36 AM
Sending CTRL-ALT-DEL to a Windows 2000 box using VNC from Linux scottpioso Linux - Newbie 1 03-04-2003 04:27 PM


All times are GMT -5. The time now is 02:29 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration