Hi Guys,
I'm running last Ultr@VNC on my PCs at home, actually only on 2 laptops (clients) and desktop (server).
I was wondering if Ultr@VCN could handle more client connection to the same server, opening one session for every user/client.
In such a way more users could share the same server.
Is it possible?
Thanks!
Celebrating the 22th anniversary of the UltraVNC: https://forum.uvnc.com/viewtopic.php?t=38031
Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: https://forum.uvnc.com/viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Bluesky/AT Protocol: https://bsky.app/profile/ultravnc.bsky.social
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: https://forum.uvnc.com/viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Bluesky/AT Protocol: https://bsky.app/profile/ultravnc.bsky.social
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
More than 1 session at the same time on server
-
- Posts: 1
- Joined: 2005-01-30 13:06
- Location: Italy
More than 1 session at the same time on server
Ciao
Michele
Michele
I am going to give this a go from my precarious newbie position.
I am going into detail not because I want to show off, but in the hope that I can make the process of trying my suggestion as simple as possible! I hope it helps.
I think you can do what you ask.
You MAY not need to do all this. You _may_ be able to log in as normal, just with multiple Viewers. But it does indicate that the Server will handle more than one Client.
Of course each Client will have to be careful, as they are controlling the Server, not just using its resources as normal networking does. Could be confusing.<G>
Theory:
* You can make the Viewers into "listening Viewers". Place /listen after the call to the VNC Viewer programme on the command line in the icon/shortcut that calls your Viewer.
eg I have a shortcut to the Viewer in a desktop folder. the Properties command line reads .
"C:\Program Files\UltraVNC\vncviewer.exe" /listen
include quotes as shown.
You then run these listening Viewers on the laptops. On the Server, you run the Server winvnc, and right click the tray icon. Up comes "Add new Client", and you can call the IP address of any Client on the system.
There is also the possibility of runnnig multiple Servers on the same machine. You again need to use command lines.\
"C:\Program Files\UltraVNC\winvnc.exe" -multi
This allows multi instances of ther Server to be runnnig on the Host.
I have not played around with this, and I am not sure how this allows each Viewer to interact with the Server and / or each other, differently from both being on the same instance of a Server.
Quote from http://ultravnc.sourceforge.net/comserver.htm
"-multi : This option forces WinVNC to allow others WinVNC instances to be run on the same machine at the same time. It can be very usefull for remote upgrades, or to have one WinVNC that uses a DSMPlugin on one port while another runs normally on another port. Please keep in mind that this option is experimental and that all WinVNC instances save their settings at the same places in the registry..."
This +seems_ to indicate that (a) it may be unstable <G> (b) it will allow independent sessions on the one server.
I am going into detail not because I want to show off, but in the hope that I can make the process of trying my suggestion as simple as possible! I hope it helps.
I think you can do what you ask.
You MAY not need to do all this. You _may_ be able to log in as normal, just with multiple Viewers. But it does indicate that the Server will handle more than one Client.
Of course each Client will have to be careful, as they are controlling the Server, not just using its resources as normal networking does. Could be confusing.<G>
Theory:
* You can make the Viewers into "listening Viewers". Place /listen after the call to the VNC Viewer programme on the command line in the icon/shortcut that calls your Viewer.
eg I have a shortcut to the Viewer in a desktop folder. the Properties command line reads .
"C:\Program Files\UltraVNC\vncviewer.exe" /listen
include quotes as shown.
You then run these listening Viewers on the laptops. On the Server, you run the Server winvnc, and right click the tray icon. Up comes "Add new Client", and you can call the IP address of any Client on the system.
There is also the possibility of runnnig multiple Servers on the same machine. You again need to use command lines.\
"C:\Program Files\UltraVNC\winvnc.exe" -multi
This allows multi instances of ther Server to be runnnig on the Host.
I have not played around with this, and I am not sure how this allows each Viewer to interact with the Server and / or each other, differently from both being on the same instance of a Server.
Quote from http://ultravnc.sourceforge.net/comserver.htm
"-multi : This option forces WinVNC to allow others WinVNC instances to be run on the same machine at the same time. It can be very usefull for remote upgrades, or to have one WinVNC that uses a DSMPlugin on one port while another runs normally on another port. Please keep in mind that this option is experimental and that all WinVNC instances save their settings at the same places in the registry..."
This +seems_ to indicate that (a) it may be unstable <G> (b) it will allow independent sessions on the one server.
I am going to give this a go from my precarious newbie position.
I am going into detail not because I want to show off, but in the hope that I can make the process of trying my suggestion as simple as possible! I hope it helps.
I think you can do what you ask.
You MAY not need to do all this. You _may_ be able to log in as normal, just with multiple Viewers. But it does indicate that the Server will handle more than one Client.
Of course each Client will have to be careful, as they are controlling the Server, not just using its resources as normal networking does. Could be confusing.<G>
Theory:
* You can make the Viewers into "listening Viewers". Place /listen after the call to the VNC Viewer programme on the command line in the icon/shortcut that calls your Viewer.
eg I have a shortcut to the Viewer in a desktop folder. the Properties command line reads .
"C:\Program Files\UltraVNC\vncviewer.exe" /listen
include quotes as shown.
You then run these listening Viewers on the laptops. On the Server, you run the Server winvnc, and right click the tray icon. Up comes "Add new Client", and you can call the IP address of any Client on the system.
There is also the possibility of runnnig multiple Servers on the same machine. You again need to use command lines.\
"C:\Program Files\UltraVNC\winvnc.exe" -multi
This allows multi instances of ther Server to be runnnig on the Host.
I have not played around with this, and I am not sure how this allows each Viewer to interact with the Server and / or each other, differently from both being on the same instance of a Server.
Quote from http://ultravnc.sourceforge.net/comserver.htm
"-multi : This option forces WinVNC to allow others WinVNC instances to be run on the same machine at the same time. It can be very usefull for remote upgrades, or to have one WinVNC that uses a DSMPlugin on one port while another runs normally on another port. Please keep in mind that this option is experimental and that all WinVNC instances save their settings at the same places in the registry..."
This +seems_ to indicate that (a) it may be unstable <G> (b) it will allow independent sessions on the one server.
I am going into detail not because I want to show off, but in the hope that I can make the process of trying my suggestion as simple as possible! I hope it helps.
I think you can do what you ask.
You MAY not need to do all this. You _may_ be able to log in as normal, just with multiple Viewers. But it does indicate that the Server will handle more than one Client.
Of course each Client will have to be careful, as they are controlling the Server, not just using its resources as normal networking does. Could be confusing.<G>
Theory:
* You can make the Viewers into "listening Viewers". Place /listen after the call to the VNC Viewer programme on the command line in the icon/shortcut that calls your Viewer.
eg I have a shortcut to the Viewer in a desktop folder. the Properties command line reads .
"C:\Program Files\UltraVNC\vncviewer.exe" /listen
include quotes as shown.
You then run these listening Viewers on the laptops. On the Server, you run the Server winvnc, and right click the tray icon. Up comes "Add new Client", and you can call the IP address of any Client on the system.
There is also the possibility of runnnig multiple Servers on the same machine. You again need to use command lines.\
"C:\Program Files\UltraVNC\winvnc.exe" -multi
This allows multi instances of ther Server to be runnnig on the Host.
I have not played around with this, and I am not sure how this allows each Viewer to interact with the Server and / or each other, differently from both being on the same instance of a Server.
Quote from http://ultravnc.sourceforge.net/comserver.htm
"-multi : This option forces WinVNC to allow others WinVNC instances to be run on the same machine at the same time. It can be very usefull for remote upgrades, or to have one WinVNC that uses a DSMPlugin on one port while another runs normally on another port. Please keep in mind that this option is experimental and that all WinVNC instances save their settings at the same places in the registry..."
This +seems_ to indicate that (a) it may be unstable <G> (b) it will allow independent sessions on the one server.
hmmm...try again.....
I am going to give this a go from my precarious newbie position.
I am going into detail not because I want to show off, but in the hope that I can make the process of trying my suggestion as simple as possible! I hope it helps.
I think you can do what you ask.
You MAY not need to do all this. You _may_ be able to log in as normal, just with multiple Viewers. But it does indicate that the Server will handle more than one Client.
Of course each Client will have to be careful, as they are controlling the Server, not just using its resources as normal networking does. Could be confusing.<G>
Theory:
* You can make the Viewers into "listening Viewers". Place /listen after the call to the VNC Viewer programme on the command line in the icon/shortcut that calls your Viewer.
eg I have a shortcut to the Viewer in a desktop folder. the Properties command line reads .
"C:\Program Files\UltraVNC\vncviewer.exe" /listen
include quotes as shown.
You then run these listening Viewers on the laptops. On the Server, you run the Server winvnc, and right click the tray icon. Up comes "Add new Client", and you can call the IP address of any Client on the system.
There is also the possibility of runnnig multiple Servers on the same machine. You again need to use command lines.\
"C:\Program Files\UltraVNC\winvnc.exe" -multi
This allows multi instances of ther Server to be runnnig on the Host.
I have not played around with this, and I am not sure how this allows each Viewer to interact with the Server and / or each other, differently from both being on the same instance of a Server.
Quote from http://ultravnc.sourceforge.net/comserver.htm
"-multi : This option forces WinVNC to allow others WinVNC instances to be run on the same machine at the same time. It can be very usefull for remote upgrades, or to have one WinVNC that uses a DSMPlugin on one port while another runs normally on another port. Please keep in mind that this option is experimental and that all WinVNC instances save their settings at the same places in the registry..."
This +seems_ to indicate that (a) it may be unstable <G> (b) it will allow independent sessions on the one server.
I am going to give this a go from my precarious newbie position.
I am going into detail not because I want to show off, but in the hope that I can make the process of trying my suggestion as simple as possible! I hope it helps.
I think you can do what you ask.
You MAY not need to do all this. You _may_ be able to log in as normal, just with multiple Viewers. But it does indicate that the Server will handle more than one Client.
Of course each Client will have to be careful, as they are controlling the Server, not just using its resources as normal networking does. Could be confusing.<G>
Theory:
* You can make the Viewers into "listening Viewers". Place /listen after the call to the VNC Viewer programme on the command line in the icon/shortcut that calls your Viewer.
eg I have a shortcut to the Viewer in a desktop folder. the Properties command line reads .
"C:\Program Files\UltraVNC\vncviewer.exe" /listen
include quotes as shown.
You then run these listening Viewers on the laptops. On the Server, you run the Server winvnc, and right click the tray icon. Up comes "Add new Client", and you can call the IP address of any Client on the system.
There is also the possibility of runnnig multiple Servers on the same machine. You again need to use command lines.\
"C:\Program Files\UltraVNC\winvnc.exe" -multi
This allows multi instances of ther Server to be runnnig on the Host.
I have not played around with this, and I am not sure how this allows each Viewer to interact with the Server and / or each other, differently from both being on the same instance of a Server.
Quote from http://ultravnc.sourceforge.net/comserver.htm
"-multi : This option forces WinVNC to allow others WinVNC instances to be run on the same machine at the same time. It can be very usefull for remote upgrades, or to have one WinVNC that uses a DSMPlugin on one port while another runs normally on another port. Please keep in mind that this option is experimental and that all WinVNC instances save their settings at the same places in the registry..."
This +seems_ to indicate that (a) it may be unstable <G> (b) it will allow independent sessions on the one server.