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
- 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
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
- 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
Command line viewer IP specification
Command line viewer IP specification
I'd like to use UltraVNC SC instead of a real VNC install for remote controlling a computer on the LAN. As it is now, there are scripts which will install VNC on the remote computer, register it, set a default password, etc etc... well, SC doesn't need to be installed, doesn't need a default password, or anything. If it supported supplying the IP address of a viewer on the command line then it would be the perfect remote administration tool. Imagine this scenario:
I am the administrator of my lan. My clients do not wish to have any remote control software installed on their computers and available all the time, but they do demand remote support. I'm not always using my computer, or even using the same IP. So, I use PSEXEC to launch "UltraVNCSC -connect 192.168.0.251" and it launches and connects directly to the computer i'm on!
Nothing really has to change except adding a command line connection option. The software otherwise works perfectly.
Anyways, what do you think? Useful feature? Stupid idea? I know it already connects to a pre-defined IP address, but what if my IP address changes? A command line option for specifying an IP would make it so I don't have to create a new UltraVNC SC every time.
I am the administrator of my lan. My clients do not wish to have any remote control software installed on their computers and available all the time, but they do demand remote support. I'm not always using my computer, or even using the same IP. So, I use PSEXEC to launch "UltraVNCSC -connect 192.168.0.251" and it launches and connects directly to the computer i'm on!
Nothing really has to change except adding a command line connection option. The software otherwise works perfectly.
Anyways, what do you think? Useful feature? Stupid idea? I know it already connects to a pre-defined IP address, but what if my IP address changes? A command line option for specifying an IP would make it so I don't have to create a new UltraVNC SC every time.
Re: Command line viewer IP specification
repeater made for this function
vncviewer and winvnc could be used anywhere and with any IP change.
only repeater ip address do not change.
vncviewer and winvnc could be used anywhere and with any IP change.
only repeater ip address do not change.
UltraVNC 1.0.9.6.1 (built 20110518)
OS Win: xp home + vista business + 7 home
only experienced user, not developer
OS Win: xp home + vista business + 7 home
only experienced user, not developer
Re: Command line viewer IP specification
that works fine for one person, but lets say I have 5 techs out... 5 repeaters? 5 uvnc-sc.exe files? and if I have 5 sites that are independent of each other, that I visit... 25 uvnc-sc.exe files? (5 for each site for each tech) that's an N*2 solution, for which the repeater is useless. Sure you can have the users prompted to type in a seperate session ID number, requiring only one file per site, but that adds to the complexity, and half the users that I tried it with, couldn't enter the numbers right...
what's wrong with providing an alternative option?
what's wrong with providing an alternative option?
Re: Command line viewer IP specification
need only same SingleClick for all customers, and only one same vncviewer for all yours tech and only one repeater in the middle aka distributor for everyone.
[topic=6665][/topic]
this optimized SingleClick from luk.o solve some limitation of the official SingleClick from Rudi
repeater mode II or III
http://sc.uvnc.com/index.php?section=27
[topic=6665][/topic]
this optimized SingleClick from luk.o solve some limitation of the official SingleClick from Rudi
repeater mode II or III
http://sc.uvnc.com/index.php?section=27
nothing wrong at all. but unable to use your solution over WAN blocked from all WAN acces for security except over VPN not consided as WAN but considered as LAN.what's wrong with providing an alternative option?
UltraVNC 1.0.9.6.1 (built 20110518)
OS Win: xp home + vista business + 7 home
only experienced user, not developer
OS Win: xp home + vista business + 7 home
only experienced user, not developer
Re: Command line viewer IP specification
that's what I'm trying to tell you... by focusing ONLY on wan, you make it a PITA to use on a LAN. Add the option to specify an IP on the command line, and you make LAN use much easier, while not changing the WAN usage scenario. Sure I can setup a repeater, but if I have 5 sites, not connected to each other or the internet, I have to have 5 repeaters and 5 different uvnc-sc.exe files for each tech at each site... (different IP addressing at each site and each tech has a different ID for repeater mode).
Re: Command line viewer IP specification
do you mean ?PSEXEC to launch "UltraVNCSC -connect 192.168.0.251
tech push SC to customer, then customer have the SC auto lunched connecting to your vncviewer -listen ?
could be nice SC feature for LAN
Last edited by redge on 2006-08-22 22:17, edited 1 time in total.
UltraVNC 1.0.9.6.1 (built 20110518)
OS Win: xp home + vista business + 7 home
only experienced user, not developer
OS Win: xp home + vista business + 7 home
only experienced user, not developer
Re: Command line viewer IP specification
redge, that's exactly what I mean.. :) It would be an awesome feature for a lan.
Re: Command line viewer IP specification
improved
vncviewer -push SC.exe -callback ip/host_remote -listen ip/host_allowed::port
optional -listen ip/host_allowed::port
so you listen only this awaiting remote computer you try to remote control, so you are not troubled by another incoming session.
vncviewer -push SC.exe -callback ip/host_remote -listen ip/host_allowed::port
optional -listen ip/host_allowed::port
so you listen only this awaiting remote computer you try to remote control, so you are not troubled by another incoming session.
Last edited by redge on 2006-08-23 01:29, edited 1 time in total.
UltraVNC 1.0.9.6.1 (built 20110518)
OS Win: xp home + vista business + 7 home
only experienced user, not developer
OS Win: xp home + vista business + 7 home
only experienced user, not developer
Re: Command line viewer IP specification
"improved" ? what do you mean by that?redge wrote:improved
vncviewer -push SC.exe -callback ip/host_remote -listen ip/host_allowed::port
optional -listen ip/host_allowed::port
so you listen only this awaiting remote computer you try to remote control, so you are not troubled by another incoming session.
Last edited by SpiderX on 2006-08-23 06:04, edited 1 time in total.
Re: Command line viewer IP specification
improved, sorry should be increase the functionality
limit to only listen certain ip or FQDN from command line.
limit to only listen certain ip or FQDN from command line.
UltraVNC 1.0.9.6.1 (built 20110518)
OS Win: xp home + vista business + 7 home
only experienced user, not developer
OS Win: xp home + vista business + 7 home
only experienced user, not developer
Re: Command line viewer IP specification
redge, your english was proper. My question was, what did you improve? Is there a seperate version to download to enable that?
Re: Command line viewer IP specification
my english is not proper,
because is a mistake, I would meaning need improve not improved
so, not yet exist as my knowledge
because is a mistake, I would meaning need improve not improved
so, not yet exist as my knowledge
UltraVNC 1.0.9.6.1 (built 20110518)
OS Win: xp home + vista business + 7 home
only experienced user, not developer
OS Win: xp home + vista business + 7 home
only experienced user, not developer
Re: Command line viewer IP specification
I'll be happy to help if you wish to improve your english.