Remote access under windows 2000 pro

[getwired]

Note you can't upgrade from Pro to Server... But yes, you could have the functionality if you reinstalled. Though using VNC, PCAnywhere, or simply upgrading to XP Pro will also solve this.

What I meant earlier, Zillah (sp?) sorry was that all connections to XP Pro are to the console. That is, there is one session, and if you connect via Remote Desktop, the local console will lock. Log back onto the local console, and the RD connection will be disconnected. This is compared to Windows Server 2003, where you can have technically three connections - 1, 2, and the console - via mstsc /console. A true terminal server setup brings more connections, but licensing fun.

[zillah]

Getwired

Could you please what did you mean by VNC?

What I meant earlier, Zillah (sp?) sorry was that all connections to XP Pro are to the console. That is, there is one session, and if you connect via Remote Desktop, the local console will lock. Log back onto the local console, and the RD connection will be disconnected. This is compared to Windows Server 2003, where you can have technically three connections - 1, 2, and the console - via mstsc /console. A true terminal server setup brings more connections, but licensing fun.

Could you please let me know what you did mean by "Zillah(sp?)" ?

Could you kindly explain to me what did yo console? what did you mean by RD?

Thanks

[Shotgun]

VNC = Virtual Networking Client. A client/server combination that makes it possible to view and fully-interact with one computer from any other computer or mobile device anywhere on the Internet. VNC software is cross-platform, allowing remote control between different types of computers. For ultimate simplicity, there is even a Java viewer, so that any desktop can be controlled remotely from within a browser without having to install software. Originally developed by the UK ATT Labs (now an archive no longer mantained by ATT Labs), is still being developed at the RealVNC website. Many "flavors" are still in development in the open source community, some have significant improvements on speed and bandwidth utilization built upon the original VNC protocol. The VNC protocol (and clients) found a "niche" in the IT world that at the time it was developed was in an extreme need of an efficient, fast, easy to deploy solution to remote viewing/administration. The best thing about VNC is that it is cross platform. You can even view/control a server from a PocketPC or Palm PDA!

I think he meant [by Zillah(sp?)] is that he wrote your nick and did not know if the spelling was correct.

By console, Getwired means the currently logged session on the remote PC.

RD = Remote Desktop or Remote Desktop Connection.

RDP = Remote Desktop Protocol

hope that helps.

[hammy_chen]

FYI It's available in Windows 2000 Server running terminal services.

Hi, why not try the build-in NetMeeting?

You can set the NetMeeting to auto accept dial-in, make it more like a server to accept your multi-session remote control over that win2k computer.

Of course you can specify a password for every connection.

[kevin.parry]

You CAN connect to a windows 2000 pro box if you copy and paste the mstsc.exe and the mstscax.dll from an XP machine into the System32 folder of the 2000 pro machine.

[zillah]

Thanks shotgun for your explaination

[zillah]

You CAN connect to a windows 2000 pro box if you copy and paste the mstsc.exe and the mstscax.dll from an XP machine into the System32 folder of the 2000 pro machine.

That is very intersting,,,Have you tried that ? Do you if you copied these files to windows 2000 Pro,,,we can connect remotly from any machine to windows 2000 pro Box?

thanks

[getwired]

That will allow you to connect FROM. Those two binaries are only for the Terminal Services Client - they don't affect the ability to connect to a 2000 Pro machine at all. The only way to connect to the GUI of 2000 Pro remotely is using third party software.