Help Needed: SC and Repeater (almost there?)

[remoter]

Hello.

I think I'm closer to getting this to work, but I need some more pointers. I'm using a Windows 7 laptop for the viewer and a Windows XP desktop for the server.

I created the .exe file by uploading the files from custom.zip. The helpdesk.txt has the following:

~~~~~~~~~~~~
[HOST]
Support Agent1 (encryption)
-plugin -id 1234 -connect REPEATER-ADDRESS:5500 -noregistry

(Note: I'm using a different id)
~~~~~~~~~~~~

The repeater has the following properties:
Viewer Port: 5901
Server Port: 5500


In the custom.zip uploaded to create the .exe file, I've included the downloaded 'MSRC4Plugin.dsm' file and a copy of the rc4.key file I have on the laptop and use for the viewer (non-SC).

On the Online Creator page (http://www.uvnc.com/pchelpware/sc/creator.html), I used the "UltraVncSC update 2009" version to create the custom.exe file, ALTHOUGH I had no clue what '[DIS_UAC]' is so I didn't use it.

I'm not sure which of the 3 options on that page to use anyway - so advice needed about that too is appreciated.

I copied the (renamed) .exe file to the XP machine and started it (double-clicked) and it shows in the tray.

As far as the viewer on the W7 machine is concerned, I started it via 'Run' using "C:/Program Files/UltraVNC/vncviewer.exe" -dsmplugin msrc4plugin.dsm -listen 5901 which worked because the icon is in the tray and hovering over it shows it is listening.

I then clicked "New Connection" and in the VNC Server field, I put 'ID:1234' which is the same ID as that in the helpdesk.txt field. I checked the plugin field and selected the plugin 'MSRC4Plugin.dsm'. For the proxy/repeater field, I put 'REPEATER-ADDRESS:5500'.

It doesn't connect so I'm not sure what to do to get this to work.

Please advise.

Thanks.

[YY]

I created the .exe file by uploading the files from custom.zip. The helpdesk.txt has the following:

~~~~~~~~~~~~
[HOST]
Support Agent1 (encryption)
-plugin -id 1234 -connect REPEATER-ADDRESS:5500 -noregistry

(Note: I'm using a different id)
~~~~~~~~~~~~

In the custom.zip uploaded to create the .exe file, I've included the downloaded 'MSRC4Plugin.dsm' file and a copy of the rc4.key file I have on the laptop and use for the viewer (non-SC).

Basically what you had done are corrected.

But the submit of 'MSRC4Plugin.dsm' is not necessary, as the "UltraVncSC update 2009" always offers its own MSRC4Plugin.dsm. The one inside the zip file will simply be ignored.

The repeater has the following properties:
Viewer Port: 5901
Server Port: 5500

It's OK.
Make sure that:
- Mode "Enable Mode II" box is checked, and
- Enter 0 at "Restrict access to server port"

I had no clue what '[DIS_UAC]' is so I didn't use it.
UAC is a feature in Vista.

If your SC.exe is running on XP, it is OK not using it.

I'm not sure which of the 3 on that page to use anyway - so advice needed about that too is appreciated.

Quite a lot ...., for best of what I learnt, here are some of their features.
1. RC23 -- The oldest one of the three available online creater. It always provide MSCR4Plugin.dsm (ver.1.1.6) as the encryption plugin.

2. REL 1.0 -- A revised version from RC23, add new options in helpdesk.txt, such as:
　　[ENTERCODE], [DEBUG],
　　-- add support of Mirror Driver,
　　-- allow user submit their own DSMPlugin,
　　-- Change of the connection retry characteristic (no more retry if fail to establish connection)

3. UltraVncSC update 2009 -- the latest creator that support Vista/Win7
　　-- It always provide MSCR4Plugin.dsm (ver.1.2.4) as the encryption plugin
　　-- add new option [[DIS_UAC] to disable the UAC on Vista


and even a lot I forget to mention, or I don't know .......

As far as the viewer on the W7 machine is concerned, I started it via 'Run' using "C:/Program Files/UltraVNC/vncviewer.exe" -dsmplugin msrc4plugin.dsm -listen 5901 which worked because the icon is in the tray and hovering over it shows it is listing.

You don't need to start the viewer in listening mode. What you should do is:
1. You must be using the same DSMPlugin and key as that using on the SC.exe, and putting them on the same folder as vncviewer.exe.
　　the plugin -- As you used "UltraVncSC update 2009" creator, then you must use MSCR4Plugin.dsm (ver.1.2.4), which is bundled with UVNC 1.0.8 package.
　　the key -- so you created it, put a copy with the viewer.

2. Double click the viewer to open it GUI, input as the picture (replaced with the real id, ip), then click "Connect"

[remoter]

Thanks YY for your reply.

Make sure that:
- Mode "Enable Mode II" box is checked, and
- Enter 0 at "Restrict access to server port"

I am testing the repeater feature with a public repeater therefore, I don't have it setup on either of my PC's.

I saw what I have quoted here on the 'Repeater' page (http://www.uvnc.com/addons/repeater.html) in the Repeater Settings area. Is this something I need to set and/or download?

I'm using UltraVNC v.1.0.8.2 x64. The key is the same for both this viewer (Windows 7) and the created '.exe' file. The error I'm getting after 'Connect' is 'Negotiate Protocal Version'. Could it be the difference between the viewer's x64 and SC's 32-bit? Or is it because I don't have the repeater software?

Thanks.

[YY]

I am testing the repeater feature with a public repeater therefore, I don't have it setup on either of my PC's.

I saw what I have quoted here on the 'Repeater' page

If you use the public repeater from uvnc.com, it should be configured to support mode II operation, 5500 for "listen to server", and 5901 for "listen to viewer"
Or did you use some other repeater else?

Is this something I need to set and/or download?

Of course, it is better if you can carry the test with your own repeater, so that you can have everything under your control, and also able to view the repeater log to monitor if the repeater pickup the connection as you expect.

The error I'm getting after 'Connect' is 'Negotiate Protocal Version'. Could it be the difference between the viewer's x64 and SC's 32-bit?

I don't have experience with x64 Windows, but "'Negotiate Protocal Version" is not an error, but if the viewer stop here then most likely something is wrong.


Can you try to use the 32bit vncviewer to test once again? It should be able running on 64bit system.

Also, make sure the firewall not blocking the VNC signal.

[remoter]

Thanks for your reply, YY.

Yes, I'm using a repeater from uvnc.

Right now, I have not tried to create my own repeater. I looked at the page and it looks like it might take a bit for me to get it configured as this area is rather new to me.

I installed the 32-bit v.1.0.8.2 WITHOUT uninstalling the 64-bit version. During the install, it asked if to remove the server and replace (with 32-bit) so I chose to remove and use the 32-bit. I tested the new installation by communicating with the XP machine via 192.168... (using encryption) and it still worked.

After stopping the server on the XP PC (the icon no longer showed in the tray), I then went back to enable the SC app after recreating it without the plugin file just to be sure there is no interference with it. It remained in the tray until I tried connecting with it. Once I got the message re: Negotiating Protocal Version', the icon disappeared. I had used ID:1234 instead of 192.168... and enabled the proxy/repeater in the viewer.

So, I assume that it is very close to connecting if by communicating with the server, the icon disappeared when the '...Protocal...'message appeared on the Windows 7 PC.

Any other thoughts?

Thanks.

EDIT: Regarding the firewall, I'm trying to configure this to support other machines at some point. From what I read about the SC app, it seemed as though I wouldn't need to do any firewall-type work when using the repeater. Is that not true?

[remoter]

Hello again YY.

Here is an image of the message received (a 2nd window opened after the communications window):

[IMG=http://img694.imageshack.us/img694/995/ultravncviewermessagebo.jpg][/IMG]

Thanks.

[remoter]

Hello again.

FYI-

I was able to get PcHelpWare to work with the uvnc repeater before I tried configuring SC.

I also have port forwarding setup on the XP PC but they are different ports than what I'm using with the repeater.

Q: Could either of these cause the 'Connection Failed - Invalid Protocol' issue?

Thanks.

[YY]

I was able to get PcHelpWare to work with the uvnc repeater before I tried configuring SC.

If PcHelpWare worked, then most likely the firewall will allows SC.exe too (from the points of the ports used), as the two program using the same ports.

I also have port forwarding setup on the XP PC but they are different ports than what I'm using with the repeater.

Q: Could either of these cause the 'Connection Failed - Invalid Protocol' issue?

I don't the port forwarding may causing any problem. In fact, neither SC.exe nor PcHelpware require port forwarding when making connection with repeater at mode II (i.e. using ID)

I just try to make a connection by using the uvnc.com as repeater, and my SC.exe fail to connect to it. I suspect your problem is caused by it.

You may try using other public repeater for your test, see [topic=9600]Other Repeaters besides uvnc.com[/topic].
I have tried repeater01.ultravnc.info and vserver.homeftp.org, both work perfect.

Note: be remind that vserver.homeftp.org using 5900 (not 5901) as viewer port.

My suggestion:
- first try non-encrypted connection.
- remember the ID allows number only.

[remoter]

Thanks as usual for your reply, YY.

Regarding PcHelpWare where I mentioned that it worked, let me clarify as I forgot what the problem was when I replied here.

It did connect and it uses 'repeater01.uvnc.com' but upon loading, it gets as far as displaying the server's screen saver but locks up before displaying the icons on that desktop screen. I hadn't applied the 2 dll patches on the PcHelpWare download screen but will soon to see if that helps. But the GOOD NEWS there is that it was able to make the connection.

You mentioned that if it can make the connection with PcHelpWare, then it should be able to with SC. That's good to know as I am using the same repeater.

I did notice on the PcHelpWare Customization page that it had the following examples for the helpdesk.txt file similar to that used with SC EXCEPT their [HOST] examples are different as SC shows the use of the '-plugin' and '-noregistry' params (NOTE: I have not used a customized helpdesk.txt with PcHelpWare, yet):

~~~~~ per PcHelpWare Customization page ~~~~~

[HOST]
Internet support (Encrypted Direct Connection)
-connect 192.168.1.102:5500

[HOST]
Internet support (Encrypted Repeater Connection)
-connect uvnc.com:5500 -id 543

[HOST]
Internet support (Autorecon Encrypted Repeater Connection)
-connect uvnc.com:5500 -id 543 -autoreconnect

[HOST]
Internet support (Proxy Encrypted Repeater Connection)
-connect uvnc.com:5500 -id 543 -proxy

~~~~~~~~~~~~~

In my helpdesk.txt file for SC, I have:

[HOST]
Support Agent1 (encryption)
-plugin -id 1234 -connect REPEATER-ADDRESS:5500 -noregistry

Might there be something here I can change to get past that 'Invalid Protocol' message and therefore connect? Does it have anything to do with the '-noregistry' param?

I see that you were able to get the same repeater I'm using to work so it must be something else I'd think.


Thanks.

[YY]

PcHelpWare and SingleClick are two different products. Although they both keep the config. info in a file named "helpdesk.txt", but has no relation of the syntax used.

So don't use the example of the PcHelpWare syntax as a reference for you SC.exe helpdesk.txt.

Back to your case, I have no other idea why your SC.exe fail to make the connection. Just to sum up my procedure the test as follow:

1. To create a SC.exe using the repeater "repeater01.ultravnc.info"
or "vserver.homeftp.org". For testing purpose, don't use excryption. The content of helpdesk.txt is like following:

=================
[HOST]
Support Test (w/o encryption)
-id 12341357 -connect repeater01.ultravnc.info:5500 -noregistry

================
　　Note: Use a very special id to avoid the collision with other user


2. When you get the created SC.exe, you can test the connection. YOU CAN DO THE TEST WITH YOUR OWN PC, that is both SC.exe and VNCviewer running on your pc

3. Start your viewer with the matched setting, as bellow:



4. To start the connection:
　　- First connect the viewer to the repeater,
　　- then connect the SC.exe
　　- Make sure the firewall will not block the outbound connection signal.
　　- Make sure the antivirus/antispy program will not stop the running of the two program.
　　- If the UAE (Vista) ask, you should instruct it to allow the program to run.


Hope this can help.
If you are still not able to make a sccuessful connection. I'm out of idea.

[remoter]

Thanks YY, as you are a gem for providing so much info.

I hope to try this tomorrow as it's been a busy couple of days.

I'll let you know the results.

Thanks again!

[redge]

I last is too complicate, you can choice another solution, very easy to use.
[topic=6750][/topic]

[remoter]

4. To start the connection:
　　- First connect the viewer to the repeater,
　　- then connect the SC.exe
　　- Make sure the firewall will not block the outbound connection signal.
　　- Make sure the antivirus/antispy program will not stop the running of the two program.
　　- If the UAE (Vista) ask, you should instruct it to allow the program to run.

This did it, YY! (plus the detail you also provided in this same and earlier replies that confirmed the setup and including what you previously said about the 'Negotiate Protocol Version' message was not an error message... )

Here's what I found out:

For the SC application: On the Windows 7 PC, I started the UltraVNC viewer with the repeater box checked and 'ID:1234' in the 'VNC Server' box AND clicked 'Connect'. While it was waiting for a connection, it shows 'Negotiate Protocal Version'.

Then, I started SC custom exe file on the Windows XP machine and it shows 'WinVNC - listening' when hovering over it.

On the W7 PC, immediately after the SC exe file was started, a small message window popped up. The window was entitled, 'Accept Incoming SC connection' and the details showed the current user, IP of the machine (192.168...), etc.

Once 'Yes' is clicked, the window loaded.

NOTE: Had I started SC on the server PC before clicking 'Connect' in the viewer, then the error message appeared. Also, had I just started the viewer without clicking 'Connect' and then started the SC app, it had the same effect of starting the SC app before the viewer and therefore produced the error.


I also have UltraVNC installed on both machines. When I use the XP machine as the server, I normally have WinVNC waiting before I start the viewer. I haven't tried it with the viewer started first, yet, to know whether the order matters.

So, thanks so much, YY!


@redge - Thanks to you, also. I looked at Teamview again and may consider it in the future. The reason I really wanted to get either SC or PcHelpWare working is because it allows me to create my own customized interface. Thanks again!