Using SC with Windows 2000 Terminal Server

deborahfarrell · Post by **deborahfarrell** » 2006-05-03 06:31

I apologize in advance if this has been answered previously or is addressed in the documentation. I did search the forums but found nothing.

We would like to use VNC SC to support our clients remotely. I installed and configured it successfully on a server at my office. However, we would also like to be able to use it when we are working in the field. We have terminal services access to the server where VNC is installed, but the notifications only pop up on the "console" session. Is there any way around this?

Thanks in advance,
--deborah

rmoller · Post by **rmoller** » 2006-05-03 10:04

If the problem is the popup just after installation, then try searching for fastpush.

If you want to do something yourself, then you can avoid the popup by following this recipe:

Preparation in advance:
(optionally run UltraVncDriverSetupSilent /verysilent)
Install and configure manually a standard (Ultra)VNC server.
Set default VNC settings incl password.
Export HKLM\Software\ORL subtree to, say ORL.REG.
Save ORL.REG for future remote installations.

Remote install:

(optionally run UltraVncDriverSetupSilent /verysilent)
Copy VNC directory to new server.
winvnc -install
regedit /s ORL.reg
net start winvnc

Fastpush does the same thing cooler and slicker, if you get it to work.

Rasmus Møller

deborahfarrell · Post by **deborahfarrell** » 2006-05-03 15:30

Thanks for the help. I think I was not very clear though.

When the client downloads and runs the executable, they double click the name of the person they want to connect to, and there should be a message on the terminal server (which is running the viewer in listen mode) like this: "so and so would like to connect". That message is not showing up for us in our terminal services session. It is instead showing up on the desktop of the locally logged in user.

It looks like fastpush is designed to handle installation and initial configuration issues, but this is more of a functionality issue. Has anyone ever run into this before?

Thanks in advance,
--deborah

kaldag · Post by **kaldag** » 2006-05-04 19:49

Have you tried using the repeater. You can create multiple ID sessions on the repeater and have your support people listen for those ID's. I use the repeater when I am away from the office and need to get into a customers computer.

Ken

deborahfarrell · Post by **deborahfarrell** » 2006-05-04 20:07

Thanks, I will give that a try.

--deborah

Dwalf · Post by **Dwalf** » 2006-05-06 10:41

deborahfarrell wrote:Thanks, I will give that a try.

--deborah

Why dont you just add another user say called

Support - Jon = Work Desktop
Support - Special = Terminal Server

When client calls tell him to connect to Support Special
I think only one connection will work at a time.
Mind you i never tried this myself so dont know if it will work.
or you could setup your router to forward to your dekstop pc's
dratek and cisco come to mind.

The way i work away form the office was to install another product on my desktop pc ... I know these guys are going to shoot me if i say what it is ....log--in
and then connect to my pc and operate SC from anyware in the world with out over complecating things.

BIG NOTE.. watch what is open on your firewalls. only open what needs to be open. Lock down everything else and if you cant restrict to IP's
Read my security topic and you will see why.

Dwalf