MobaXterm Professional provides full X server and SSH support in a portable (no install required) customized (no unwanted games nor tools) application.

connect from Linux servers to Windows clients

Diligent system administrators usually isolate the EPM system servers completely from the Internet, allowing no direct connections. The recommended practice is to download and validate more than 20GB of Oracle EPM source software and patches to a client desktop before transferring to the EPM servers. By running MobaXterm on a Windows client, secure connections, rapid file transfer and remote terminal access is straight-forward from the Windows client to Solaris/Linux servers AND from Solaris/Linux servers to the Windows client.

description

Prerequisite: MobaXterm Professional
This post describes the process that I use to setup MobaXterm Professional. The cost is negligible as we remove components undesirable in client environments (e.g., games, port scanner, network packet capture, http server, NFS server, et cetera).

In addition, we will add plugins (e.g., httperf, Curl, and DnsUtils like dig or  nslookup).

The Home Edition is free, subject to MobaXterm terms and conditions, but somewhat limited and excludes professional support.

steps

1. Subscribe online.
2. Buy and download the MobaXterm Professional package. Existing licensed customers visit Customer Area for updated packages.
3. Download required plugins to project build location
   

   MobaXterm_Customizer and plugins directory

4. Extract the download to project build location, and run MobaXterm_Customizer_x.x.exe 
5. The GUI allows customizations to meet our needs
   

   MobaXterm Customizer GUI

6. Modify the banner – this is what I use:

        ┌────────────────────────────────────────────────────────────────────┐
        │                  • MobaXterm Professional ${V} •                   │
        │            (Unix utilities and X-server on Gnu/Cygwin)             │
        │                                                                    │
        │ ➤ Your computer drives are accessible through the /drives path     │
        │ ➤ Your DISPLAY is set to ${EXPORTED_DISPLAY}                       │
        │ ➤ When using SSH, your remote DISPLAY is automatically forwarded   │
        │ ➤ Each command status is specified by a special symbol (✔ or ✘)    │
        │ ➤ For more info, type help or click on the help button above.      │
        └────────────────────────────────────────────────────────────────────┘
   this product is licensed to Jon H. Williams and installs nothing on the server(s) ...please delete the MobaXterm directory to remove this software from the system

7. Edit the .profile
   

   Editing MobaXterm profile

8. Add a custom logo
   

   Set a custom logo

9. Keep the SSH Server, and remove the un-necessary components
   

   select options and set security

10. Create the portable package
    

    Create the final package

11. Save the customization for re-use
    

    Save customization

12. I name them the same and keep the two pieces together
    

    save the customizations as a file for reuse

13. Close the customizer and test the new package by extracting the zip; I used C:\projects\software\MobaXterm\MobaXterm_Portable_epm-jonhwilliams
14. In addition to the MobaXterm.exe, the folder might contain an automatic backup, configuration files and plugin files, per your selections. MobaXterm configures and starts X at runtime
    

    X is configured and started at runtime

15. Starting an SSH server on Windows is a three-click process. This allows a Linux user to connect to a Windows machine and rsync files as needed.
    

    Select Servers

16. Start, stop and configure SSH Server using the buttons. Use any available port
    

    click the Blue arrow to start the SSH Server on Windows

using rsync and ssh

There are extensive writeups on-line to help with rsync and ssh. Here are the two commands I use most frequently.

First validate that SSH Server (in MobaXterm) is running on the Windows client machine. From the Linux server:

ssh -X WindowsUser@windows.client.where.SoftwareDownloaded

If that works the following will synchronize and validate  all source files in drive L to the Linux hyperion installer drive (dry-run does what you think it should; check out the other options here)

rsync --dry-run -Ivvvrtz -e "ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null" --progress WindowsUser@windows.client.where.SoftwareDownloaded:/drives/l/ /u01/hyperion/installer

external links

The rsync utility can really mess things up if you don’t know what you are doing, so take some time get to know what you are doing. The advantage is a rapid, validated file transfer, that if interrupted will resume without complaint wherever transfer got interrupted.

If you need more robust tools for frequent transfers of massive (TB) data, there are other options.

This is a desired and expected behavior to guarantee a secure connection. When running a temporary SSH server on Windows, it can be repetitive.

steps

Begin by starting the SSH server in MobaXterm on Windows where the source software was downloaded
'Servers' > 'Start SSH/SFTP Server' > 'OK'
From the Linux server, ssh into the Windows Server
'ssh WindowsUser@WindowsServer.where.SourceSoftwareIsDownloaded.com'
Alternately, attempt an rsync to rapidly transfer and verify the source software and patch archives (this requires some fiddling to get right).
'rsync -Ivvvrtz -e "ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null" --progress WindowsUser@WindowsServer.where.SourceSoftwareIsDownloaded.com:/drives/l/ /u01/hyperion/installer'

Some time later, when you attempt to repeat the process, ssh will fail with error like:

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
34:df:34:df:34:df:34:df:34:df:34:df:34:df:34:df.
Please contact your system administrator.
Add correct host key in /home/<user>/.ssh/known_hosts to get rid of this message.
Offending key in /home/<user>/.ssh/known_hosts:3
RSA host key for <servername> has changed and you have requested strict checking.
Host key verification failed.

This is caused by stopping and restarting MobaXterm on the Windows server; The SSH Server fingerprint will change.

Delete the offending key (the location of known_hosts will vary):
sed '3d' -i /var/lib/sss/pubconf/known_hosts  
sed -i -e 3d /home/<user>/.ssh/known_hosts

Note: the sed command is worth learning.

description

MobaXterm is the preferred method for facilitating X and SSH between Windows and Unix/Linux. A single portable exe painlessly facilitates the use of standard tools like rsync. This recurs at most clients for transferring 22.7+ GB of  11.1.2.4.000 Oracle EPM Linux files and patches to a Linux server that is not connected to the Internet.
Additional details are in the MobaXterm toolbox post.

In a normal use case (not a temporary SSH server) one should update the offending key, as long as the same hostname is re-used.
ssh-keygen -R <hostname>

external links

Additional thanks for the post:  user mockinterface  help.
Get more information from stackoverflow.