Hello, have an odd question... i have had VNC installed on my solaris server for over a year now and all of a sudden, i cannot have more that two sessions connected thru VNC at a time. I used to be able to have 8 users. The other problem is someone else installed the VNC server and i cannot seem to find where any of the files are installed at on the server.
just came in one day and now i get the error message on my pc of
Error in TightVNC Viewer, Unsuppoted Protocol /opt/tigntvn on my windows desktop
So, your config is tightvnc on windows to vnc on solaris? I use the free version, and there is no user limit but the 100 ports. I recall times I had to edit 'vncserver' to force it to use TCP because UNIX socket directories had too tight permissions. Are you sure that is your Xvnc on that socket?
How do get to the machine that has your VNC server(s) running? SSH? Check the remote server and see what's listening on ports starting at 6000 and up, maybe up to 6030 or so.
Each VNCserver virtual display needs to open a standard X Windows server display port and listen on it for connections from client processes that want to display on that server. The envval "DISPLAY=host1:8.0" means display 0 on port 6008 on host1, while "DISPLAY=host2:2.1" means display 1 (not normally used) on port 6002 on host2. The most common - "DISPLAY=:0.0" means display 0 on port 6000 on the local host.
If there are no port conflicts, firewall rules could be limiting the available ports.
Yes, each additional user on a host has to consume a port number 5900-5999 for incoming viewer connections, to take X connections on 6000-6099 respectively. A firewall may not be letting your viewer in. Try "netstat -an | grep '\.59[0-9][0-9][^0-9]'" to see users of vnc ports. You can easily get vncserver to use any port, so try a higher one.
this is what i am getting on the netstat. not sure even how to shut down and restart the server. when i try vncserver i get an xauth not found error. so thinking maybe there is a different command to shut down the services.
if i try to bring up the xvnc-inetd:default, it does not enable, it says maintenance mode.
does the above statemnt mean i am running a differnt version of vnc. this was upgraded from a solaris 9 and always ran the tightvnc. we had some database issues and lost a directory for a while but that has since been rebuilt. that was the /opt directory and it now checks without errors.
my question is what is the xfs:default service and is it preventing me from enabling the xvnc?
It looks like another app is using 59?? ports. Does vncserver check for taken ports both 60?? and 59??, if not a vnc bug. Yes, vncserver checks both ports:
#
# GetDisplayNumber gets the lowest available display number. A display number
# n is taken if something is listening on the VNC server port (5900+n) or the
# X server port (6000+n).
#
sub GetDisplayNumber
{
foreach $n (1..99) {
if (&CheckDisplayNumber($n)) {
return $n+0; # Bruce Mah's workaround for bug in perl 5.005_02
}
}
die "$prog: no free display number on $host.\n";
}
#
# CheckDisplayNumber checks if the given display number is available. A
# display number n is taken if something is listening on the VNC server port
# (5900+n) or the X server port (6000+n).
#
sub CheckDisplayNumber
{
local ($n) = @_;
socket(S, $AF_INET, $SOCK_STREAM, 0) || die "$prog: socket failed: $!\n";
eval 'setsockopt(S, &SOL_SOCKET, &SO_REUSEADDR, pack("l", 1))';
if (!bind(S, pack('S n x12', $AF_INET, 6000 + $n))) {
close(S);
return 0;
}
close(S);
socket(S, $AF_INET, $SOCK_STREAM, 0) || die "$prog: socket failed: $!\n";
eval 'setsockopt(S, &SOL_SOCKET, &SO_REUSEADDR, pack("l", 1))';
if (!bind(S, pack('S n x12', $AF_INET, 5900 + $n))) {
close(S);
return 0;
}
close(S);
if (-e "/tmp/.X$n-lock") {
warn "\nWarning: $host:$n is taken because of /tmp/.X$n-lock\n";
warn "Remove this file if there is no X server $host:$n\n";
return 0;
}
if (-e "/tmp/.X11-unix/X$n") {
warn "\nWarning: $host:$n is taken because of /tmp/.X11-unix/X$n\n";
warn "Remove this file if there is no X server $host:$n\n";
return 0;
}
if (-e "/usr/spool/sockets/X11/$n") {
warn("\nWarning: $host:$n is taken because of ".
"/usr/spool/sockets/X11/$n\n");
warn "Remove this file if there is no X server $host:$n\n";
return 0;
}
return 1;
}
It'd be interesting to see the lsof of those ports, who is using them for what, but you need to be root for that (to see all user info). You'd think 100 ports would be enough.