Sponsored Content
Full Discussion: Linux terminal server?
Top Forums UNIX for Dummies Questions & Answers Linux terminal server? Post 302567607 by lupin..the..3rd on Monday 24th of October 2011 12:55:21 PM
Old 10-24-2011
Linux terminal server?

Hello everyone, I have an interesting project I'd like to implement on a Linux server here at work. Essentially, I'd like to replace a handful of Windows servers with a single Linux server. The only task these Windows servers perform, is provide remote desktops via RDP protocol that people connect to. That it!

So Windows apparently cannot handle more than 2 users logged in at once via RDP. So the company in their infinite wisdom simply bought more Windows servers. So we've got 10 of them in total, providing 20 possible RDP remote desktop sessions.

The reason we need these remote GUI desktops, is that our network connection between our office, and the data center, is flaky. It disconnects and goes down and has errors all the time. So we cannot run remote applications on our servers reliably, because the network will drop and we'll lose what we were working on. So instead, we remote desktop to a Windows server that's in the datacenter, and run our programs from there. That way, if the network drops, we simply have to re-establish our remote desktop to the Windows server, and voila, all our programs are still there running and we pick up where we left off. It actually works well.... except for the fact that it takes 10 servers to provide 20 remote desktop sessions.

Still with me? Ok, good. Smilie I want to replace these 10 Windows servers with a single Linux server. I know I can ssh to a Linux box and do X11 forwarding and have a program run remotely but display locally...... but that's not what I want to do, since it will fail when the connection drops. I need the same functionality that Windows provides, whereby 20 users can each connect to their own unique gui sessions, and if the network connection drops, they can simply reconnect to their remote gui desktop and be right where they left off.

Any ideas on how to accomplish this? The machines they are connecting from are all Windows desktop PC's. I looked at LTSP but that's more of a thin client thing, where the clients boot from the network. I can't use that. I need to connect to the remote Linux gui sessions from some kind of software client on Windows desktop pc's.

I've searched but didn't find any easy answers, so any advice or guidance is much appreciated - you are helping to eliminate 10 Windows servers, and everyone here likes that idea, right?? Smilie
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Annex Terminal Server

Anyone set up Annex Terminal Server on Solaris 8 I'm having issues getting the Annex box to upload the boot file. Anyone know of easy to follow procs anywhere, looking a docs.sun.com This is turning into the thorn in my side after doing a major transition of disks frames, backup tools and... (2 Replies)
Discussion started by: kie
2 Replies

2. Solaris

Sun Server Hyper Terminal

Anyone know how to connect to a sun server using serial cable my client PC is also a Sun !!! I have the cable , just do not know how to start a terminal session in Sun . (1 Reply)
Discussion started by: civic2005
1 Replies

3. Solaris

Booting Up Servers from the Terminal Server.

All, I have a problem with booting up of servers. I am involved in application programming(Perl/Shell), but don't have much hardware knowledge about the Sun Solaris Server's we use. Our Development Servers are located at a remote place from the Development Centre. Every time there is a Power... (1 Reply)
Discussion started by: rahulrathod
1 Replies

4. UNIX for Dummies Questions & Answers

mac 10.4>terminal>linux remote server>ssh login accepted>session closed-why?

mac 10.4>terminal>linux remote server>ssh login accepted>session closed-why? AHHHH!! I have been connecting to the server with the line: ssh userid@website.com The remote server accepts my password; logs me in with ssh; posts a lovely welcome message AND closes the session. Is this a "term... (0 Replies)
Discussion started by: xprankard
0 Replies

5. Solaris

How do I get basic server specs from terminal?

Hi there. Anyone know how to get CPU speed, RAM size etc (basic specs) from a SUN server running solaris, from the unix terminal? I'm sure there must be a command for this but ... I haven't been able to find it so far.. :o Cheers. (8 Replies)
Discussion started by: kenny123m
8 Replies

6. Cybersecurity

ssh to terminal server

Hi. We are currently upgrading the terminal server in our system (Solaris 8). Previously, we used telnet to reach the terminal server from our maintenance workstation. Now, the new one supports SSH, so we're finally moving off telnet. When logging into the terminal server via telnet, a user was... (0 Replies)
Discussion started by: jalburger
0 Replies

7. Cybersecurity

ssh to terminal server

