Remote desktop: How deeply nested can you go?

[jtvang125]

If you remote desktop to one machine and then use that machine to remote desktop to another one and use that to connect to another one and so on. How far can you go before something goes wrong or stops?

 

[mzkhadir]

I have used remote desktop to another desktop and then vmware and then remote into a server before.

 

[Kappo]

It isn't so much that anything will go wrong rather than you will start getting confused as to which one is which and the performance will suffer.

 

[Stuxnet]

I have everyone beat. I have to log in to counties across the country, and I usually end up having to RD to my machine at the office, RD to the county's domain controller, then RD to a gateway machine and then finally PC Anywhere (suck) to the final node.

PITA

 

[secretanchitman]

RD into school computer (i leave mine on) to get to another computer which then i have to get access to a server. thats the farthest ive gone before.

 

[eelw]

I've only done it 2 levels deep.

 

[Lord Evermore]

From office desktop: RDP to our jumpbox (remote access to all clients), VNC to customer gateway server, Terminal Services to internal network jumpbox, TS to server I need to work on.

It is agonizingly slow, and VNC never updates the screen often enough.

Give yourself 100Mb (or better, 1Gb) dedicated links between each system, and quad-processors of the fastest models available and plenty of memory, and it'd probably be pretty usable even through several systems. But you still end up with a window within a window within a window within a window, and they all have scroll bars which take up more and more space relative to the usable desktop space. Unless you use full screen mode for each connection, which is fine if you only care about the final node and don't need to switch back to any previous nodes.