Fedora 8, how to get VNC into a Windows XP box working?

Permabanned
Joined
28 Nov 2003
Posts
10,695
Location
Shropshire
One thing I do NEED to get working is VNC, to allow me to view and operate my main Windows PC from my Fedora 8 Linux enabled laptop. With Fedora 8 I can access files via the cabled network, on the Windows PC, which is called emu, but VNC fails to find this PC, which does have a VNC server running. The laptop finds it and runs VNC fine under Windows though. Do I have to do something other than load VNC under Fedora 8 to make it work? Thanks again
 
IIRC you need to enter "vncviewer ip.address.of.windowsbox:n in a terminal.. do it from a terminal and you should see any errors printed up.

Where n is the screen number (usually be 0 or 1 on a windows box).

Ooh, and you would also need to open the port number in Windows Firewall (5900 or 5901 depending..)
 
You can also use rdesktop from linux box and connect straight to Windows builtin remote desktop. Or logmein free edition to control your windows PC from any browser. Both are much faster that VNC as well...
 
You can also use rdesktop from linux box and connect straight to Windows builtin remote desktop. Or logmein free edition to control your windows PC from any browser. Both are much faster that VNC as well...

VNC Free Edition maybe, but not VNC Personal/Enterprise Edition, for which you can get a 30-day trial. The mirror driver is much faster/more efficient than any of the protocols logmein/rdesktop uses.

Plus RDP can't remote the console session, only create new virtual sessions.

Download the trial from http://www.realvnc.com and give it a go.

install vnc server on the machine you want to access and run from a terminal:

vncviewer ipaddr (if on a lan use internal IP, if over the internet you'll need to configure port forwarding and access the public IP)
 
VNC Free Edition maybe, but not VNC Personal/Enterprise Edition, for which you can get a 30-day trial. The mirror driver is much faster/more efficient than any of the protocols logmein/rdesktop uses.

I'm not even going to ask for benchmark proof to see how VNC could possibly be faster, but instead just ask why, why, why would anyone want to pay or trial something when there is perfectly usable, easy, secure and darn fast software already out there - and shipped with Windows by default at that?

Plus RDP can't remote the console session, only create new virtual sessions.

Explain
 
I'm not even going to ask for benchmark proof to see how VNC could possibly be faster

I work for RealVNC and we've commissioned several internal reports for competitor product comparisons, VNC came out on top in most areas, I can try and get you the specifics if you want but it's pretty boring, i'm not going to lie. The problem is that most people are using the legacy version of VNC based on the VNC3 protocol, which is outdated.. other than that people use VNC Free Edition, which although updated to the VNC4 protocol (4.1.2 being the latest FE release) is still an outdated piece of software, it's got several issues, isn't compatible with Vista and depending on bandwith/latency can run like a dog if not configured correctly.

VNC PE/EE on the other hand are in constant active development and have been updated with a multitude of features/fixes/patches.

You can tell i'm giving you the spiel because I work for the company, although I do actually agree/believe it, otherwise I wouldn't be spouting it on a public forum ;)

The only argument against it as far as I can see is the obvious one, that you need to pay for it; which is a very valid point, I wouldn't use it myself if I didn't get it for free ^^


When you 'initiate' a remote desktop connection, it 'creates' a virtual session, you cannot connect to your actual 'Deskop' screen, i.e. screen:0, known as the console session.

VNC on the other hand connects to the console session by default (logmein does this aswell), you're literally viewing the computer as it is, not creating a new virtual session.

This has its good points and bad points. If you actually *want* to create virtual sessions, then VNC isn't for you (not under the Windows platform at least, under Unix you can control the console session aswell as creating multiple VNC sessions)
 
Back
Top Bottom