What would be the best way to establish remote desktop connectivity from a Windows 7 machine to Red Hat Enterprise Linux 6? The machines reside on the same network.
For graphic usage, you have at least the following options:
SPICE (http://spice-space.org/download.html)
NoMachine's NX Server (http://www.nomachine.com/)
VNC (http://www.redhat.com/magazine/006apr05/features/vnc/)
SPICE is newer and pretty slick. I've used NX Server for years and it's great. VNC is pretty unsecure, so use that as a last ditch option.
XRDP is a Remote Desktop Server implementation for Linux. It allows you to use the standard Remote Desktop client that ships with Windows to connect to remote Linux desktops. I've had good results using it in Fedora so I'd imagine it'd handle okay in RHEL.
Here's a tutorial on setting it up: http://sirjune.wordpress.com/2009/11/06/howto-xrdp-on-fedora-rhel/
Adding to the comment from #BoeroBoy. You have to also look into the firewall. I used TightVNC to connect from my workstation(Windows 7) to Red Hat Linux 6, but in vain was not able to(even after activating the Remote Access from System -> Preferences -> Remote Desktop).
So one should also look into System -> Administration -> Firewall and allocate necessary access for process and/or port(s).
Related
I've tryed to RDP an Ubuntu 16.04 and an Mac OSX-lion machine from a Windows Home Pc on a local lan without succsess. What steps should I take for such a connection and which programs, preferably open source are best to use? If there in a link to a tuturial, please share it with me.
Remote Desktop Protocol (RDP) is a proprietary protocol developed by Microsoft, it is not available on Linux. You can use third party software like VNC, Teamviewer
If I create a container with windows image on it, is it possible to use a remote connection to actually see the desktop and , for example, play minesweeper?
My use case is this:
I have hundreds of users. Each user need to create their our infrastructure consisting in about 6 machines linked together. After creating, the user will open some desktop gui apps on each one using a remote desktop connection.
No, this isn't something you will be able to do.
There are currently two Windows container images, microsoft/windowsservercore and microsoft/nanoserver
nanoserver
This blog post about TP4 (one of the earlier releases) says
The only option available when logging into console of a virtual machine running Nano Server or connecting a crash cart to a physical Nano Server is this very plain emergency console
This section on managing Nano server also states
Nano Server is managed remotely. There is no local logon capability at all, nor does it support Terminal Services.
There is also this article, admittedly not from Microsoft, about Windows Nano server
Nano Server strips back the operating system further still, dropping things like the GUI stack, 32-bit Win32 support, local logins, and remote desktop support.
Nano Server is designed for two kinds of workload: cloud apps built on runtimes such as .NET, Java, Node.js, or Python, and cloud infrastructure, such as hosting Hyper-V virtual machines.
servercore
Docker blog has a pretty interesting entry
Introducing Docker for Windows Server 2016. This part addresses the question of GUI apps
The Windows Server Core image comes with a mostly complete userland with the processes and DLLs found on a standard Windows Server Core install. With the exception of GUI apps and apps requiring Windows Remote Desktop, most apps that run on Windows Server can be dockerized to run in an image based on microsoft/windowsservercore with minimal effort.
If you wanted to set up that kind of an environment, one option is to use something like Vagrant to orchestrate starting and provisioning regular windows VMs. Though 6 windows VMs will not be easy on memory.
I am working on a driver for a remote desktop server. Something like UltraVNC(in house protocol).
First of I see that mirror drivers are not supported on windows 8.
Only subset of DDI as a remote display driver.
1)
Does that mean I need to implement Remote Display Driver for windows 8?
2)Starting of with mirror driver and only adding the DDI specified here enough to have Remote Display Driver run on windows 8 (Will it install no windows 8)? It says that remote display driver is a subset of mirror driver.
http://msdn.microsoft.com/en-us/library/windows/hardware/hh974665(v=vs.85).aspx
3) Are there any any any examples? It looks like the mirror driver example is no where to be found ?
UPDATE : (on wdk 7.1) I found these examples.
4) I looked at Utlra VNC server source and It looks like they only have drivers up to Windows 7. However VNC SERVER still supports windows 8(for that it just does GDI stuff on user level to get the image update). So they have not implemented it.
There is a Remote Desktop Protocol Driver. Can that be used ?
5) what is the best place to start ?
Is this windows' way to limit remote desktop server implementation so that it is harder to compete with RDP.
6)
if implementing windows 8 implementing the DDIs necessary to have remote desktop driver is not enough to run it on windows.
Is the api below only way to do it on windows 8.
http://msdn.microsoft.com/en-us/library/windows/desktop/hh404487(v=vs.85).aspx
On Windows 8, there is a "Desktop Duplication API". With this API, it seems that you do not need to develop a driver anymore. Doc is here.
The "Remote Display Drivers" documented here is a bit mysterious...
I need a virtual server for web development, it'll host Apache+Postgres+Ruby+something else.
What's the most effective software to run such a server? (ie with least virtualization overhead)
Is there a way to run Linux as as service?
I use VirtualBox at the moment, but it's inconvenient in some ways, such as it needs an emulator window open which also captures keyboard input when alttabbed into.
(Also, coLinux hangs at boot on my machine, so it's probably not an option)
Check out the features of VMWare Server. It's free, you just have to register.
I've never found VMware to be much of a performance hog unless running 3+ virtual machines.
The latest free server version (VMware Server 2) runs as a service IIRC, so you can set up your dev server to start up and shut down when your PC does, and you can either log on to the VM's console through the web interface, or create a shortcut on your desktop so it's fairly non-obtrusive.
There is a very convenient utility that hides VirtualBox from the foreground completely: vboxctrl. With vboxctrl you can run a Linux server on your Windows machine, make it automatically go to sleep when Windows shuts down or hibernates; then use any SSH client to log in to the server. Or you can use Xming to open graphical windows from the Linux server; I've worked quite a lot of time in GVim open through Xming.
If anyone needs more details, leave a comment, I may write an article about this.
I'm trying to remotely control a Macintosh computer. I know that in the Windows world, you can use Remote Desktop to connect from one Windows computer to another Windows computer. This works relatively well.
I know that you can use a VNC server but this isn't always the most secure or give the best performance. Are there other options available for remotely connecting to a Mac?
In some situations Copilot is a good solution. Not so much for day-to-day admin, but great for remote tech support.
If you need the solution to be cross-platform (ie, controlling an OS X box from Windows) then VNC is the obvious choice. I've had much better luck with the free Vine VNC Server than with Apple's built in one. As for viewers, Chicken of the VNC on OS X or Tight VNC on Windows are good solutions.
As others have said, for security firewall VNC and then use an SSH tunnel. There's lots of ways to do that, and the exact details depends on OS, firewall, network, etc. One method of creating an SSH tunnel for VNC is described here.
If you're trying to connect from one (Leopard) Mac to another, you can use the built-in Screen Sharing functionality; turn the server on from the Sharing System Preferences pane, and either use the network browser (on a LAN) or just open a vnc:// URL.
If you're trying to manage a bunch of Macs, try Apple's Remote Desktop (ARD) software; it's sold in 10- and unlimited-client versions, so if you've got fewer than 5 or so Macs it's probably not worth the money. The client bits for ARD are part of OS X. Screen Sharing and ARD use the same protocol, which includes some Apple-proprietary extensions to VNC which do encryption (either of all data, or of just keystroke/password info) and support adaptive JPEG compression, which gives you decent-enough performance (usable, but nothing like RDP or NX unfortunately).
If you need something cross-platform, check out TeamViewer (which will punch through firewalls and so forth).
Apple's Remote Desktop has AES encryption. Another good way is to just enable SSH in sharing and use shell access to perform tasks without interrupting the user.
http://www.apple.com/remotedesktop/
^That's your best solution.
If you go into the Settings panel, you can find a variety of other remote access options including SSH.
You can use VNC which is built into Tiger.
Yeah, VNC is good, but what about Apple's Remote Desktop?
If you are looking for a free, secure solution: I would recommend using any of a number of VNC servers that are available, blocking the ports that VNC uses to communicate, and then using SSH tunneling to connect. This way, ssh is encrypting everything, and you can still rely on free, open source (?), and cross platform standards for controlling the Desktop remotely.
Citrix, the people behind pc anywhere and the windows remote desktop have a hosted app called "Go to my pc" https://www.gotomypc.com/
I've heard people says it good.
I personally like RHUB's service for remote access and collaboration. It's an appliance that's easy to use and very secure. The device works from behind your firewall (instead of outside of it).
if you need low bandwidth or cross platform there's RDP server for mac that also offers there own iRapp protocol
from their site:
http://www.coderebel.com/2013/11/08/irapp-mac-client-available-download
Lowest supported speed: 512 kbit/s (64 KB/s) for iRAPP protocol
By adjusting the image quality you are able to make iRAPP work on
lower bandwidth connections as recommended above.
iRapp TS (Mac Terminal Server) allows multiple users to connect one
Mac simultaneously