UltraVNC Single Click Help

[psass]

Hi,

I posted a couple of questions last week and am still sitting here tonight wondering what I am doing wrong.

I have UltraVNC installed on two computers in my home where I have a small network consisting of 4 XP-Pro workstations and one Windows 2003 server.

I have the full blown server installed on the Windows 2003 server and one other workstation. I have the viewer installed on my own computer. I have no problems and get an instant connection and all works 100%.

I was after trying to get the Single Click version going and have setup the customized version of this point to my computer's IP address and tried a variety of ports. Ports: 443, 445, 5500, 5800, 5900. I know that port 5900 will work to my IP address as I can connect using the full blown server. So I setup the single click using the same port, and once I load the Single click server I try to connect with my viewer targeting the IP and port where the server is running:
IE: 192.168.0.100::5900
I get an instant error message unable to connect to server. That's it that is all I get as far as an error.
I tired using the Single click server with both RC203, RC205 and currently am running 1.0.1. Same issue with all 3 versions.

Any brainstorms as to my problem here?

Pete,

[mod=494,1148942782]moved to SC[/mod]

[bevtech]

Do you have Norton Antivirus installed on the pcs giving you grief. If so disable the internet worm protection. SC needs port 5500 and the worm protection blocks that port from being accessed.

[redge]

you had difficult to understand that SingleClick from partner computer made a reverse connection over port 5500 to vncviewer listening port 5500 at your side.

remember:
vnc viewer outgoing port 5900 ---> vnc server listening port 5900 (classic UltraVNC Server)
vnc viewer listening port 5500 <--- SingleClick outgoing port 5500

1st , you need lunch vncviewer listening and waiting your customer lunch
2. Singleclick you gave to your customer and their click over and then their a connect to you.

with SingleClick (customer don't touch their don't modify their router )
vncviewer listening singleclick (you) need open to your router open the port 5500 for accept incoming connection of SC of your customer
then your viewer remote support your customer by their own volontary request (their lunched SC)

Anyway, don't confuse UltraVNC Server (Remote control) and SingleClick (remote support) working as inverse.

Remote control --- almost nobody at front of remote computer vnc server (your own computer that you control from anywhere)
remote support --- always someone at front of remote computer SingleClick (customer/friend/family)

anyways,
you really need review and follow the example below:
[topic=3567][/topic]
and then you finally understand how it work, You can create a new SC more complex.

I tired using the Single click server with both RC203, RC205 and currently am running 1.0.1. Same issue with all 3 versions.

Total confusion
SC20.3 is unrelated to UltraVNC 20.5

What I can see, You really did'nt follow anything
except successfully made a direct connection from Ultravnc viewer to Ultravnc server (classic)

[redge]

So I setup the single click using the same port, and once I load the Single click server I try to connect with my viewer targeting the IP and port where the server is running:

Totally wrong

SC use 5500 as default port (outgoing)
vncviewer must listen same port 5500 (incoming)

SC is targeting vncviewer !

1. start vncviewer -listen 5500 (must ready to accept connection of SC)
2. close vnc server and lunch SC outgoing connection
3. SC connected to viewer


Again
[topic=3567][/topic]

[psass]

Just so you know I understand reversal outbound connections and understand what UltraVNC double click is and how it works. What was missing in the entire thing for me was that I had to load up the UltraVNC Viewer in listen mode.
This was the part the I kept looking for and was using the regular viewer icon. So this now works 100% and I thank all that replied to my question.

Many thanks, Pete,

[redge]

I'm happy for you the way you understand the need of vnc viewer -listen
Have a nice remote support

but this solution was already answered to your first post
[topic=6677][/topic]

Start... Run ...
"%programfiles%\UltraVNC\vncviewer.exe" -listen
(mean listen only default port 5500 without any number)

Start... Run ...
"%programfiles%\UltraVNC\vncviewer.exe" -listen 80
(mean, listen only port 80 non standard port and not listen anymore 5500)

[hkeiner]

What was missing in the entire thing for me was that I had to load up the UltraVNC Viewer in listen mode.

I am a newbie and have a few questions regarding the use of SC. I plan to use SC to support my Dad's computer and want to anticipate problems as much as I can before actually trying to use it with my Dad. He has little patience when things don't work the first time.

1) After loading UltraVNC in listen mode on my PC, is it necessary to change the Viewer's configuration in any way? (I ask because when double clicking on the Viewer icon in the system tray, there is a dialoge box that includes "VNC Server" information. This box already contains an IP address from a previous effort to 'connect" to the Server running on the client , which is not the current IP address of my Dad's PC.)

2) Will having an incorrect IP address in the "VNC Server" information box cause problems in "listening" for the SC's connection effort from the client?

3) Should the "VNC Server" information be cleared (blank) when listening for a connection from the SC client?

4) Will the "VNC Server" information be overwritten automatically with the client's IP address when the Listener gets "contacted" by the SC client?

These questions may appear somewhat redundant but sometimes it helps me to be real granular so that I can better understand the answers I may get.

Thanks in advance for any information

[redge]

