The one thing that would benefit is if you could get it working over Java.
The current implementation is only ActiveX within IE. It would be nice if
Netscape, and other browser, clients could get in on the action as well.
But, you are right about the licensing. a TSAC costs about $85/connection,
regardless of where it comes from, except W2K (which is a free connection
license).
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Matthew C. Grab
Sent: Wednesday, November 29, 2000 4:00 PM
To: [EMAIL PROTECTED]
Subject: Re: Announce: RDP to VNC
Now I could be dumber than the average bear, but what are the benefits of
using
a linux box to connect to W2K Terminal Server. Wouldn't you still need a
license for each user to connect to Terminal Server? Can't you already use
a
dos box to connect to Terminal Server?
Matt Grab
Alastair Carey wrote:
> Woah. Now _that_ is very cool. If you or somebody can get it serving up
W2K
> screens, you're onto a serious winner here. Imagine a network of cheap
Linux
> desktops serving up independent W2K sessions via standard W2KS/TS...
> Mind-blowing thin(nish) client solution!
>
> Is there a mailing list? I couldn't see a link to one on the page...
>
> -----Original Message-----
> From: Glenn Mabbutt [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, 30 November 2000 4:51
> To: '[EMAIL PROTECTED]'
> Subject: RE: Announce: RDP to VNC
>
> So, does this run _on_ NT4 Terminal Server? I'm sorry, I don't understand
> the "Linux-hosted" part, and the fact that the web page says "hopefully
> someone will port this to NT4"....
>
> -----Original Message-----
> From: Tim Edmonds [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, November 29, 2000 8:57 AM
> To: [EMAIL PROTECTED]
> Subject: Announce: RDP to VNC
>
> Announce: RDP to VNC
>
> the wonders of open source brings you true
> multi-user VNC access for NT4 Terminal Servers
>
> http://www-lce.eng.cam.ac.uk/~tme23/vdesktop
>
> it's fast. it's fantastic. it lets anyone with a
> vnc client connect to terminal server.
>
> rdp2vnc is basically a translating proxy between VNC
> and RDP protocols. it's not 100% complete but plenty
> usable.
>
> some caveats:
>
> - NT4 only, no support for win2k
> - Raw, RRE, CopyRect only
> - no built in httpd
> - no authentication (authenticate by TS login)
> - no VNC session persistence (it persists in TS)
> - no shared session support
> - is linux (unix) hosted
>
> comments/praise/abuse/cash to me.
>
> t
> ---------------------------------------------------------------------
> To unsubscribe, send a message with the line: unsubscribe vnc-list
> to [EMAIL PROTECTED]
> See also: http://www.uk.research.att.com/vnc/intouch.html
> ---------------------------------------------------------------------
>
> -----------------------------------------
> TridiaVNC - http://www.tridiavnc.com/
> ---------------------------------------------------------------------
> To unsubscribe, send a message with the line: unsubscribe vnc-list
> to [EMAIL PROTECTED]
> See also: http://www.uk.research.att.com/vnc/intouch.html
> ---------------------------------------------------------------------
> ---------------------------------------------------------------------
> To unsubscribe, send a message with the line: unsubscribe vnc-list
> to [EMAIL PROTECTED]
> See also: http://www.uk.research.att.com/vnc/intouch.html
> ---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
