After more 2 000 000 (two million) views on forum for 1.5.0.x development versions... and 1.6.1.0, 1.6.3.0-dev versions
A new stable version, UltraVNC 1.6.4.0 and UltraVNC SC 1.6.4.0 have been released: https://forum.uvnc.com/viewtopic.php?t=38095
Feedback is always welcome

2025-12-14: 1.7.1.X-dev release builds need tests and feedback: https://forum.uvnc.com/viewtopic.php?t=38134

2025-12-02: We need help: English Wikipedia UltraVNC page has been requested to deletion: https://forum.uvnc.com/viewtopic.php?t=38127
Any help is welcome to improve the UltraVNC page and/or to comment on the Wikipedia Talk page

2025-05-06: Forum password change request: https://forum.uvnc.com/viewtopic.php?t=38078

2023-09-21: Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864

Development: UltraVNC development is always here... Any help is welcome
Feedback is welcome

Dynamic IPs in SC

Single Click discussions / bugs
Post Reply
johnhct
Posts: 6
Joined: 2008-02-21 17:02

Dynamic IPs in SC

Post by johnhct »

We've been using SC for a while now with static IP's. That part of the hekpdesk.txt looks like:
[HOST]
Support 66
-connect 69.16.235.66:5500 -noregistry

[HOST]
Support 67
-connect 69.16.235.67:5500 -noregistry

[HOST]
Support 68
-connect 69.16.235.68:5500 -noregistry

Now, we need to use it with some dynamic IPs. I thought we'd set up the port forwarding to each support rep with each having a differrent port. Then, I thought we'd set up the helpdesk.txt to look like:
[HOST]
Support1
-connect 70.16.235.66:5501 -noregistry

[HOST]
Support2
-connect 70.16.235.66:5502 -noregistry

[HOST]
Support3
-connect 70.16.235.66:5503 -noregistry

After further reading, I think it should look like:

[HOST]
Support
-connect 70.16.235.66:5500 -noregistry

And then port forward to the reps. Then, the rep with 5502 would launch SC like vncviewer.exe -listen 5502.

Is the first method or the second correct?

Thanks.
Post Reply