VNC2Me comes with large amounts of debugging abilities built into the program, but debugging needs to be enabled in the INI file first.
Open the vnc2me_sc.ini file in your favourite editor (mine is notepad++) within the [V2M_GUI] section of the INI (near the top) is the option "MAIN_ENABLE_DEBUG=0", this should be set to "MAIN_ENABLE_DEBUG=1". This will enable the Debug checkbox near to the "Exit" button on the Main window, and a "Debug" option in the "Show" Menu of the Tray icon.
Two possible uses for debugging are:
- Setup on NEW custom SSH server.
- One / Some clients are having connection problems.
Basic Debugging
Type 2 above is the easiest to describe, as you have already eliminated possible SSH server problems due to most clients ability to connect successfully.
so lets start there:
- Enable debugging using above method
- Test and copy debug output to a text file (or other document such as spreadsheet)
- Package this using your preferred method (setup scripts are provided in SVN or "Roll-your-Own" package), and send to the client.
- Have the client open the application and tick the box (or use tray menu) to show the debug window.
- Initiate the client connection (using the normal buttons on the main window).
- Upon connection failure, press the "Debug > Clipboard" button on the debug window to copy all debug output to clipboard.
- Instruct client to paste into email (or other).
- Compare unsuccessful client connection with successful to find where application stops
This is the simplest way of debugging the application, as minimal data is collected.
Advanced Debugging
For more advanced troubleshooting, we have enabled the standard windows debugging system used by many applications, so applications like "sysinternals debugview
" can be used to view all actions (well most) of the application. This allows pausing of debug output, large amounts of history to be viewed easily (its not unlimited), and many other features. Follow Step 1 of the above instructions to enable debugging, then:
- Download and run a debugging program like "sysinternals debugview"
- Close all running application that may be using this debugging system (best to close as much as you can)
- Start VNC2Me with debugging enabled (described above)
- View debugging output and troubleshoot problem.
If problem appears to be related to the SSH connection, try opening a command prompt in the VNC2Me directory, then open v2mplink using the following arguments: " your.host -v -ssh" (include a space between v2mplink and you host name)
You may also want to include any of the following:
- -P port# (connect to specified port - if different from 22)
- -l username (connect with specified username - otherwise plink asks)
- -pw password (login with specified password - otherwise plink asks)
- -2 (force use of SSH protocol Version 2) (NOTE: SSH Version 2 should be used in 99.9% of cases)
This should give you a successful connection, and allow you to run commands like "ls" on Linux or "dir" on windows. If you are unsuccessful with connecting using plink, then the problem is outside of the scope of our help, and you should lookup the problem in Google, or contact your hosting provider.
Add this page to your favorite Social Bookmarking websites
