Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Microsoft Remote Desktop Connection Client 2.0 (Beta)

petieg said:
While it indeed seems to be a good start for a UB RDC client, there is no Console support, so no session 0 on a Win2k3 server. They should also have included some 16x9 'type' resolutions instead of the standard 4x3. We'll see about printer support -- this has always been an issue, even for Windoze worlds.
Click to expand...

In the connection window, append "/console" to the server name.

IE if you are connecting to 192.168.10.10 put "192.168.10.10 /console" in the connection window. Obviously, you can use a FQDN or a hostname as well.

IJ Reilly said:
I'd like an answer to this question too. Is there any way to run Terminal Services or Remote Desktop Services in XP Home?
Click to expand...

Remote Desktop is a feature available exclusively to XP Pro. It is not available to XP Home... you're stuck using VNC or www.gotomypc.com or www.logmein.com
 
mkrishnan said:
As long as the firewalls / NAT permit it, yes. I RDC over the public internet all the time.
Click to expand...

The question was: "Does RDC only work for computers on the same network?"


No, RDC does not only work on the same subnet. So long as you can access the remote machine on the allowed ports, traversing firewalls, public nets, etc should pose no problem aside from latency.
 
mkrishnan said:
Does that mean anything interesting for this type of app in terms of functionality? Or is it just a peek at things to come? Cocoa Office? :) :)
Click to expand...
A rewrite of RDC is one thing, but a rewrite of office is totally another.
 
While this would work, dont you think its a little messy? Also, some people don't like to mess with their registry. I know on D-Link routers you can open 23389, for example, on the external interface to forward to 3389 in a certain internal ip address.
I think this solution would be simpler...

AidenShaw said:
If you have multiple Windows machines behind the same router, you can run the 2nd/3rd/4th... machines on alternate ports.

For example, you could run the 2nd machine on 23389. You'd need to go to the registry and edit:

HKLM\SYSTEM\CurrentControlSet\Control\TerminalServer\Winstations\RDP-Tcp\PortNumber to 23389 (decimal)

and reboot. Set the router to pass 23389 to the ip:23389 of the 2nd machine.

From the client, open ip:23389 to start the window.
Click to expand...
 
Clive At Five said:
Cross platform drag-n-drop?
Copy/Paste?
What's the response time?

Details, please.

-Clive
Click to expand...

Copy/Paste already works in the current version. Except for binary copy pastes like files and screenshots. Textual copy paste works...

balamw said:
For anyone who has already downloaded it.

How does it compare with CoRD? http://cord.sourceforge.net/

B
Click to expand...

Thanks for this post; I did not yet know about CoRD :) I'm definately give that a shot :)
 
mkrishnan said:
As long as the firewalls / NAT permit it, yes. I RDC over the public internet all the time.
Click to expand...

I often use SSH tunnels to get to a machine; you can -for example- easily forward your machine at your home network to your local machine if you have a Unix box as gateway.

For example:
-your local machine --> the MAC (or other *nix machine) you are working on
-unix.home.com --> your home *nix gateway (a Mac, Linux or other unix flavored machine)
-192.168.1.1 --> your windows machine on the local home network

On your local machine you can then execute the following command in your terminal to start a SSH tunnel which forwards the remote desktop connection from your home windows machine to your local machine:

Code: 
ssh -L 3389:192.168.1.1:3389 -g -l [I]your_user_name[/I] unix.home.com

(by adding the -g option you allow remote users to connect to the forwarded remote desktop port on your local machine as well)

After login you just get a regular SSH shell but now with a portfoward for port 3389 (=RDP) to the machine on your home network. Now you can connect with your remote desktop client to localhost and get the desktop of your home windows machine :) It's that easy... Note that you can create multiple forwards at one as well. Also reverse tunnels are possible using the -R option. I usually start a top -d 5 command to keep the connection open; however this of course is not really necessary :)

It's even better to use remote desktop like this as the connection will be encrypted because you use a SSH tunnel. Directly connecting to Remote Desktop over the internet could allow sniffing or 'man in the middle' attacks. Personally I think adding a publically available portforward to your home router (as some people have mentioned previously) is a security hole in your network; I think the SSH tunnel (or using a VPN) approach is the proper way of doing this.

Note: make sure though that sshd.conf on unix.home.com allows portforwards (AllowTcpForwarding yes) and that you -of course- allow remote users to connect your windows machine using remote desktop :)

You can use the same process for forwarding whatever (TCP!) ports you like :) Perhaps VNC? ;) Or SMB :)
 
steviem said:
While this would work, dont you think its a little messy? Also, some people don't like to mess with their registry. I know on D-Link routers you can open 23389, for example, on the external interface to forward to 3389 in a certain internal ip address.
I think this solution would be simpler...
Click to expand...

Yes - I should have said something like "if your router can't forward to a different port...."

You'll still need to specify the port number on the connect, for example

