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

Microsoft Releases Remote Desktop Connection Client 2

digitalbiker said:
Try entering the ip address of the Windows Vista Computer instead of the computer name. There may be a problem with translating the name into an ip address.

Also you say the two computers are on the same local network but could you supply more details. I mean are they both contacting a wireless hub to get their ip address or are they both plugged into a wired ethernet hub? Is one wired and one wireless, etc? Do the laptops have fixed ip addresses?

It is possible that the two computers are on the same network but are being supplied ip address within a different range.
Click to expand...

Yes they are connected to the same Netgear router which is wireless. Both computers are wireless.

Also, to get the ip, do I just type ipconfig in the cmd and then get the default gateway? Or is it something else. The ipconfig thing didn't work.

Also, I have filesharing on and SMB on in my MBP, and filesharing is on in the XPS laptop. But I still can't see it in my "Shared" de vices in the Finder. Maybe that is the whole problem?
 
I was asking a friend to try this out, he has Vista, i have OS X. Anyway he was saying it's a big pain to use that program on his end. He has to mess with his firewall and router etc. He uses logmein.com so i tried that and connected to his PC through the web browser, works great, can go either way.

And poops. :apple:
 
As far as MS, RDC and other recently updated apps go, it is nice to see more frequent updates. I myself prefer 'release early, release often'.
 
Watabou said:
Yes they are connected to the same Netgear router which is wireless. Both computers are wireless.

Also, to get the ip, do I just type ipcondig in the cmd and then get the default gateway? Or is it something else. The ipconfig thing didn't work.

Also, I have filesharing on and SMB on in my MBP, and filesharing is on in the XPS laptop. But I still can't see it in my "Shared" de vices in the Finder. Maybe that is the whole problem?
Click to expand...

In windows the command is winipconfig. Type it in the command console and it should report the ip address and mac address of the current machine.

Also I forgot to ask you what version of Vista you are using because RDC does not work in Vista Home.

Sorry, but I forgot this was Vista the correct command is just plain "ipconfig" not winipcfg.
 
digitalbiker said:
In windows the command is winipconfig. Type it in the command console and it should report the ip address and mac address of the current machine.

Also I forgot to ask you what version of Vista you are using because RDC does not work in Vista Home.
Click to expand...

Well that is the problem then. It runs Vista Home Premium. Oh well. :( (Also, I typed in ipconfig not "ipcondig" lol, my bad.)

Thanks for helping me anyways :)
 
Sky Blue said:
Was using the beta for a looooonnnnnggg time. Eventually gave up on it and i just use CoRD now, much better imho.

http://cord.sourceforge.net/
Click to expand...

I don't say this very often, but OMFG!

How is it I've struggled with RDC this long and didn't know about CoRD? I love having the little "console session" checkbox. Beautiful. Beautiful. Beautiful. :D
 
MacRumors said:
The final version is available for download now and allows you to remotely connect to Windows-based PCs to access Windows-based files, applications, devices, and networks from your Mac.
Click to expand...

idk but i might be the only one who found that funny due to its redundantness lol.. oh well im weird so i guess it doesnt matter
 
Well, there's been TeamViewer for this...
Anyway, seems like the Microsoft Mac Unit has been working more and more those days, that's good, we MAY have a proper version of the Microsoft Messenger someday... Hopefully.
 
Sky Blue said:
Was using the beta for a looooonnnnnggg time. Eventually gave up on it and i just use CoRD now, much better imho.

http://cord.sourceforge.net/
Click to expand...

CoRD fails completely on our W2k3 terminal server, I suspect it can't deal with the latest security protocols, whereas the Microsoft client can. Therefore, if you have a locked-down server, you need this client, at least until CoRD is updated.

Note: The Microsoft betas also couldn't handle the new protocols.. was a serious pain for us.
 
Yay!
I've been using the beta for forever. I can't believe this took so long to finalize. But I can't complain:
* It's free
* The beta's been working for me, trouble-free
 
Brother Michael said:
I used to use the RDC program, but honestly I prefer VNC to RDC.

For the Windows Machine (Host): http://www.realvnc.com/
For the Mac (Client): http://sourceforge.net/projects/cotvnc/

This way, you can stay logged into your windows machine and use it remotely as well.

This is especially awesome, if you are helping someone with their computer, you can share the mouse.
Click to expand...

The basic difference in VNC vs RDC is that VNC connects you to the "console" session, RDC can create an alternative session which is very nice because you don't disrupt the operation of the computer. This is only officially supported by Windows Server, but can also be enabled on XP SP2. Especially useful if like me you have a computer dedicated as an HTPC and want to do some tinkering without interrupting the TV.


BTW, CoRD rocks hardcore.
 
CoRD is good, but I've got an issue when using :apple:-tab it activates the start menu in the windows desktop. Very annoying. I also use RDC MENU, which lets you share your hard drive with the windows machine and navigate to it through the windows network folder. I don't know if CoRD can do this but I haven't looked too hard.
 
LogMeIn

I am using LogMeIn app which is free and perfect. Try this on secure.logmein.com and tell me what you think. :):):)
 
This RDC has an issue where it's utterly impossible to type the '#' key on a UK keyboard, making it unusable for any kind of programming work. This bug was reported by multiple people during beta3 but they never fixed it. Damned americans never testing outside the US.

CoRD non-beta doesn't support Ctrl+Tab (WTF???).. which is a complete showstopper. Cord beta doesn't support full screen mode (the button in fact resizes the window to a tiny window), meaning it scales everything and gives dreadful picture quality... again a complete showstopper since you can't read the text on the screen. Also.. no spaces support, so having two machines open at once is completely impractical.

RDC 1.0 FTW! Takes everything you throw at it, solid as a rock. With RdcLauncher currently the best available. Failing that, 2.0 beta 1 which only has the issue of the nag screen, otherwise works perfectly.
 
i've never heard of this before, and was about t say it was a great idea.

but then i read a earlier post saying the windows pc had to install something too. kinda makes it abit of pain to quickly get hold of some files, IMO tho.
 
Does anyone know if this will allow Mac users to assist friends with Windows PCs using the "remote desktop assistance" feature? (Start-->Help, I think in XP).
 
Yay! Hopefully this means they fixed the dreaded inverted caps lock problem!

When I was using the beta to connect to my work laptop (I usually plug it in and throw it under the bed and TS into it when I work from home) there was something that would cause the caps lock key to invert. Caps lock had to be on to type normally on the remote machine, and off to type normally on my MBP. It was strange. I got used to it, though. We'll see if this is fixed tomorrow, I'll be WFH to avoid the traffic of Red White and Boom.
 
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