1) not related to incoming connection and won't affect vncviewer
best way for stop accidental breaking network connection
vncviewer -listen 5500 -noauto -64colors

2) not related to incoming connection

3) No and not necessary and nothing fail

4) No, because is for outgoing connection to vnc server (not incoming to viewer!

[hkeiner]

1) not related to incoming connection and won't affect vncviewer
best way for stop accidental breaking network connection
vncviewer -listen 5500 -noauto -64colors

2) not related to incoming connection

3) No and not necessary and nothing fail

4) No, because is for outgoing connection to vnc server (not incoming to viewer!

Redge,

Thanks for the above response. It helped me increase my understanding of how the 'listen" mode of Viewer works.

I provided a remote user (my dad with a 56k dialup connection) with the SC file and I was able to connect to his PC desktop successfully. However, his PC's response to my mouse/keyboard actions was very, very slow. Often 5-10 seconds delay to each mouse/keyboard action. I changed the quick option in the Viewer's options box to MODEM but it didn't seem to make any difference. It is too slow to be usable. I figure I need to learn a little more about configuration matters. Accordingly, I have the following additional questions.

1) Does changing the "Quick Option" settings for the Viewer (Auto, Ultra, Lan, Medium, Modem, and slow) affect the connection or are they also not related to an incomming connection from SC?

2) If the answer to 1) is that they are not related to an incomming connection, then how can I change the connection speed settings (e.g, set connection for B/W, greyscale, or 8 colors) to improve performance when using SC on a PC with a 56K modem?

3) Would using the the Server/Viewer combination (instead of SC) allow for better configuration choices to improve performance connecting my PC (with a cable mode) to my dad's remote PC (with a 56K modem)?

Note: I considered having my dad install the UltraVnc Video Driver on his PC but when I installed this driver on my PC as a test, it messed up my normal video driver (the screen resolution was stuck on 640 x 480 and was distorted) and I had to reinstall my video card's regular drivers to correct the problem. I don't want to risk messing up my Dad's PC as it is hard for him to deal with such things. Also, my dad's PC is a 1GHZ Pentium 3 with 512MB memory, if that matters.

Thanks in advance if you have any suggestions in this area.

[redge]

1) right, they also not related to an incoming connection from SC

2) "%programfiles%\UltraVNC\vncviewer.exe" -listen -noauto -8greycolors
or other example:
D:\vncviewer.exe -listen -noauto -8greycolors
I use a shortcut with this command line.
so, I'm not worry to lost time how to do on next remote support request.

3) No, due to slowest network speed of 56k.

I never install UltraVNC video driver on any computers friends,
I don't want complaint of my friends. Just help,
I had installed UltraVNC mirror driver only on my own computer.

[hkeiner]

1) right, they also not related to an incoming connection from SC

2) "%programfiles%\UltraVNC\vncviewer.exe" -listen -noauto -8greycolors
or other example:
D:\vncviewer.exe -listen -noauto -8greycolors
I use a shortcut with this command line.
so, I'm not worry to lost time how to do on next remote support request.

3) No, due to slowest network speed of 56k.

I never install UltraVNC video driver on any computers friends,
I don't want complaint of my friends. Just help,
I had installed UltraVNC mirror driver only on my own computer.

Redge,

Thanks for this info. I'll try the "shortcut" method that you suggested. From your comments, I presume that you have connected to remote users with a 56K dialup connections and had reasonable speed in mouse/keyboard actions.

[redge]

From your comments, I presume that you have connected to remote users with a 56K dialup connections and had reasonable speed in mouse/keyboard actions.

acceptable... for 800x600 SC user

Another better responsiveness
tabbed_vncviewer is much better
http://prdownloads.sourceforge.net/ultr ... e?download

[hkeiner]

From your comments, I presume that you have connected to remote users with a 56K dialup connections and had reasonable speed in mouse/keyboard actions.

acceptable... for 800x600 SC user

Another better responsiveness
tabbed_vncviewer is much better
http://prdownloads.sourceforge.net/ultr ... e?download

Redge,

1) You stated "acceptable... for 800x600 SC user" Does this mean that the SC user should set their screen resolution to 800 x 600 before clicking on the SC exe file? If they leave their screen resolution higher (e.g., 1280 x 1024) will this result in slower performance.

2) Does the "tabbed_vncviewer" in listen mode work with SC in the same way the Viewer in listen mode works? That is, can I use the same shortcut parameters you suggested earlier (-listen -noauto -8greycolors)?

Sorry to hit you with so many questions buy you apparently know this stuff very well and your answers are getting me focused on the best solution for my particular situation.

Thanks again....

[redge]

1) I had tested the only their XP with 800x600 screen size over 56k modem
do not change anything to partner computer,
you just need more waiting screen change.
higher resolution, more data to transfer = slower responsive,
lower resolution screen, less data to transfer = higher responsiveness

2) yes, same as vncviewer
http://prdownloads.sourceforge.net/ultr ... e?download
"%programfiles%\UltraVNC\tabbed_vncviewer.exe" -listen -noauto -8greycolors
or
"d:\tabbed_vncviewer.exe" -listen -noauto -8greycolors