search for: 590n

On my 'older' systems that include Centos 5.5 and Fedora 12, vncserver is running on ports 580n where n is defined by userid in the /etc/sysconfig/vncserver I just spent a bit of time getting it working on my new Centos 6.3 server and found it listening on ports 590n. When did the change occur? And guess I should test out where it is on Fedora 17...

...HIS SERVICE if your local area network is # untrusted! For a secure way of using VNC, you should # limit connections to the local host and then tunnel from # the machine you want to view VNC on (host A) to the machine # whose VNC output you want to view (host B) # # [user at hostA ~]$ ssh -v -C -L 590N:localhost:590M hostB # # this will open a connection on port 590N of your hostA to hostB's port 590M # (in fact, it ssh-connects to hostB and then connects to localhost (on hostB). # See the ssh man page for details on port forwarding) # # You can then point a VNC client on hostA at vncdispla...

...the Centos wiki instructions for doing an install via vnc: http://wiki.centos.org/TipsAndTricks/VncHeadlessInstall CD is all burned and ready to go. I then thought about the viewer settings particularly the port number and firewall rules. When I connect vncviewer to a vncserver it uses port(s) 590n where n is the display number. OK, is that what happens when a server connects back to a -listen viewer? Seems not. According to the man page, it seems the default is port 5500, so I have to open up this port on the 'client' system and of course allow it through my internal firewall...