I have a machine at the University on which I run an nVidia GTX580. It works great if I use it on the console, and I can turn on the GRU rendering which works very well.
But if I get a Remote Desktop session into the machine, I cannot turn on CUDA anymore, it simply is not in the options list. And if I go back to the console, it is there.
What should I try to fix in the RDP to get the machine to render on GPU even if I am home and come in using RDP? This has me baffled.
Another fun part: if I boot Blender on console, then switch to RDP and join the session, I have CUDA. So the question actually is… why can I not initiate a CUDA-capable session remotely?
I had the same problem with octane (cuda only renderer) and vnc and rdp.
It worked with teamviever and teamviever is based on turboVNC.
After setup with turboVNC I have no problems.
May you test teamviewer.
This is causing me serious problems too! I left my work PC turned on, rendering an animation on the GPU. During the night, the PC unhelpfully decided to install some updates and restart itself, killing Blender. Now, if I start Blender from home over Remote Desktop (via a Cisco VPN connection), sure enough my GPU is not listed any more. Even starting the render using a command line (i.e without opening Blender) doesn’t work. The only workaround I can find is to set the tile size to 16x16 pixels (see this: http://www.blenderguru.com/4-easy-ways-to-speed-up-cycles/) and let the i7 CPU do it on 8 threads. Takes 3-4 times as long as my [pathetically bad] Quadro 4000 GPU, but at least it will get a few frames done before I go back into work tomorrow…
Install Splashtop Streamer on your remote computer and the correspoding client on your machine. Also, your firewall needs to have the ports 6783 to 6785 open (this caused me some problems).
We have been using tightvnc for network based control for blender as we ran into the same problems with RDP… seems like RDP doesnt actually initialize the gpu properly and is more of a shell then a desktop viewer.