[ On Sunday, April 21, 2002 at 17:28:06 (+0200), De Vos Rudi wrote: ]
> Subject: vnc as multi-applic server on w2k without terminal server
>
> Hi,
>
> A time ago I tought it wasn't possible to use vnc as an application
> server. But with a video driver you can
> d
CTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, 2002-04-21 10:28
Subject: vnc as multi-applic server on w2k without terminal server
> Hi,
>
> A time ago I tought it wasn't possible to use vnc as an application
> server. But with a video driver you can
> do great things.
> O
Hi,
A time ago I tought it wasn't possible to use vnc as an application
server. But with a video driver you can
do great things.
One w2k machine can serv multiple vnc clients (with each running there
own application).
Changing the code of the mirror driver a bit, the driver is now running
as a s
TRS
PHONE 603.898.2513 X1537
CELL603.560.5525
FAX 603.893.4208
EMAIL [EMAIL PROTECTED]
-Original Message-
From: Steve Palocz [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 19, 2002 1:20 PM
To: [EMAIL PROTECTED]
Subject: RE: Blank Screen - Terminal Server
Hello everyon
Hello everyone.
I have heard a lot about terminal services on 2k and xp. I agree that
terminal services has it's uses, but I still use vnc as it is just more
robust for my situation.
Now the secret to installing vnc on a terminal server or xp...
IS...
DO it from the console. If you do it
hmmm. i had seen the rdesktop stuff before, but back then they didnt have
w2k term services working correctly...
now i must play! *:)
-Original Message-
From: De Vos Rudi [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 01, 2001 4:39 PM
To: [EMAIL PROTECTED]
Subject: RE: Terminal
iginal Message -
From: "Peters, A John (MN27)" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, November 01, 2001 3:04 PM
Subject: RE: Terminal Server -- Comments
> Every Terminal Server client connection must have a license for a verion
of
> Windows NT (XP
- Original Message -
From: "Walter.Kwaan" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, November 01, 2001 2:41 PM
Subject: RE: Terminal Server -- Comments
> more importantly, you must be running a WIN32 client to use w2k term
> services.
>
&g
|more importantly, you must be running a WIN32 client to use w2k term
|services.
|
|no java client is available, no mac, no linux, no unix clients...
Not true, w2k clients exist for unix (rdesktop)
http://rdesktop.tuxia.org/rwin-1.4.0.tar.gz
or you can use the rdp2vnc on your w2k or unix box an
Every Terminal Server client connection must have a license for a verion of
Windows NT (XP 2000) etc.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Walter.Kwaan
Sent: Thursday, November 01, 2001 1:42 PM
To: '[EMAIL PROTECTED]'
Subject: RE
: [EMAIL PROTECTED]
Subject: Re: Terminal Server -- Comments
First, unlike the NT version, which is a separate product (Windows NT Server
Terminal Server Edition), and unlike Citrix Metaframe, which is an add-on to
Windows 2000 Server, Windows 2000 Server (and Advanced Server, and
Enterprise Server
First, unlike the NT version, which is a separate product (Windows NT Server
Terminal Server Edition), and unlike Citrix Metaframe, which is an add-on to
Windows 2000 Server, Windows 2000 Server (and Advanced Server, and
Enterprise Server, but not Professional) has Terminal Services as a built-in
Justin Bennett wrote:
> This sounds good, but forgive me, I have very little knowledge of the M$ server
> products/Liscensing Scams. I would need NT Terminal server, Does 2000 Advanced server
> have the Terminal Server stuff, or is it a seperate product. I can't use The 2000
This sounds good, but forgive me, I have very little knowledge of the M$ server
products/Liscensing Scams. I would need NT Terminal server, Does 2000 Advanced server
have the Terminal Server stuff, or is it a seperate product. I can't use The 2000
Professional (desktop) product or NT 4.0 s
t. This will let
you use a Linux desktop to connect to a M$ Terminal Server ... This will
let you use very thin-clients { 486/32MB-Boot Rom } ( Not M$ idea of a
thin-client ... { P3-800/128MB-8GB }) You will then not need to pay for
the desktop lic, just your cal for Terminal Server. Now y
October 31, 2001 11:27 AM
To: [EMAIL PROTECTED]
Subject: Re: Terminal Server
Would someone out there elaborate a little on
http://services.simac.be/vnc/gina.html, please? It sounds intriguing, but
it's not obvious a) where one starts from or b) where one winds up.
You have to have either
Would someone out there elaborate a little on
http://services.simac.be/vnc/gina.html, please? It sounds intriguing, but
it's not obvious a) where one starts from or b) where one winds up.
You have to have either 1) Windows NT Server Terminal Server Edition or 2)
Windows 2000 with Ter
ndows
'Terminal Server' then I could get around this, it would need to support
about 120 clients. However, I'm trying to do this without paying microsoft
any more money than needed. I'm running Sun PCnetlink on Solaris to avoid
paying licensing on a NT/2000 box. It doesn't
ia the list archives.
Glenn
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 31, 2001 8:00 AM
To: [EMAIL PROTECTED]
Subject: RE: Terminal Server -- Comments
Interesting, but i think he was looking to do this
with out terminal services.. which i
as written..
>From what i can tell anyway.. Hell it might even negate
what they are doing on that web page..
/rant ON
stupid Microsoft licensing schemes. Grrr
/rant OFF
Zig-
>
> Date: Tue, 30 Oct 2001 17:00:35 -0500
> From: Glenn Mabbutt <[EMAIL PROTECTED]>
> Subject: RE
See http://services.simac.be/vnc/gina.html - same idea, but config is
somewhat manual...
-Original Message-
From: Justin Bennett [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 31, 2001 3:59 AM
To: '[EMAIL PROTECTED]'
Subject: Terminal Server
For the VNC programmers o
For the VNC programmers on the list, has any thought been given to
making the VNC server peice capable of serving multiple sessions
fromWindoze NT/2000, acting like a Winframe Terminal Server, but not
having to pay for a commercial solution? I know the idea is to keep VNC
compact and changing
You should try rdp2vnc, from
http://www.uk.research.att.com/~jnw/downloadables, which is a newer
equivalent of vdesktop.
There should also be another new release based on rdp2vnc quite soon, with
more encodings, better updates and suchlike.
Cheers,
---
James "Wez" Weatherall
"The path
r-own
"terminal server" running on NT/2000 that uses VNC.
second link: offers basically an RDP-VNC gateway. Potentially useful if
you've already got MS Terminal Server/Services running, but want to use VNC
as the client. Does not run natively on NT/2000 (runs on Linux) but if yo
Can anyone tell me what is the better route:
This..
http://services.simac.be/vnc/gina.html
or
http://www-lce.eng.cam.ac.uk/~tme23/vdesktop/
Do these two projects do the same thing?
help.
-
To unsubscribe, mail [EMAIL PROTEC
Sure. I'll get one on Monday when I'm back in the office. Thanks.
- Original Message -
From: "James ''Wez'' Weatherall" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, January 19, 2001 4:54 AM
Subject: Re: Pocket PC, Te
> D:\ORL\vss\winvnc\vncClient.cpp : client connected : 255.255.255.2 (1)
> D:\ORL\vss\winvnc\vncServer.cpp : verify succeeded - null filter
> Thu Jan 18 13:54:22 2001
> D:\ORL\vss\winvnc\VSocket.cpp : socket error 0
>
> That is it. The VNC client shows "Connection Closed." Again, this
> procedur
OK, here is the log when I connect to from the iPAQ Terminal Server client
from the Win2K terminal server to a WinNT 4 machine with VNC server running.
Thu Jan 18 13:51:26 2001
D:\ORL\vss\winvnc\vncService.cpp : SelectHDESK to Default (10) from
10D:\ORL\vss\winvnc\vncService.cpp : SelectHDESK
> > > Is that correct? What happens if you start a session using the PC
> > > client, then run VNCviewer, disconnect the TS session and reconnect to
> it
> > > from the PocketPC?
> >
> > It works. The VNC client doesn't die or get kicked by the VNC Server.
Of
> > course that only does me goo
> > Is that correct? What happens if you start a session using the PC
> > client, then run VNCviewer, disconnect the TS session and reconnect to
it
> > from the PocketPC?
>
> It works. The VNC client doesn't die or get kicked by the VNC Server. Of
> course that only does me good if I set up
> > > > I have an iPAQ Pocket PC that runs Windows CE 3.0. I need to be
able
> to
> > > log
> > > > onto my Windows 2000 Terminal Server and launch a VNC client inside
> > *that*
> > > > window to access other machines on our network.
Thanks - I'll give it a shot.
- Original Message -
From: "Ben Prescott" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, January 17, 2001 6:23 PM
Subject: Re: Pocket PC, Terminal Server client and VNC
> I've just put server on my W2K
it running primarily on Windows 2000 machines. How do you start the
>log and where is it located? I couldn't find it in the FAQ or docs.
>
>- Original Message -
>From: "Ben Prescott" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Sent: Tuesday, J
Hey Ed,
Notice you mentioned using Windows Terminal Server on your Pocket PC.
How do you find it? I am looking for a device I can plug directly into my
mobile and log onto a Terminal server via dial-up, I have tried the PalmVNC
but it is dog slow and virtually unusable.
Let me know. Or if
> > > I have an iPAQ Pocket PC that runs Windows CE 3.0. I need to be able
to
> > log
> > > onto my Windows 2000 Terminal Server and launch a VNC client inside
> *that*
> > > window to access other machines on our network. I can do this just
fine
> > &
> > I have an iPAQ Pocket PC that runs Windows CE 3.0. I need to be able to
> log
> > onto my Windows 2000 Terminal Server and launch a VNC client inside
*that*
> > window to access other machines on our network. I can do this just fine
> > with my PC's Win2K Te
AIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 16, 2001 4:17 PM
Subject: Re: Pocket PC, Terminal Server client and VNC
> Does the vnc server log anything when you get kicked out?
>
>
> At 19:21 15/01/01 -0600, you wrote:
> >I have just joined this list. I se
t runs Windows CE 3.0. I need to be able to log
>onto my Windows 2000 Terminal Server and launch a VNC client inside *that*
>window to access other machines on our network. I can do this just fine
>with my PC's Win2K Terminal Server client.
>
>On the iPAQ however, I log int
January 16, 2001 6:57 AM
Subject: Re: Pocket PC, Terminal Server client and VNC
> > I have an iPAQ Pocket PC that runs Windows CE 3.0. I need to be able to
> log
> > onto my Windows 2000 Terminal Server and launch a VNC client inside
*that*
> > window to access other machines on o
> I have an iPAQ Pocket PC that runs Windows CE 3.0. I need to be able to
log
> onto my Windows 2000 Terminal Server and launch a VNC client inside *that*
> window to access other machines on our network. I can do this just fine
> with my PC's Win2K Terminal Server client
I have just joined this list. I searched the archives first and read the
FAQ and everything else and couldn't find anything on this, so here it goes.
I have an iPAQ Pocket PC that runs Windows CE 3.0. I need to be able to log
onto my Windows 2000 Terminal Server and launch a VNC client i
41 matches
Mail list logo
