Skip to Content

Remote Desktop Madness

What happens when you make your Remote Desktop point to your own machine? Something like this, apparently. TUAW reader Chris Mills, who decided to give into his curiosity and give this a try, snapped this screenshot after opening a remote desktop connection to the same machine he was working on. This caused his system to more or less lock up but it made a nifty picture and offered a tesseract-ish view of his desktop. We at TUAW appreciate this kind of reader-generated ingenuity particularly because it allows us to enjoy the results without all the bother of messing with our own Macs.



Categories

Humor Hacks

What happens when you make your Remote Desktop point to your own machine? Something like this, apparently. TUAW reader Chris Mills, who...
 

Add a Comment

*0 / 3000 Character Maximum

23 Comments

Filter by:
sjmills

Heh, just yesterday I was looking for newer VNC clients and was trying them with Tiger's built-in VNC server. I didn't go that nuts, but I did get around to controlling the G5 in the basement from the G5 in the den from the Mac Pro at my desk. And it wasn't even that slow. :)

February 02 2007 at 4:37 PM Report abuse rate up rate down Reply
Steven Fisher

You can't to this easily on Windows XP with its Remote Desktop. It tries to be smart about it. However, I once managed to port forward with SSH and connect my PC to itself. The result? Hardware text screen, all black, with a blinking text cursor in the top left. Stylin'. Had to turn the PC off to fix it.

February 02 2007 at 2:04 PM Report abuse rate up rate down Reply
Pepe

What ever it is, it's wonderful :-)
I like the comment "This must be the first real 3D-Desktop." Absolutyl priceless.

Thanks, everybody for starting me off with a smile today.

February 02 2007 at 11:28 AM Report abuse rate up rate down Reply
Anthony Scott

I got ARD to observe my computer using the built-in VNC client. It didn't lock up either. I was able to do everything at normal speed. The windowed machines just took a while to update.

February 02 2007 at 9:30 AM Report abuse rate up rate down Reply
Edsel



"Mr. Sulu, all ahead warp factor 9."

February 02 2007 at 9:24 AM Report abuse rate up rate down Reply
ossiejnr

The reason this occured was because I was trying to connect from mac A to mac B over SSH - I'd just forgotten to setup the port forward and disable my local ARD service.

Therefore when I connected to localhost it connected to itself.

I was having a senior moment :-)

-Chris-

February 02 2007 at 9:17 AM Report abuse rate up rate down Reply
Dimebag

@Ted & ossiejnr, Apple doesn't expect dumba$$es to do this…

February 02 2007 at 9:10 AM Report abuse rate up rate down Reply
Karl Childers

Actually any VNC client will do the same thing. I did this on a windows machine several months ago.

February 02 2007 at 9:02 AM Report abuse rate up rate down Reply
ossiejnr

I agree - I had to SSH in as well to kill off the ARD process.

-Chris-

February 02 2007 at 8:11 AM Report abuse rate up rate down Reply
Ted

It's kind of pathetic that the UI locks up when you do this, and a direct result of OS X having only one UI thread for every running application to share. I actually tried this a few weeks ago with Chicken of the VNC and had to ssh in from another machine to kill the process before I could use my computer again. Bad design from the hacks at Apple.

February 02 2007 at 7:46 AM Report abuse rate up rate down Reply
Buy an ad here

Hot Apps on TUAW

Tweets

© 2012 AOL Inc. All Rights Reserved.