VNC Java Client Setup for Remote Access

One of the requirements that we have is to be able to look at the status of a running test to verify the status.

The simplest way to do this is to point your browser at port 5800 on the host running the VNC Server - http://xxx.xxx.xxx.xxx:5800. By default TightVNC installs a Java client on every server host.

 Follow the directions below if you want to reach different hosts from a single point of contact.

 Here are steps for doing this on Oracle Linux (I used Apache, but hopefully this should work with NodeJS eventually)-

  • Install Apache (sudo yum install httpd)
  • Modify the /etc/httpd/conf/httpd.conf and add the following section to it under 'Aliases' -

What is your first and last name?
  [Unknown]:  FName LName
What is the name of your organizational unit?
  [Unknown]:  MyGroup
What is the name of your organization?
  [Unknown]:  Some Company
What is the name of your City or Locality?
  [Unknown]:  New York
What is the name of your State or Province?
  [Unknown]:  New York
What is the two-letter country code for this unit?
  [Unknown]:  US
Is CN=FName LName, OU= MyGroup, O=Some Company, L=New York, ST=New York, C=US correct?
  [no]:  yes

Enter key password for
  (RETURN if same as keystore password): 
  • Export the certificate you just created (keytool -export vnckey -file vnckey.crt)
  • Sign the VNC jar file using the key you just created (jarsigner /var/www/vnc/VncViewer.jar vnckey)
  • Your certificate is valid for 6 months and you will need to re-sign the applet again in 6 months (unless you sign it with an authoritative key)
  • Create your HTML page for the applet -

  • The full list of available parameters is in the README - http://www.tightvnc.com/doc/java/README.txt
  • A few things to be aware of -
    • Unsigned Java applets are sandboxed and cannot make remote connections. They can only connect to localhost. If you see "Error: access denied (java.net.SocketPermission", the applet is unsigned
    • Make sure that the VNC Server has a read-only password set so that your mouse clicks and keystrokes don't interrupt work in progress
    • The first time you run the app, you will be prompted to give the app permission to run. Make sure you check all the boxes or the applet will not run

Comments

Post a Comment

Popular posts from this blog

The Forecaster Brown Fan Club

I spent the last couple of weeks in October watching what could only be described as the Idiot's Guide to the Wikipedia entry on Hurricane Sandy, otherwise known as the Weather Channel (it was the only live channel I could find online). Half of it involved presenters with an emotional age of 14 trying to get as close to the storm surge as they could, while Dr. Thang in Atlanta helpfully pointed out the eye of the storm every so often. It left me wondering why India had fought so hard for a Cray XMP-24 all those decades ago when all they needed was a helicopter, a doppler, a satellite photo and a half-crazed adolescent with a death-wish. Then I came across this page written by the imaginately named 'Forecaster Brown'. The post, dated ' 1100 AM EDT SAT OCT 27 2012 ' begins " NOAA AND AIR FORCE RESERVE HURRICANE HUNTER AIRCRAFT HAVE BEEN  SAMPLING THE CYCLONE THIS MORNING. "  It turns out the NOAA (National Oceanic and Atmospheric Administ
Read more

How to Create a Pentaho Report Using the REST Client

Image
Prerequisites Pentaho Kettle (see earlier blog post) Pentaho Report Designer You will get an error message in Pentaho Report Designer that says ' java.lang.NoClassDefFoundErr: com/sun/jersey/api/client/ClientConfig ' if you try to run a report against the Kettle job. To fix this error copy the following files from  C:\pentaho\data-integration\libext\jersey\ to C:\pentaho\prd-ce-3.9.1-GA\report-designer\lib\. If you plan to ublish the report to the BI Server, also copy these files to C:\pentaho\biserver-ce\tomcat\webapps\pentaho\WEB-INF\lib\ as well - jersey-apache-client-1.7.jar jersey-client-1.7.jar jersey-core-1.7.jar The Payload My example returns an array of objects [   {       "id":"1",       "name":"item1",       "description":"someDescription1"   },   {       "id":"2",       "name":"item2",       "de
Read more

Automated Testing with vncdotool (Not Headless, but Hairless)

Image
The headless testing problem is a thorny one and impacts the fundamental architecture of the test automation platform I'm working on. If we can't find a solution, we might not be able to use the private cloud nor parallelize our testing effectively. Part of the problem are the tests themselves that still rely on SendKeys() and MouseMove(). Two aspects of remote interaction that are insecure and therefore disallowed by Microsoft from Windows Vista onwards. This means that we have to rely on hacks like the VIX API and the one that I am about to document below. There are two widely-used technologies for remote interactive connectivity on the Windows platform - the Remote Desktop Client (RDC) and VNC. The first is entirely proprietary while the second offers a number of open-source implementations (and some proprietary, full-featured, commercial implementations). The RDC implementation requires access to the VIX API which in turn relies on proprietary, privileged access t
Read more