Hi. We are currently upgrading the terminal server in our system (Solaris 8). Previously, we used telnet to reach the terminal server from our maintenance workstation. Now, the new one supports SSH, so we're finally moving off telnet. When logging into the terminal server via telnet, a user was... (3 Replies)
Discussion started by: jalburger
3 Replies

8. Solaris

how to connect a PC terminal to UNIX server?

Hi everyone, I am new to Unix and looking for help here. we have four terminals connected to our solaris server (x86 based). the server got an interface card which provide serial port and video port for all chained terminals in a serial way. All these clients have no IP and they all display... (3 Replies)
Discussion started by: Cheong
3 Replies

9. Debian

How to exit debian server terminal?

I have an situation that are quite strange to me. I am not able to exit the server terminal and enter back into my home computer terminal by the command exit like I used to be able to exit the server terminal with before. I end up into my root shell again without even typing the root password like... (6 Replies)
Discussion started by: Jonathan Sander
6 Replies

10. Windows & DOS: Issues & Discussions

Start X Server without starting a terminal

when I run C:\cygwin\bin\run C:\cygwin\bin\startxwin.exe it fires up a terminal by default. Can I eliminate that terminal and start the x server as a service silently and sits in my status bar just there? Thanks Jack (0 Replies)
Discussion started by: lucky7456969
0 Replies
rdesktop(1)						      General Commands Manual						       rdesktop(1)