> mstsc /console /v:216.109.112.135:23389 /width=1280 /height=1024


Some people recommend using an alternate port (other than 3389) on the external side for a bit of extra security. Botnets and the like that do automated scans for RDP vulnerabilities will be hitting port 3389 - not scanning the entire port range.

If a dedicated crook (like the NSA) is after you, though, they'll see signature RDP traffic through the alternate port and get you.
 
4np said:
It's even better to use remote desktop like this as the connection will be encrypted because you use a SSH tunnel. Directly connecting to Remote Desktop over the internet could allow sniffing or 'man in the middle' attacks.
Click to expand...

Actually, RDP is encrypted with most current clients - but it is vulnerable to man-in-the-middle attacks. Vista <-> Vista or Vista <-> Win2k8 RDP sessions do block the man-in-the-middle attacks.

Some very good infos about some simple settings to help secure RDP are at:

http://www.mobydisk.com/techres/securing_remote_desktop.html


4np said:
Personally I think adding a publically available portforward to your home router (as some people have mentioned previously) is a security hole in your network.
Click to expand...

But, you're opening the well-known port 22 for the SSH connection, so it can't be all bad.... ;)
 
Jasonbot said:
How does this compare to Apple's Remote Desktop?
Click to expand...

MS RDC is for accessing individual Windows boxes.

ARD allows access to Windows based boxes running VNC, and in addition allows users to remotely control or monitor other computers over a network, deploy software installations, get monitoring reports, reboot machines or groups of machines, and so on. You can even control multiple computers at once, really easily.

http://www.apple.com/remotedesktop/

Have a look at the website ;)
 
bigandy said:
MS RDC is for accessing individual Windows boxes.

ARD allows access to Windows based boxes running VNC, and in addition allows users to remotely control or monitor other computers over a network, deploy software installations, get monitoring reports, reboot machines or groups of machines, and so on. You can even control multiple computers at once, really easily.

http://www.apple.com/remotedesktop/

Have a look at the website ;)
Click to expand...

Yeah, I have Apple Remote Desktop but I was jsut wondering in terms of accessing windows boxes what the difference is. I should be more specific next time.

Do I need to install a VNC client on my windows PC's to get ARD to access them? I've been having problems.
 
WOW. Way faster. Like it.

Now I just wish they would add video support so I can watch tv through windows media center.
 
Need more

This seems like a great update but I need something that's not only going to go Mac to PC, but PC to Mac.

Does such a program exist that allows you to control Mac OSX from a PC?

Reading through this update it doesnt look like this has been done yet.
 
I haven't noticed any difference between 2.0 beta and the previous version 1.0.3. It's probably using a smaller memory footprint, since it's not running under Rosetta, but speed seems the same. Performance bottleneck is likely the work VPN.
 
Yateball said:
Reading through this update it doesnt look like this has been done yet.
Click to expand...

Why would that be MS's responsibility? Apple doesn't support the Microsoft RDC protocol in OS X. So there's no way for MS to magically make Apple computers able to be RDC'd to from Windows computers.

Apple *does* support the VNC protocol on all versions (wkstation and server) of OS X. You go to system preferences and allow other people to access the Mac remotely (I think it's the Network pane -> Sharing tab).

You will then be able to log into the Mac using a VNC client on Windows (e.g. this one).

Since the VNC and the RDC are both very small programs that use substantially different protocols, what is the benefit of merging them into one program?
 
Dont like that it needs in installer...

Doesn't want to work with any of our Win2003 servers, it connects, shows login window, but then credentials dont get accepted... might be keyboard mapping or something.... :mad:
 
Lollypop said:
Dont like that it needs in installer...

Doesn't want to work with any of our Win2003 servers, it connects, shows login window, but then credentials dont get accepted... might be keyboard mapping or something.... :mad:
Click to expand...
If Win2003 server support is possible. Please link me to a tutorial or something. I've been super pissed at my new job with not being able to remote in from home. I came across a link a month ago with a way to setup 2003 to allow OSX RDCs. I've since lost the link and have only found a blurb about it from Experts-exchange. It states to do this to your 2003 server's Active Directory...

-> Security Settings -> local policies -> security options:
Domain member: Digitally encrypt or sign secure channel data (always): have put in on "Not Defined" instead off "enabled"
Microsoft Network server: Digitally sign communications (always): have put in on "Not Defined" instead off "enabled"
Microsoft Network server: Digitally sign communications (if client agrees): have put in on "Not Defined" instead off "enabled"
Microsoft Network client: Digitally sign communications (always): have put in on "disabled" instead off "Not Defined"
Click to expand...

I haven't convinced my boss to try this yet. So, I'm hoping there's something I can do for my OSX computers that will work with it... ****!
 
Memory Leak

Has anyone noticed that it has a memory leak? I had it running for about 8 hours and it was using up over 1Gb of RAM.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back