# Configuring Remote Kernel via terminal in Linux

There's a server at work, which I would like to use as a remote kernel. I have access to it via terminal (server is running Red Hat, my client Windows 7). I don't know if the kernel is set up or not, so I want to check this. However, I don't know how perform this check in the terminal. All guides I have seen so far require the front end.

So, is there a way to configure a remote kernel via the terminal?

-
So you want to run the front end on your own computer, and run a kernel at a remote location? If yes, you don't need to set up anything on the kernel side. You need to set up the correct launch command on the front end side, on your computer. If the server is not directly accessible, you may need to forward some ports through SSH which may be some trouble. (In that case try using the remote kernel strategies package.) –  Szabolcs May 27 '13 at 19:08
@Szabolcs Thanks, that is exactly what I want. I am connected via VPN, I guess that should do it. Why isnt it necessary to config the kernel of the server? –  BillyJean May 27 '13 at 19:28
When the front end launches a kernel, it creates a link, launches the kernel process and passes it command line options which tell it what link to connect to. What you need to do in your case is modify the launching so it happens on the remote machine and modify the link creation so it'll use TCP/IP. It may be sufficient to choose "remote machine" in the kernel configuration options. –  Szabolcs May 27 '13 at 19:32
@Szabolcs I tried setting up a new kernel (using Basic Options), where I give server name, login name and command ("math"). When I evaluate an expression I enter my password, but I get the message: The kernel test failed to connect to the front end. (Error = MLECONNECT). You should try running the kernel connection outside the front end.. Now sure what to make of this. –  BillyJean May 27 '13 at 19:58
In the past, when I tried to get things like this working, I didn't have a very good experience. There maybe several things that can go wrong, unfortunately. Does it prompt from a password when you launch the kernel? Can you try to set up passwordless authentication on the Linux server and try again? If that doesn't work, then your best (= least-effort) bet might be the Remote Kernel Strategies package I linked to. It will try to automatically tunnel the necessary ports though SSH, ... –  Szabolcs May 28 '13 at 20:38