VNC remote control of Desktop

[Beach]

Hey PB, I know the topic is regarding VNC remote access - but that free remote control service service called LogMeIn I mentioned above works really well here behind our corporate firewall (which only allows ports 80,443, and 21). I'm not sure how secure everything is but here is the process.

- You log in at the site which is SSL encrypted (all activity is SSL based).
- You can see all PC's you have added, or you can create a new one.
- The remote client starts if you select a PC (Java or ActiveX client).
- The client then asks you for the username and password for the desktop to be controlled. This is the username and password on the remote PC.
- You can adjust the remote screen to maximized bandwidth.

Also, the remote desktop put a label on the screen stating that someone is controlling that PC... Here is a screen shot if you want to see it in action:

http://www.penguinbyte.com/apps/pbwebst ... screen.jpg (76k)

[TerryHough]

@PB

The problems you have mentioned and some of the replies prompted me
to look back at my installtion. I didn't have some of the tab, etc.
mentioned. I was using RealVNC vs. 3.3.

FYI, I am running Win98SE on all my usual machines. Do have a couple
of WinXPHome that I am successful with though.

Downloaded and installed Vs 4.0. While I can connect successfully, the
screen paints are horrible and unusable. It is impossible to see the
server's screen enough to actually control it. So, back to Vs 3.3 for me.

Downloaded the latest TightVNC and installed it. I immediately had
connection failures between the same machines that RealVNC 3.3 had
just connected easily too. Once I did get connected, the server locked
up upon the Viewer cancelling the connection. Uninstalled that quickly.

I had a reference to another version, Ultr@VNC. Downloaded and
installed it. There are numerous more features in it, including the ability
to transfer files (missing in the others) and nice things like speed
adjustments, screen blankers, a chat system, a new optional GUI control
line. These features come at a price of about twice the footprint on the
HD and installation size (still not huge).

Ultr@VNC takes a bit longer to connect, but once connected is substantially
faster with the Viewer controlling the Server. Cursor motion is remarkably
improved.

Looks like Ultr@VNC is my new tool for remote control.

You might want to take a look at it. http://ultravnc.sourceforge.net/

Good luck,
Terry

[PB]

> Ultr@VNC takes a bit longer to connect, but once connected is substantially
> faster with the Viewer controlling the Server. Cursor motion is remarkably
> improved.

I was just able to successfully connect to tinman's PC from my home, using
the same VNC Viewer I was using (unsuccessfully) at work, so it seems my
work PC is doing too good of a job of preventing outbound connections.

I will download and try Ultr@VNC then, but I doubt it'll work too.

[Pupil]

I was just able to successfully connect to tinman's PC from my home, using
the same VNC Viewer I was using (unsuccessfully) at work, so it seems my
work PC is doing too good of a job of preventing outbound connections.

I will download and try Ultr@VNC then, but I doubt it'll work too.

While you were at it did you get tinman to try to connect to your computer?

[TerryHough]

Pupil's question is a good one... that is the direction you need to test so you can see if your Server is accepting connections.

Using VNC Viewer to connect to Tinman's system proves that his Server is accepting connections and that your Viewer can find it only.

You need to prove that your Server can accept connections. If it can't then you don't need to blame your works systems.

[tinman]

PB tried to connect from his work PC to my home PC and it didn't work. He tried to connect from his home PC to my home PC and it did work. Not saying it's conclusive, but I had everything open so it's likely his outgoing connection from work is the problem.

I'd be happy to try to connect to his home PC from mine >)