SC + Repeater

[JGraham]

Hey all,

First of all, excellent product from what I've seen so far. I have a few questions I was hoping you all could clear up for me though.

We are looking to do remote support for our clients. We currently use Symantec PC Anywhere, but would love to switch over to SC. Let me go over what I assume is right, and maybe someone can correct me if I'm wrong. We have 4 techs who have internal IP address' for their machines. What I would want to do is create a SC file that would allow our clients to click on the name of their support tech to establish a support connection. I am assuming that I can build SC with multiple host files which would route to our Repeater behind our firewall and the Repeater would route the connection to the internal workstation depending on what support tech our client selected. I've read through a lot of the walkthoughs on the forums, and they are all pretty helpfull, I just want to make sure I have my thinking right.

I've been testing locally using our internal ip address' with encryption and haven't had any problems, but for some reason I can't use our external ip address of our router. I've forwarded the correct ports to the correct machine, and I've triple checked them. I can connect to the server when I build SC with the internal ip, but not with the external so I know it's not a server issue. Any other thoughts on this would be helpfull too!

Thanks again in advance for the help!

Best Regards,
Josh

[Ipsec]

I've been testing locally using our internal ip address' with encryption and haven't had any problems, but for some reason I can't use our external ip address of our router. I've forwarded the correct ports to the correct machine, and I've triple checked them. I can connect to the server when I build SC with the internal ip, but not with the external so I know it's not a server issue. Any other thoughts on this would be helpfull too!

Have you done a port scan externally on your IP address and ensured it is open? - do the ports show open on those scans (either web based and or inet based)

I would say part of the issue is you could be using the same port for all 4 techs. If you arent then thats not the problem yet you can use what is called the "repeater" to try this. I havent done it but have read others saying they were successfull.

I would try to build one SC for one tech's machine - run the port scan (either from sheilds up or from another inet connection verify the port is open) then attempt SC. Until you verify that the port is open you may be hitting a brick wall. Just my opinion though.

[JGraham]

Ipsec,

Thanks for the response. Actually I haven't set up everything like I have described yet. I've just been doing the initial testing on one machine. I noticed a couple problems that I am going to try to smooth over and I will let you know how everything turns out. Thanks again for the help.

Josh

[JGraham0903]

One more thing. I've been testing with 1.0.0, and haven't had any problems. I went ahead and installed 1.0.1 with the DSM plugin, created and renamed the key, etc., and started it in listening mode using the command line. When I open up the viewer everything looks right (the plugin is selected and checked), but when I click on options it throws the error "The plugin cannot be loaded, please check it's integrity."

Also, when I try to connect I get the same error. I built SC with the UltraVncSC based on REL1.00 (TEST) creator, and I've been following the directions from this post: [topic=3278][/topic] The directions worked fine when I was using 1.0.0, but not with 1.0.1. Is there something that I am doing wrong? Thanks!

Edit (Again ):
I noticed a response in this post: [topic=3386][/topic]

An extra space between the -dmsplugin and the msrc4plugin_noreg.dsm in the shortcut command line will also cause the error about checking the name integrity. Found that one out the hard way. Seems like that is a command line parsing error in vncviewer executable.
_________________
Ralph

Has this been addressed yet? Is there a workaround?

Fixed
I realized that I wasn't running the command from the UltraVNC directory. To initialize UltraVNC in listening mode with the DSM plugin you have to run the "vncviewer -dsmplugin MSRC4Plugin_NoReg.dsm -listen" command from inside the working VNC directory. (I ran it from Start > Run) Sorry is this has been addressed before. Oh, and I'm sure that it doesn't make a difference but I went ahead and started using the DSM version 1.1.9.5 plugin. Hope this will help someone else out. Moving on....

[JGraham0903]

Edit: Everything seems to be in order now. Excellent program! Thanks again!