Re: RealVNC
- From: "Luka Manojlovic" <luka@xxxxxxxxxxxxxxxxxxx>
- Date: Fri, 24 Aug 2007 20:24:06 +0200
That is not correct.
VNC server that runs on the "machine you want to connect to" listens on port
5900.
Listener "VNC Viewer in listening mode" listens on port 5500. The connection
is established by clicking on the VNC server on the other machine and "Add
new client".
I suggest that your vendor uses RealVNC Viewer in listening mode and your
client in the network installs RealVNC server. After that just right-click
on the icon in tray and do "Add new client" insert the IP of your vendor and
vendor will se the client's desktop without extra ISA rules.
This way was "invented" to bypass firewall setup.
Luka
"Iakov" <Iakov@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C7305B0F-0063-49AA-8643-B42723D5D733@xxxxxxxxxxxxxxxx
A vendor wants to remotely train an employee via VNC. Two ports (VNC-in
and
VNC-out on port 5500) have been opened via the Services screen of CEICW,
but
they still can't access the employee's desktop.
The employee installs a small VNC client via the vendor's website. The
client places an icon in the Notification Area (system tray) and pops
"Trying
to connect to remote assistant." The vendor's VNC is supposed to gain
access
to the employee's desktop, but that doesn't happen. Instead, the
employee's client's popup changes from "Trying to connect to remote
assistant" to "WinVNC Listening," and then the client terminates after
about 5 minutes.
Has anybody used RealVNC successfully behind SBS 03 Premium with ISA 04?
The Internet feeds straight into the external NIC and the employee
connects
to the internal NIC via a switch. Thank you.
.
- Follow-Ups:
- Re: RealVNC
- From: Iakov
- Re: RealVNC
- From: Claus
- Re: RealVNC
- Prev by Date: Re: External NIC keeps getting registered in internal DNS zone
- Next by Date: Re: RealVNC
- Previous by thread: Allow some users to modify GAL
- Next by thread: Re: RealVNC
- Index(es):
Relevant Pages
|
