mnkeybsness:
No, Microsoft RDC only works with the following:
* Windows XP Professional
* Windows .NET Standard Server
* Windows .NET Enterprise Server
* Windows 2000 Server
* Windows 2000 Advanced Server
* Windows 2000 Datacenter Server
* Windows NT Server 4.0, Terminal Server Edition
So, basically all their higher end servers that normally offer Terminal Services, plus XP Pro (where the "remote desktop" troubleshooting feature is essentially a single user Terminal Server). If someone else is using RDC to connect to an XP Pro box, and you force a connect, you kick the other person off.
Only tried it with XP Pro so far, where it works quite nicely, although I've found the client to be rather crash-prone (but at least when you reconnect your session is still going) Not 100% sure how much of the crashing is the client or due to my wireless network dropping data and RDC bailing on me because iof this.
rojazz:
Have to say that RDC is much slicker to use than VNC although it's obviously not got the cross-platform flexibility, and I've no idea how well it tunnels over ssh, for example.
VNC was the first solution I tried for using my XP box from the Mac. I'd favorably compare RDC over my 802.11 wireless network with VNC over 100BaseT full duplex, but without VNC's screen-redraw issues. Note that since I used VNC regularly in the past over DSL to get to my work Windows and Linux boxes, I've no idea whether it's the case that the Mac VNC client is buggy, or if the Windows one was exceptionally good.
Both RDC and VNC crash reasonably often, but with RDC it's usually just a matter of restarting the client (which is good because the XP box is in another room and I'm hobbling around here on crutches and tend to fall over), whereas with VNC it usually required directly logging into the XP box to restart the VNC server.
Nobody's about to start playing Quake 3remotely using either
I'd consider both to be usable for short remote admin tasks. I'm not yet sure whether I consider RDC to be usable enough for my needs (which is basically doing .NET development without having the PC roaring away under my desk) - I long ago ruled out VNC for this, it just wouldn't stay up long enough. Maybe once I'm healthy and can get the Mac wired into the same switch as the PC I'll see if there's a reliability difference.
I think most people were caught completely off guard by this - suddenly, out of nowhere, Microsoft releases a useful, needed piece of software that *doesn't* compel the user to switch to their platform to use it, and gives it away for free.
