Home > Windows > Administering Windows Server 2003 Remotely Administering Windows Server 2003 Remotely Eugenia Loli 2004-08-02 Windows 7 Comments This chapter covers the wealth of tools and options available to administrators in Windows Server 2003, including many enhancements to tools that existed in previous versions of the system. About The Author Eugenia Loli Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker. Follow me on Twitter @EugeniaLoli 7 Comments 2004-08-03 12:52 am Anonymous Remore desktop is one of the few reasons to go with XP pro rather than Home. I threw XP pro on my dads PC for this reason. The only thing I don’t like about it is that I have not yet figured out how to do file xfers with it, where on UNIX I can just scp the file through ssh. I think I read somewhere that the box you remote into should mount as a network drive but I have not seen this in practice, any takers? 2004-08-03 2:07 am Anonymous Remore desktop is one of the few reasons to go with XP pro rather than Home. XP Home probably has that “remote assistance” feature which is basically the same thing. I think I read somewhere that the box you remote into should mount as a network drive but I have not seen this in practice, any takers? In the RDP client, on the “Options” tab, check “Disk drives”. That will map the client’s local drives. 2004-08-03 5:17 am Anonymous “XP Home probably has that “remote assistance” feature which is basically the same thing.” It does but you can only receive assistance, not initiate it. 2004-08-03 7:45 am Anonymous Its not the same thing. Remote Desktop is a single interactive logon. If you use it remotely you log the person on the console (at the PC) off. Its like a 1 license terminal server. Remote assistance is like VNC in that you can view or share the logged on users desktop. Both use the terminal services RDP technology but they operate in different ways. 2004-08-03 1:46 pm Anonymous xp home has remote assistance and can initiate the request for assistance, and a remote user comes in and takes over. a remote user cannot dial in and take control without the initiation coming from the xp home machine. xp home can run the remote desktop client to control an xp pro machine and a windows server 2003 machine http://www.microsoft.com/windowsxp/downloads/tools/rdclientdl.mspx allows Windows 95, Windows 98 and 98 Second Edition, Windows Me, Windows NT 4.0, or Windows 2000 to control a xp pro machine. http://www.microsoft.com/windowsxp/downloads/tools/rdwebconn.mspx allows you to control an xp pro machine via a web browser from the internet. http://www.microsoft.com/mac/downloads.aspx?pid=download&location=/… allows mac os x to remotely control xp pro, server 2003, server 2000, and nt 4 terminal services. http://www.microsoft.com/downloads/details.aspx?familyid=a8255ffc-4… remote client that allows Windows 2000, Windows 2000 Service Pack 2, Windows 2000 Service Pack 3, Windows 95, Windows 98, Windows 98 Second Edition, Windows ME, Windows NT, Windows Server 2003, Windows XP, Windows XP Media Center Edition to remotely control a windows 2003 server. 2004-08-03 1:48 pm Anonymous ms pocketpc allows you to control a server via terminal services as well. not sure what options exist for ms phone os or any of the palm oses. 2004-08-03 3:21 pm Anonymous Nice to see articles that follow the directions. However, directions aren’t always good. Repeat after me: 1. Install SSH server on winxx server 2. Lock down all ports except SSH on server 3. Create jailed remote SSH user account 4. Use PuTTY or similar to SSH into server 5. Port forward remote desktop 6. Remote desktop into localhost Given Microsoft’s security track record ‘turn on remote desktop/terminal services security for a safe connection’ type articles just can’t be trusted.