Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

General discussion

Multiple Remote Desktop Connections to a single host

Jul 8, 2009 3:14AM PDT

Good Afternoon

I am trying to research this for my boss, but havent had much luck with it.

What he is trying to do is, for lack of a better description, setup a remote desktop server, that will allow multiple clients to remote in to have direct access to our software.

We have well over 500 clients and remote users for this system that may end up connecting.

Now, I have found hacks for Windows XP that increase the multiple concurrent connections, but that only goes to 3. I have looked into a software called ThinStuff, but cant get through the base configuration and cant get any sort of support.

I know we can do what we want to do with a Terminal Server, but he doesnt want to pay for licesnes for each and every person in order to do this. I have also looked into clients like citrix, x2, quest and others, but they all require Ts to run.

Does anyone know of a third party software taht will allow multiple RDP connections to a single system, or does anyone know of another way of doing this?

Anything would be helpfull.

Thanks

Discussion is locked

- Collapse -
(NT) Why not go web-based?
Jul 8, 2009 7:51AM PDT
- Collapse -
That's called Terminal Server.
Jul 9, 2009 1:05AM PDT

And a machine to run 500 instances of anyone's software is unlikely be found in your office.

I'd re-plan this and go web based next time.
Bob

- Collapse -
hello
Jul 14, 2009 4:52PM PDT

I also stuck on the same problem. If you do have any solution regarding this please tell me.

- Collapse -
"a machine to run 500 instances of anyone's software is
Jul 16, 2009 12:38AM PDT

"a machine to run 500 instances of anyone's software is unlikely be found".

Given the requirement you should remain stuck for a few years.
bob

- Collapse -
a machine to run 500 instances of anyone's software is unlik
Jul 29, 2010 5:48PM PDT

hiiii

is it possible for a machine to run 500 instances of anyone's software

- Collapse -
I think we covered that.
Aug 1, 2010 7:09AM PDT

Given the millions this will cost, your next stop is to the companies that provide terminal server and platforms to host this.
Bob

- Collapse -
Multiple connections
Aug 9, 2009 12:43AM PDT

First, going web based is probably not a solutions because your software is not web based. And therefore can't be ran in a browser.
Second, you need to ask yourself these questions.
1. how many CONCURRENT connections do you anticipate having?
2. What is the real budget?
3. Can your internet feed handle this amount of traffic?
4. your opeing up a "security, can of worms" You have 500 computers out there that you know nothing about, -(viruses, passwords, security levels, who sites at them, etc etc).
You will not run this many users on an XP box, I don't care how they get to the software. You will have to go with a Windows Server, unless your software will run on Linux, then go Ubuntu.

You should be going web based with this one, BUT you a complete re-wite of the software would have to be done. (Yikes, the thought of it). If your software was written in Clarion, a 10 minute, low cost solution exists for this project.
Good Luck
Les

- Collapse -
Thinstuff
Aug 12, 2009 6:12AM PDT

You might consider the Thinstuff terminal server solution. It's compatible with the Microsoft client and it also needs to be paid for, but you can have an unlimited license for a reasonable price. Making it cheaper than the Microsoft solution.

About the Microsoft one, when paying for the licenses, I believe that you only have to pay for the simultaneous accesses, not for the whole potential user base. Did you consider that?

- Collapse -
Simultantous / concurrent licensing for Windows Servers??
Jul 27, 2010 5:37AM PDT

If you are talking about Terminal Server CALS, those are not for concurrent/simultaneous usage. You need as many as you have USERS or DEVICES depending on how you choose to use it. Then - if you don't use your CAL for 90 days (or so) - it is cancelled and reusable by another user/device.