So as some of you know I use a Mac Pro at home, and spend most of my time in Mac OS X. (I have VMs with Windows Server 2008 for SQL Server and other Windows development.) I use RDC on the Mac to connect to my desktop at work (after I use the 64-bit VPN client which Cisco makes for the Mac, but not for Windows (!)), where I have ready access to SourceSafe, Visual Studio etc. It is not the fastest, but it's good enough on most days.
Today I am trying to find the weak network and/or I/O spots in our primary data center facility, due to an increasing frequency of failure in either backups or post-backup file copies. So the image you see below is me connecting from the Mac, to my desktop at work (Windows Server 2008 x64 R2), then hopping to 3.205, then to 3.202, then finally to 5.205 (all of the RDP sessions are nested, not individual!). I won't get into the details of why I have to go through so many hoops, and I'm sure there are better ways to do what I'm trying to do with these specific tests, but for now it works so I will leave the process alone. I posted it more because I found it amusing as I prepare to turn my computer off for the evening.
I should have added what protocol's it supports:-
RDP, VNC, Telnet, SSH1 & 2 & ICA Citrix which adds that buit extra.
Cheers,
Stephen
Thanks Stephen, I will check that out! In certain scenarios I need to hop and nest but there are certainly some cases where something like that could come in handy.
Not sure if this would work (depends on those ins and outs of all your IP's and how and where you can get to them.
http://www.codeplex.com/Terminals/
Think of it as a RDP Tabbed Client (ala. IE/Firefox Tabs but for RDP)
Cheers,
Stephen
My best:
Laptop -> home server with VPN software installed
Home Server -> Work gateway server
Work gateway -> Work Desktop
Work Desktop -> Datacenter gateway
Datecenter gateway -> Our group gateway
Group gateway -> Application server I actually needed to manage