NAME
rdesktop - Remote Desktop Protocol client SYNOPSIS
rdesktop [options] server[:port] DESCRIPTION
rdesktop is a client for Remote Desktop Protocol (RDP), used in a number of Microsoft products including Windows NT Terminal Server, Win- dows 2000 Server, Windows XP and Windows 2003 Server. OPTIONS
-u <username> Username for authentication on the server. -d <domain> Domain for authentication. -s <shell> Startup shell for the user - starts a specific application instead of Explorer. -c <directory> The initial working directory for the user. Often used in combination with -s to set up a fixed login environment. -p <password> The password to authenticate with. Note that this may have no effect if "Always prompt for password" is enabled on the server. WARNING: if you specify a password on the command line it may be visible to other users when they use tools like ps. Use -p - to make rdesktop request a password at startup (from standard input). -n <hostname> Client hostname. Normally rdesktop automatically obtains the hostname of the client. -k <keyboard-map> Keyboard layout to emulate. This requires a corresponding keymap file to be installed. The standard keymaps provided with rdesktop follow the RFC1766 naming scheme: a language code followed by a country code if necessary - e.g. en-us, en-gb, de, fr, sv, etc. The default keyboard map depends on the current locale (LC_* and LANG environment variables). If the current locale is unknown, the default keyboard map is en-us (a US English keyboard). The keyboard maps are file names, which means that they are case sensitive. The standard keymaps are all in lowercase. The keyboard maps are searched relative to the directories $HOME/.rdesktop/keymaps, KEYMAP_PATH (specified at build time), and $CWD/keymaps, in this order. The keyboard-map argument can also be an absolute filename. The special value `none' can be used instead of a keyboard map. In this case, rdesktop will guess the scancodes from the X11 event key codes using an internal mapping method. This method only supports the basic alphanumeric keys and may not work properly on all platforms so its use is discouraged. -g <geometry> Desktop geometry (WxH). If geometry is the special word "workarea", the geometry will be fetched from the extended window manager hints property _NET_WORKAREA, from the root window. The geometry can also be specified as a percentage of the whole screen, e.g. "-g 80%". -f Enable fullscreen mode. This overrides the window manager and causes the rdesktop window to fully cover the current screen. Fullscreen mode can be toggled at any time using Ctrl-Alt-Enter. -b Force the server to send screen updates as bitmaps rather than using higher-level drawing operations. -A Enable SeamlessRDP. In this mode, rdesktop creates a X11 window for each window on the server side. This mode requires the Seamless- RDP server side component, which is available from http://www.cendio.com/seamlessrdp/. When using this option, you should specify a startup shell which launches the desired application through SeamlessRDP. Example: rdesktop -A -s 'seamlessrdpshell notepad'. -B Use the BackingStore of the Xserver instead of the integrated one in rdesktop. -e Disable encryption. This option is only needed (and will only work) if you have a French version of NT TSE. -E Disable encryption from client to server. This sends an encrypted login packet, but everything after this is unencrypted (including interactive logins). -m Do not send mouse motion events. This saves bandwidth, although some Windows applications may rely on receiving mouse motion. -C Use private colourmap. This will improve colour accuracy on an 8-bit display, but rdesktop will appear in false colour when not focused. -D Hide window manager decorations, by using MWM hints. -K Do not override window manager key bindings. By default rdesktop attempts to grab all keyboard input when it is in focus. -S <button size> Enable single application mode. This option can be used when running a single, maximized application (via -s). When the minimize button of the windows application is pressed, the rdesktop window is minimized instead of the remote application. The maxi- mize/restore button is disabled. For this to work, you must specify the correct button size, in pixels. The special word "standard" means 18 pixels. -T <title> Sets the window title. The title must be specified using an UTF-8 string. -N Enable numlock syncronization between the Xserver and the remote RDP session. This is useful with applications that looks at the numlock state, but might cause problems with some Xservers like Xvnc. -X <windowid> Embed rdesktop-window in another window. The windowid is expected to be decimal or hexadecimal (prefixed by 0x). -a <bpp> Sets the colour depth for the connection (8, 15, 16 or 24). More than 8 bpp are only supported when connecting to Windows XP (up to 16 bpp) or newer. Note that the colour depth may also be limited by the server configuration. The default value is the depth of the root window. -z Enable compression of the RDP datastream. -x <experience> Changes default bandwidth performance behaviour for RDP5. By default only theming is enabled, and all other options are disabled (corresponding to modem (56 Kbps)). Setting experience to b[roadband] enables menu animations and full window dragging. Setting experience to l[an] will also enable the desktop wallpaper. Setting experience to m[odem] disables all (including themes). Experi- ence can also be a hexidecimal number containing the flags. -P Enable caching of bitmaps to disk (persistent bitmap caching). This generally improves performance (especially on low bandwidth con- nections) and reduces network traffic at the cost of slightly longer startup and some disk space. (10MB for 8-bit colour, 20MB for 15/16-bit colour and 30MB for 24-bit colour sessions) -r <device> Enable redirection of the specified device on the client, such that it appears on the server. Note that the allowed redirections may be restricted by the server configuration. Following devices are currently supported: -r comport:<comport>=<device>,... Redirects serial devices on your client to the server. Note that if you need to change any settings on the serial device(s), do so with an appropriate tool before starting rdesktop. In most OSes you would use stty. Bidirectional/Read support requires Windows XP or newer. In Windows 2000 it will create a port, but it's not seamless, most shell programs will not work with it. -r disk:<sharename>=<path>,... Redirects a path to the share \tsclient<sharename> on the server (requires Windows XP or newer). The share name is limited to 8 characters. -r lptport:<lptport>=<device>,... Redirects parallel devices on your client to the server. Bidirectional/Read support requires Windows XP or newer. In Windows 2000 it will create a port, but it's not seamless, most shell programs will not work with it. -r printer:<printername>[=<driver>],... Redirects a printer queue on the client to the server. The <printername> is the name of the queue in your local system. <driver> defaults to a simple PS-driver unless you specify one. Keep in mind that you need a 100% match in the server environment, or the driver will fail. The first printer on the command line will be set as your default printer. -r sound:[local|off|remote] Redirects sound generated on the server to the client. "remote" only has any effect when you connect to the console with the -0 option. (Requires Windows XP or newer). -r lspci Activates the lspci channel, which allows the server to enumerate the clients PCI devices. See the file lspci-channel.txt in the documentation for more information. -r scard[:<Scard Name>=<Alias Name>[;<Vendor Name>][,...]] Enables redirection of one or more smart-cards. You can provide static name binding between linux and windows. To do this you can use optional parameters as described: <Scard Name> - device name in Linux/Unix enviroment, <Alias Name> - device name shown in Win- dows enviroment <Vendor Name> - optional device vendor name. For list of examples run rdesktop without parameters. -0 Attach to the console of the server (requires Windows Server 2003 or newer). -4 Use RDP version 4. -5 Use RDP version 5 (default). LINKS
Main website of rdesktop http://www.rdesktop.org/ November 2005 rdesktop(1)
All times are GMT -4. The time now is 07:20 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy