unable to connect to socket connection refused 111: Tiger vnc
Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
unable to connect to socket connection refused 111: Tiger vnc
hi,
installed tigervnc server on centos 6 64bit which one of my virtual machine on rhel6 host. when i try to connect centos vm from rhel6 using tiger vnc viwer it says
"unable to connect to socket connection refused 111". i added root user in /etc/sysconfig/vncserver, started the vncserver on centos, disbabled SElinux. but same error. Please help me.
thnks in adv.
I know this is old, but when I ran into this issue today this was one of the top posts that came up.
Here is what I did on a SL 6.2 Box
1. Turn on VNC Server.
Code:
chkconfig vncserver on
2.
Code:
service vncserver start
I got a no displays configured error.
a. run as the user you want to use for vnc
Code:
vncserver
b. it will set up your password and files.
3.
Code:
service vncserver start
4. Now I was getting the error that the OP mentions.
a. unable to connect to socket connection refused 111: Tiger vnc
5. I searched around and found some folks saying to turn off the firewall. I had already enabled 5900 - 5910 on the firewall. So I decided to check what port VNC Server was using.
netstat -putna |grep LISTEN |grep vnc should do the trick
but frankly, the right solution is `vncserver -list` where every number returned should be added to 5900 to get the port, or fed directly to vncviewer as the display number
netstat -putna |grep LISTEN |grep vnc should do the trick
but frankly, the right solution is `vncserver -list` where every number returned should be added to 5900 to get the port, or fed directly to vncviewer as the display number
That is one thing that is strange about this I don't actually connect using the 6001 port that had to be added to the firewall rules. It just had to be added before I could connect on 5900 +. I must admit that I have not done the proper research on the vncserver -options just went with a quick down and dirty port listing. Thanks for the reply it is easier to remember then my grep command.
for VNC you need to open a range of ports, starting at 5900 and ending at 5900 + the amount of sessions you intend to allow. 6001 is simply session number 101
Yeah, but the port I connect on is one I already had open and cant actually connect on 6001 so I am wondering if it is some sort of loopback session, I couldn't even guess if such a thing exists. Once I allowed it through my firewall I could connect on one of the previously opened ports 5901.
Okay further reading leads me to believe being lazy and using the out of the box configs was my issue. Evidently you can limit the session to be what port you like in the config, by leaving it open it must have been trying to open a predefined number of sessions to flip to as users connect. Kind of like child servers waiting to be used.
just turned vncserver on here, and also got two ports - for display :2 I ot 5902 and 6002. Guess one is used for encrypted data and the other for non-encrypted. Same as with spice, but I'm just guessing here, need to look at the code or the internals documentation to verify this assumption
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.