"Linonut" <linonut@xxxxxxxxxxxxx> wrote in message
news:pguej.43018$vt2.10069@xxxxxxxxxxxxxxxxxxxxxxxxx
>* Antonio Murphie fired off this tart reply:
>
>>
>> "Linonut" <linonut@xxxxxxxxxxxxx> wrote in message
>> news:sRsej.42969$vt2.1997@xxxxxxxxxxxxxxxxxxxxxxxxx
>>>* Antonio Murphie fired off this tart reply:
>>>
>>>> "Roy Schestowitz" <newsgroups@xxxxxxxxxxxxxxx> wrote in message
>>>> news:35279476.aPtAkqZxjB@xxxxxxxxxxxxxxxxxx
>>>>
>>>> In other words.... it's just like "Remote Desktop" which has been
>>>> bundled
>>>> with every Windows computer for the past 8 years.
>>>
>>> Nope. First, X has been around in one form or another for 23 years.
>>> SSH has been around for 12 years.
>>
>> Thanks for the history lesson but what does it matter? The issue isn't
>> which protocol has been around the longest... it's functionality. In the
>> end the user has a graphical connection to the remote computer. Whether
>> ssh
>> has been around 12 years and RDP only 8 years isn't relevant. The issue
>> is
>> administering a remote computer.
>
> And, of course, UNIX has had the covered for /far/ longer than Windows,
> Chuck-o.
Longer yes. But people using it today care more about functionality and
capabilities than the historical walk down memory lane.
>> Yeah I know how it works. At work we may need to connect remotely to any
>> one of over 30,000 remote servers that we administer.
>
> So why the "ignoramus" ploy?
Not at all. I'm simply setting the record straight that the capability
Schestowitz was recommending to remotely install Opera is essentially doing
the exact same thing that Remote Desktop would do.
>> With RDP (the Microsoft implementation) users can also connect to
>> "sound",
>> "printers", "serial ports", "disk drives" and etc. So it makes the
>> notion
>> that you can optionally tunnel FTP, cp, etc. somewhat redundant since
>> RDP
>> also supports this.
>
> Cool.
>
>>> "ssh -L3390:mydesktop.mycompany.net:3389 sshserver.mycompany.net"
>>
>> Yep. Been there and done that.
>
> Sure you have. Sure you have.
I do it quite often. I work at the IT center of a Fortune 500 company.
(We're almost a Fortune 100 company.) So say we need to administer a remote
Windows machine in California. All of the desktops (running Windows) are
behind a Unix machine. You login to the Unix box using a line similar to
yours:
"ssh -l username -L3390:mydesktop.mycompany.net:3389
sshserver.mycompany.net"
Then forward local port 3390 to port 3389 on the remote side. Then locally
I startup remote desktop and connect to localhost:3390 and the port gets
forwarded to the remote machine. Not exactly rocket surgery.
>>> GNU/Linux and OSS wins (get it? get it?) again!
>>
>> Not a strong start for the New Year, eh?
>
> I agree. Slapping you down isn't much.
So that's what that was. I thought some punk was tickling me.
--
Posted via a free Usenet account from http://www.teranews.com
|
|
