1. (I'm running firewall software and) When I try to activate remote controlling, I get a message indicating that I cannot connect the system to be controlled. What do I do?
   
   
2. How do I setup ZoneAlarm firewall software to allow KMremoteControl?
   
   
3. How do I setup Mac OS X firewall software to allow KMremoteControl?
   
   
4. How do I setup Little Snitch firewall software to allow KMremoteControl?
   
   
5. What should I know about the behavior of the "caps lock" key?
   
   
6. What should I know about the behavior of the "num lock" key?
   
   
7. How do I send F13, F14 or F15 when controlling a Mac OS X system from a PC/Windows system?
   
   
8. How do I send Ctrl-Break when controlling a PC/Windows system from a Mac OS X system?
   
   
9. How do I send a PrintScreen when controlling a PC/Windows system from a Mac OS X system?
   
   
10. Can I run KMremoteControl on Virtual PC?
    
    
11. Can I use KMremoteControl to remote control a system upon which I'm playing a game?
    
    
12. My software was licensed but suddenly it behaves as though it's not licensed any more. What should I do?
    
    
13. I'm controlling another system from a Mac OS X system ... how do I use the application switcher on the system being controlled?

1. (I'm running firewall software and) When I try to activate remote controlling, I get a message indicating that I cannot connect the system to be controlled. What do I do?

Normally, the inability to connect to a system is due to:

• the system not being visible on the network (determine whether you can you "ping" it with a network utility? ... can you "see" it for filesharing? ... do I have a route to the system? ... etc.)
  
  
• the networking port you are trying to access is not visible on the network (this issue often appears identical to the previous issue since it's a particular case of the previous issue)

The first issue is general network setup and is beyond the scope of our products and this FAQ. The second issue will be encountered if you are running firewall software.

In addition to the firewall setup that is part of most modern operating systems, there are numerous third-party software firewalls and firewall-setup programs. Regardless of how your particular firewall software accomplishes it, you'll need to setup the following firewall entry:

• allow TCP communications via port 4888 (or the port you have set via the KMremoteControl "Networking" preferences)

If you are using firewall software that distinguishes between client and server behavior, then you should know that, technically, the system "being controlled" is running the KMremoteControl server software and the "remote controlling" software is running the KMremoteControl client software.

Depending upon the naming you use for the "System to Control", KMremoteControl may also make naming queries that cause access to the Domain Name resolution services and these will normally require setup for any outgoing firewalls. However, since this is not unique to KMremoteControl, it is assumed that these services would already be set up.

2. How do I setup ZoneAlarm firewall software to allow KMremoteControl?

Two things must be done in order to remote control a computer running ZoneAlarm:

• When you first enable the computer to for "being controlled", Zone Alarm will show an alert querying whether KMremoteControl should be allowed to act as a server. Respond "Yes", and also select the check-box "Remember this answer the next time I use this program."
  
  
• You must also add, to your Trusted Zone, the computer that will be doing the remote controlling (or the network on which that computer resides). Open ZoneAlarm and go to the "Zones" tab of the "Firewall" page. Using the "Add" button, add the IP address of the desired computer to the Trusted Zone.
  
  Adding the computer to the trusted zone is essential if you want KMremoteControl to function properly immediately after a reboot when the "Activation" on the "Being Controlled" preferences is set to "Permit this system to be remote controlled as soon as possible during system startup".

When operating Windows-to-Windows, ZoneAlarm can be avoided by connecting by computer name rather than by IP address.

3. How do I setup Mac OS X firewall software to allow KMremoteControl?

On the system(s) that will be controlled:

• Open the "System Preferences" and visit the "Sharing" panel.
  
  
• Press the "New..." button
  
  
• On the drop-down, select "Other" in the pop-up menu beside "Port Name:"
  
  
• For "Port Number, Range, or Series:", enter 4888 (or the port you have set via the KMremoteControl "Networking" preferences)
  
  
• Enter "KMremoteControl" (or whatever you prefer) for the "Description:"
  
  
• Press the "OK" button

4. How do I setup Little Snitch firewall software to allow KMremoteControl?

On the system(s) that will be remote controlling other systems:

• Open the "System Preferences" and visit the "Little Snitch" panel.
  
  
• Press the lock button and supply an Administrator's password
  
  
• Depending upon your version, press the "New..." button or select the "New..." pop-up menu
  
  
• On the drop-down, press the "Choose..." button beside the "Application:" label
  
  
• For "Permission:", select the "Allow" item in the pop-up menu
  
  
• For "Server:", enter the IP address of the system you want to control
  
  
• For "Port:", enter 4888 (or the port you have set via the KMremoteControl "Networking" preferences)
  
  
• For "Protocol:", select the "tcp" (or "any") item in the pop-up menu
  
  
• Press the "Save" button

On the PC hardware, the "caps lock" functions as a keystroke to Windows and windows communicates the information to the keyboard to turn on the "caps lock" light/indicator (assuming there is one). In effect, the state of the "caps lock" concept is maintained by Windows, not the keyboard hardware.


On the Mac hardware, the "caps lock" functions to set the "caps lock" state in the keyboard hardware, which turns on the "caps lock" light/indicator (assuming there is one). In effect, the state of the "caps lock" concept is maintained by the keyboard hardware, not by OS X.

PC/Windows controlling PC/Windows: You can always activate and deactivate the "caps lock". This is true regardless of whether you issue the "caps lock" on the keyboard locally attached to the controlling system or the system being controlled. The worst that can happen is that the "caps lock" indicator light on the two keyboards will be out of sync.


PC/Windows controlling Mac OS X: If the "caps lock" on the system being controlled is activated, it will override the "caps lock" behavior from the remote controlling system and only uppercase characters will be supplied to the system being controlled.


Mac OS X controlling PC/Windows: You can always activate and deactivate the "caps lock". This is true regardless of whether you issue the "caps lock" on the keyboard locally attached to the controlling system or the system being controlled. The worst that can happen is that the "caps lock" indicator light on the two keyboards will be out of sync.


Mac OS X controlling Mac OS X: If the "caps lock" on the system being controlled is activated, it will override the "caps lock" behavior from the remote controlling system and only uppercase characters will be supplied to the system being controlled.

Virtual PC from the Mac upon which it is running


the Mac upon which Virtual PC is running from Virtual PC running on that Mac

If the status indicates "The license is invalid. ... [20178]" then it's likely that your system/boot disk has been defragmented. Disk defragmenting, depending upon the condition of a disk, can corrupt the licensing information. For now, we recommend that you do not run defragmenting on a scheduled basis.


If the status indicates "The license is invalid. ..." ending in some number other than "[20178]" and this problem recurs after relicensing, please contact us with the full text and error number.