Novell ZENWORKS LINUX MANAGEMENT 7.3 IR2 - ADMINISTRATION GUIDE 02-12-2010 Administration Manual

Also see for ZENWORKS LINUX MANAGEMENT 7.3 IR2: Installation guide

Contents

Novell ZENWORKS LINUX MANAGEMENT 7.3 IR2 - ADMINISTRATION GUIDE 02-12-2010 Administration Manual Manual pdf 670 page image

670 Novell ZENworks 7.3 Linux Management Administration Guidenovdocx (en) 7 January 2010ssh -L 5952:work:5950 work Any connections to port 5952 on your local management console would actually connect to5950 on “work,” so instead of running a vnc viewer as:vncviewer work:50run it as follows:vncviewer localhost :52Figure J-1 Linux Console to Linux Managed Device with TunnelingNOTE: If you are using the Linux VNC viewer to connect via SSH, when the viewer connects to aserver on the local management console, by default it uses VNC’s pixel encoding because thisgenerally gives better performance for local access. If this server is actually an SSHD redirecting thedata for another workstation, you can override this using the -tight option to the viewer or you cansend a lot more data over the network.J.2 SSH Tunneling between a WindowsManagement Console and a Linux ManagedDeviceSSH clients are also available for Windows, Macintosh, and other platforms, but if you want serverson these platforms you might need to use a commercial version or route your connection via a Linuxdevice.There are several scenarios for using SSH tunneling between a Windows management console and aLinux managed device. For the sake of simplicity, the following procedure uses a scenario in whichyou are using a Windows laptop “viewer” in a non-secure Wide Area Network to remotely controlyour Linux managed device “work” installed inside your secure Local Area Network. AnotherLinux device called “gateway” is in your secure local area network and runs the SSH daemon. Thefollowing steps explain how you can use the PuTTY SSH client to configure an SSH tunnel so thatthe Remote Management data is encrypted when it travels between “viewer” and “gateway” and isthen forwarded to “work” inside the secure network.NOTE: The PuTTY SSH client is available at the PuTTY site (http://www.chiark.greenend.org.uk/~sgtatham/putty). If you are using other SSH client software, use the appropriate commands for thatsoftware.1 Enter the following command in the shell prompt:putty -L 5952:work:5950 gatewayThe first argument is the local forwarding option, which says that the local fake port 5952should be created and connected to the genuine port work:5950. The second argument is themain non-option parameter to SSH, which tells it to connect to the device that runs the SSHdaemon.