Open Source Terminal Server

[Jan Blomqvist Kinander]

Hi Developers, I have been aproached by a certain Gonzalo from Colombia, he claims to be a
developer who wants to make a Terminal Server Clone, I enclose the mail he sent me, please
have a look at it and answer him.

Yours Sincerely,
Jaix Bly

>  >> 
Hey Jaix, i'm Gonzalo from Colombia
(South America) tecnologia(a)slmsistemas.net 

I'm a coder, i develop more than 500 utils and apps for terminal server and citrix
.... i have a product called Galeon that is a "clon" of terminal server with
shell replacement, full duplex sound, universal printer driver, etc ...


I want to develop a Open Source Terminal Server based in something like VNC and OpenVPN

Opening many sessions in windows is really bad idea ... for kernel stuff and another
csrss, smss problems ... terminal server blue screen, black screen, printers, etc ... so i
have an idea for a workaround ...


Is open a session using createwinstation api ... in that session, create multiples
desktops, using createdesktop api, in each desktop will be secure shell replacement,
ejecuted using x user credentials (runas) ... the printing is gonna be universal virtual
printers that receive the buffer from the win32, and send the emf or pdf to the client
...


Using Virtual Channels is a pain in the ass ... because they all travel using only one tcp
socket ... (really bad idea) so, problems with video, audio, performance, etc ...i think
we can use openvpn to connect to only one port (443 to ssl vpn) and after the vpn is
connected, we can open many socket (each service) between the client and the server
desktop ... so we can send printing, sound, video, etc ...


I have many things already developed ... createwinstation, createdesktop, impersonate
users, universal printer, openvpn implementation .. etc ... but i need help in other
areas, like the video grabber in the desktop (maybe a modified vnc) i can make a
printscreen of each desktop, and send the jpg ... and is working, but is a really bad idea
...


This product can merge with ReactOS .. and be the ReactOS terminal server ...

https://sourceforge.net/projects/oswts/

What do you think?

Do you receive this mail?


Thanks, 

Gonzalo.

-- 
Cordialmente:

Ing. Gonzalo Araujo C
MCSE, MCSA, MCSD, ITIL, CISSP, C|EH, LPI
Desarrollo SLM Sistemas Ltda
desarrollo(a)slmsistemas.com
tecnologia(a)slmsistemas.net

http://www.slmsistemas.com
Colombia - Guatemala - Chile - Venezuela
<<<

[Timo Kreuzer]

Jan Blomqvist Kinander wrote:
>   Hi Developers, I have been aproached by a certain
> Gonzalo from Colombia, he claims to be a developer who wants to make a Terminal Server
> Clone, I enclose the mail he sent me, please have a look at it and answer him.
>
>  Yours Sincerely,
>  Jaix Bly
>     
I'll reply here.
>   I want to develop a Open Source Terminal Server based
> in something like VNC and OpenVPN
>
>  Opening many sessions in windows is really bad idea ... for kernel stuff and another
> csrss, smss problems ... terminal server blue screen, black screen, printers, etc ... so i
> have an idea for a workaround ...
>
>
>  Is open a session using createwinstation api ... in that session, create multiples
> desktops, using createdesktop api, in each desktop will be secure shell replacement,
> ejecuted using x user credentials (runas) ... the printing is gonna be universal virtual
> printers that receive the buffer from the win32, and send the emf or pdf to the client
> ...
>     
By design, each session can only have one interactive WindowStation,
that is only one WindowStation with keyboard and mouse input. And I
don't see a possibility to work around this limit. It would also limit
resources, such as number of gdi objects. There's a good reason for
sessions as they are, if you see problems in the current NT
implementation, please specify.

>   Using Virtual Channels is a pain in the ass ...
> because they all travel using only one tcp socket ... (really bad idea) so, problems with
> video, audio, performance, etc ...i think we can use openvpn to connect to only one port
> (443 to ssl vpn) and after the vpn is connected, we can open many socket (each service)
> between the client and the server desktop ... so we can send printing, sound, video, etc
> ...
>     
Remember that ReactOS aims at compatibility with Windows. A terminal
server must be compatible to Windows terminal services.

>  
>  I have many things already developed ... createwinstation, createdesktop, impersonate
> users, universal printer, openvpn implementation .. etc ... but i need help in other
> areas, like the video grabber in the desktop (maybe a modified vnc) i can make a
> printscreen of each desktop, and send the jpg ... and is working, but is a really bad idea
> ...
>
>
>  This product can merge with ReactOS .. and be the ReactOS terminal server ...
>
>  https://sourceforge.net/projects/oswts/
>
>  What do you think?
>
>  Do you receive this mail?
>
>
>  Thanks, 
>
>  Gonzalo.
>
>

[Ged Murphy]

This is the part I'm unclear on

>   Opening many sessions in windows is really bad idea
> ... for 
>  kernel stuff and another csrss, smss problems ... terminal server 
>  blue screen, black screen, printers, etc ... so i have an idea 
>  for a workaround ... 
What leads you to believe it's a bad idea?

In my job, I design and write enterprise software which can manage sessions
into the thousands.
I've never once come across a problem related to multiple sessions.
Windows was designed to handle numerous sessions and with the upcoming
advances in VDI, it's being pushed more and more.

Ged.