Your local Windows desktop system is now installed with an SSH program (PuTTY), an X-windows server program(Xming) and public/private key icon (e.g. jdoe.ppk). You also have configured a remote host connection in a saved session (e.g. compute) with host name and login details (e.g. compute.example.edu and jdoe). To complete the process, you need to exchange keys to allow a trusted connection from your Windows desktop system to this saved session.
follow the prompts and type your responses as shown below. Otherwise, proceed to step 4. Prompt Action [jdoe@compute ]$ Type ssh-keygen -C "key comment"
e.g. key comment=jdoe compute Aug26 Enter file in which to save the key (/home/jdoe/.ssh/id_rsa): Press return to accept the default key file name shown in parentheses Enter passphrase: Press return Enter same passphrase again: Press return [jdoe@compute ]$ Type ssh-add -L >> .ssh/authorized_keys
When you no longer need Xming, right-click the Xming icon in the taskbar and click Exit. Then click Exit again in the Xming - Exit? window. This will close all X-windowsand running applications.
I am using Xming to access QGIS GUI and have difficulties as some windows just won't fit in the screen and there is no option to resize them so after making some changes in a particular menu/window I can not see save button. Attaching print screen where settings window is visible (while main window is in the background):
Changing display scaling (on Windows 10) to 100% and launching Xming via XLaunch with -screen 0 X Y where X and Y matches max resolution makes QGIS/Xming windows fit the screen. If someone knows a solution where display scaling does not need to be changed please post it as an answer.
I usually have two monitors with the primary monitor on the right and the secondary monitor on the left. Now Cadence opens all windows on my secondary monitor and I always need to drag them manually back to my primary monitor on the right.
There are some cdsenv settings for each of the tools to specify the default coordinates where windows are placed - so you could set those (I can't remember what they are called off the top of my head, and don't have the software handy).
The problem with any X-Terminal is that they save the last state of window position when open.Usually you have to clear session buffers.In your case, it would be great if you switch to Xming, their release after 2013 has probably fixed this issue (the last time I used it was a long while back).If you have OS-X, there is an option on dashboard itself to define default monitor for opening Xming windows.
The WSL team is working on getting this feature built in! Soon, it looks likeGUI Linux apps will have not only their own taskbar icons, but proper shadowedwindows and full compatibility without having to worry about Xservers,firewalls, or anything like that. Thank you so much, WSL team!
Regarding the Pulseaudio thing, this is much simpler but similar. You need a pulseaudio daemon running on windows, and then setting the correct Pulseaudio client on WSL to point at 127.0.0.1
X11 Setup
Putty by default has key and mouse bindings different from Xterm. To get xterm-like behaviour (keyboard, mouse) in Putty, run the following registry file in your windows machine.
putty-settings.reg. For details about xterm, see below (Xterm Usage Notes).
To stop the Xming icon from bing hidden in the system icons tray, on Windows 10, go to < windows settings / taskbar / select which icons appear on the taskbar > and turn on the Xming Server icon. In Windows 7, customize the taskbar and select for Xming.
If you use Linux at work, and Windows at home, or vice versa, you might at times need to log in to the computer at your other location, and run programs. Well, you can install an X Server, and enable SSH Tunneling with your SSH Client, and one-up both VNC and Remote Desktop, for speed and usability.
This 'ible covers using sourceforge.net/projects/xming/ and www.bitvise.com/tunnelier as your Windows solutions, and Openssh for the Linux side. On a side note, all of this can also make use of LogMeIn Hamachi as an easy-to-use VPN.
In this step, we'll set up your SSH Client. First, install your copy of Bitvise Tunnelier, and start it up. You can create a connection profile with the Linux server's IP address or hostname, and optionally automatic login information. The next part of this step is filling out the ports to be forwarded via SSH. For the Windows X Server, we'll forward the linux box's port 6010 to the windows box's port 6000, where XMing will run. This way, Linux's own X Server can run undisturbed, at port 6000.
Xming is probably my favorite windows xserver app, but I have noticed some problems with it. Particularly with installing Oracle w/ using xming as an xserver I ran into issues with the installer hanging. When i used a cygwin xserver it didnt have a problem.
So, you want to tunnel your xwindows session? No problem. The first step is to determine what type of machine you will be connecting from. If it is a Windows machine, continue here. If it is a Unix/Linux machine, head for the *nix section.
If you don't have Xming, you can download it from Software Licensing (U of A Login Required). You will be redirected to SourceForge, where you can download the Xming installer (the 'Download' link). You will also need the additional fonts, which are available under the 'Files' link. Install both with the default settings.
You'll also an SSH client; we recommend PuTTY, available here.
Now that we have both of the necessary programs, the first thing you need to do is start up your Xwindows server (Xming or you own personal X Server). NOTE: Xming doesn't bring up a window on your screen, just an entry in your system tray (across from the start menu). Next, fire up PuTTY. This will bring up a window just like figure A.
At this point, you are all set. To start your SSH session, click "Open". If this is your first time connecting, you may receive a warning that the RSA key is not recognized. This is normal, but only if it's your first time connecting. Accept the warning, and enter your username and password when prompted. When you receive a login prompt, you can test the X forwarding by entering the command "xclock". If you see a window containing a clock pop up, you are now tunneling xwindows correctly! Not showing up? Open a support ticket with us at
On the client, simply type the command "ssh -X username@server". The "-X" tells ssh to tunnel your X11 windows. To test the connectivity, try the command "xclock". If you see a clock appear, you are all set.
We have seen this problem a number of times; it's due to Windows, not MCNP. Here are 2 possible solutions:
For Windows clusters, the precompiled MCNP6 executable is based on the MPICH2 package obtained from Argonne National Laboratory. That was found to be reasonably easy to install in precompiled binaries. The MCNP6 executable for 64-bit Windows is found at MCNP_CODE\MCNP6\bin\windows\mcnp6_windows_x86_64_omp_mp and should be copied (and renamed) to MCNP_CODE\bin\mcnp6_mpi.exe. You can then run an MPI job as mpirun -np 8 mcnp6_mpi i=myinp.txt
Oracle DBAs working on windows laptops and connecting to unix/linux environments need an Xwindows server. An Xwindows server is the software you need on your laptop in order to run the GUI interfaces for Oracle installation programs on unix. My favorite Xwindows server is Xming, whose home site is located here, and whose binaries are here.
760c119bf3