

It is intended to work, though, and over time the bugs will probably get worked out. We have had numerous problems with this in the past, specifically, we have had trouble installing SQL server remotely this way, even though we were using remote administration mode. The identity you get when you use Terminal Services to log on as administrator isn’t quite the same as if you log on from the console. There are some drawbacks, though, in that installing certain software can fail because Windows 2000 isn’t *really* multi-user. Administering the server through Terminal Services is quite a bit smoother than VNC. It will take a reboot, and you will need your Windows 2000 CD. Here is a screenshot that shows how to configure Terminal Services. You can do this: start->programs->administrative tools->configure your server. While you are compiling and installing rdesktop, make sure Terminal Services is configured on your server. Sheeesh… 🙂 We grabbed version 1.2.0 of rdesktop from here. This is a lot easier than running the Terminal Services client from Vmware like we did in this article. Rdesktop allows you to access Terminal Services natively from GNU/Linux. The Terminal Server system may be accessed from a local or wide area network or via the Internet.We usually use VNC to administer our Windows servers from our GNU/Linux workstations.

That said, dial-up modem support under Linux is a joke at best therefore, for most users the only options are wired Ethernet or wireless connectivity.

A simple 56K modem connection would be sufficient. Any sort of network or Internet connection for both the server and client.Re-compiling the SRPM and SeamlessRDP components are necessary for 64-bit machines with 64-bit operating systems. Although this software is capable of working on other distributions or Unix-like operating systems with a simple re-compile procedure, this particular package is designed to work with 32-bit versions of Fedora and Windows. At least one computer with Fedora Linux installed.Note: Windows Server 2008 terminal servers are not yet supported. A computer with a version of Windows that encompasses the server component of Terminal Services-Windows NT 4.0, Windows 2000, Windows XP Professional, Windows Server 2003, Windows Vista Business, Ultimate, or Enterprise.I've made RPMs for a patched CVS-built rdesktop, included Microsoft's Elevate Power Toy for Vista, Fontis IT's enhanced SeamlessRDP server, and a small tray application and five page Readme wrote by me.

It provides a seamless terminal solution for Fedora Linux users with capable Windows machines. I've packaged together a set of software components. Heres an early Christmas gift to fellow niners with Windows and Linux boxes, who are looking for an easy way to access all their Windows applications and remote files when Wine-type solutions fall flat.
