Need some pointers here. I've got CentOS 4.4, and I want to control my OSX 10.4.9 box via VNC. It connects, and I get a little dot for the mouse cursor, but just a black screen. I can see the mouse controlling the OSX desktop... Here's the output when I start in a terminal:
[d@f ~]$ vncviewer VNC server supports protocol version 3.889 (viewer 3.3) VNC authentication succeeded Desktop name "xxxxxxxx" Connected to VNC server, using protocol version 3.3 VNC server default format: 32 bits per pixel. Most significant byte first in each pixel. True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0 Warning: Cannot convert string "-*-helvetica-bold-r-*-*-16-*-*-*-*-*-*-*" to type FontStruct Using default colormap which is TrueColor. Pixel format: 16 bits per pixel. Least significant byte first in each pixel. True colour: max red 31 green 63 blue 31, shift red 11 green 5 blue 0 Using shared memory PutImage ShmCleanup called [d@f ~]$ vncviewer --version TightVNC viewer version 1.2.9
Are you running Vine Server (*OSXvnc*)http://sourceforge.net/project/downloading.php?group_id=64523&filename=VineServer2.1.dmgon your mac?
http://www.redstonesoftware.com/products/vine/server/vineosx/index.html http://www.redstonesoftware.com/downloads/index.html
JC
On 3/21/07, David A. Woyciesjes david.woyciesjes@yale.edu wrote:
Need some pointers here. I've got CentOS 4.4, and I want tocontrol my OSX 10.4.9 box via VNC. It connects, and I get a little dot for the mouse cursor, but just a black screen. I can see the mouse controlling the OSX desktop... Here's the output when I start in a terminal:
[d@f ~]$ vncviewer VNC server supports protocol version 3.889 (viewer 3.3) VNC authentication succeeded Desktop name "xxxxxxxx" Connected to VNC server, using protocol version 3.3 VNC server default format: 32 bits per pixel. Most significant byte first in each pixel. True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0 Warning: Cannot convert string "-*-helvetica-bold-r-*-*-16-*-*-*-*-*-*-*" to type FontStruct Using default colormap which is TrueColor. Pixel format: 16 bits per pixel. Least significant byte first in each pixel. True colour: max red 31 green 63 blue 31, shift red 11 green 5 blue 0 Using shared memory PutImage ShmCleanup called [d@f ~]$ vncviewer --version TightVNC viewer version 1.2.9
-- --- David Woyciesjes
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Justin Cataldo wrote:
On 3/21/07, *David A. Woyciesjes* <david.woyciesjes@yale.edu mailto:david.woyciesjes@yale.edu> wrote:
Need some pointers here. I've got CentOS 4.4, and I want to control my OSX 10.4.9 box via VNC. It connects, and I get a little dot for the mouse cursor, but just a black screen. I can see the mouse controlling the OSX desktop... Here's the output when I start in a terminal: [d@f ~]$ vncviewer VNC server supports protocol version 3.889 (viewer 3.3) VNC authentication succeeded Desktop name "xxxxxxxx" Connected to VNC server, using protocol version 3.3 VNC server default format: 32 bits per pixel. Most significant byte first in each pixel. True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0 Warning: Cannot convert string "-*-helvetica-bold-r-*-*-16-*-*-*-*-*-*-*" to type FontStruct Using default colormap which is TrueColor. Pixel format: 16 bits per pixel. Least significant byte first in each pixel. True colour: max red 31 green 63 blue 31, shift red 11 green 5 blue 0 Using shared memory PutImage ShmCleanup called [d@f ~]$ vncviewer --version TightVNC viewer version 1.2.9Are you running Vine Server (/OSXvnc/)
http://sourceforge.net/project/downloading.php?group_id=64523&filename=VineServer2.1.dmg
on your mac?
http://www.redstonesoftware.com/products/vine/server/vineosx/index.html http://www.redstonesoftware.com/downloads/index.html
JC
No, I just enabled the built-in Apple Remote Desktop. As suggested here: http://www.macminicolo.net/Mac_VNC_tutor.html
Ah I see. Well that should work. It's obviously connecting since you get the dot.
I've had similar issues with TightVNC before. It sits for ages saying it is doing the initial screen draw, but never connects.
I'd suggest trying RealVNC (realvnc.com).
*VNC Free Edition for Linux (x86) http://www.realvnc.com/cgi-bin/download.cgi
*JC* * On 3/22/07, David A. Woyciesjes david.woyciesjes@yale.edu wrote:
Justin Cataldo wrote:
On 3/21/07, *David A. Woyciesjes* <david.woyciesjes@yale.edu mailto:david.woyciesjes@yale.edu> wrote:
Need some pointers here. I've got CentOS 4.4, and I want to control my OSX 10.4.9 box via VNC. It connects, and I get a little dot for the mouse cursor, but just a black screen. I can see the mousecontrolling
the OSX desktop... Here's the output when I start in a terminal: [d@f ~]$ vncviewer VNC server supports protocol version 3.889 (viewer 3.3) VNC authentication succeeded Desktop name "xxxxxxxx" Connected to VNC server, using protocol version 3.3 VNC server default format: 32 bits per pixel. Most significant byte first in each pixel. True colour: max red 255 green 255 blue 255, shift red 16 green8
blue 0 Warning: Cannot convert string "-*-helvetica-bold-r-*-*-16-*-*-*-*-*-*-*" to type FontStruct Using default colormap which is TrueColor. Pixel format: 16 bits per pixel. Least significant byte first in each pixel. True colour: max red 31 green 63 blue 31, shift red 11 green 5blue 0
Using shared memory PutImage ShmCleanup called [d@f ~]$ vncviewer --version TightVNC viewer version 1.2.9Are you running Vine Server (/OSXvnc/)
< http://sourceforge.net/project/downloading.php?group_id=64523&filename=V...
on your mac?
http://www.redstonesoftware.com/products/vine/server/vineosx/index.html http://www.redstonesoftware.com/downloads/index.html
JC
No, I just enabled the built-in Apple Remote Desktop. As suggestedhere: http://www.macminicolo.net/Mac_VNC_tutor.html
-- --- David Woyciesjes
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Justin Cataldo wrote:
Ah I see. Well that should work. It's obviously connecting since you get the dot.
I've had similar issues with TightVNC before. It sits for ages saying it is doing the initial screen draw, but never connects.
I'd suggest trying RealVNC (realvnc.com).
*VNC Free Edition for Linux (x86) http://www.realvnc.com/cgi-bin/download.cgi
The version RH ships does not work - [summer@bilby ~]$ vncviewer emu
VNC viewer for X version 4.0 - built Mar 31 2005 17:48:27 Copyright (C) 2002-2004 RealVNC Ltd. See http://www.realvnc.com for information on VNC.
Fri Mar 23 21:09:18 2007 CConn: connected to host emu port 5900 CConnection: Server supports RFB protocol version 3.889 CConnection: Using RFB protocol version 3.8
Fri Mar 23 21:09:23 2007 TXImage: Using default colormap and visual, TrueColor, depth 16. CConn: Using pixel format depth 6 (8bpp) rgb222 CConn: Using ZRLE encoding
Fri Mar 23 21:09:24 2007 CConn: Throughput 5125 kbit/s - changing to hextile encoding CConn: Throughput 5125 kbit/s - changing to full colour CConn: Using pixel format depth 16 (16bpp) little-endian rgb565 CConn: Using hextile encoding unknown message type 255 main: unknown message type [summer@bilby ~]$
However, I'm getting along just swimmingly with the TightVND included in OpenSUSE.
John Summerfield wrote:
Justin Cataldo wrote:
Ah I see. Well that should work. It's obviously connecting since you get the dot.
I've had similar issues with TightVNC before. It sits for ages saying it is doing the initial screen draw, but never connects.
I'd suggest trying RealVNC (realvnc.com).
*VNC Free Edition for Linux (x86) http://www.realvnc.com/cgi-bin/download.cgi
The version RH ships does not work - [summer@bilby ~]$ vncviewer emu
VNC viewer for X version 4.0 - built Mar 31 2005 17:48:27 Copyright (C) 2002-2004 RealVNC Ltd. See http://www.realvnc.com for information on VNC.
Fri Mar 23 21:09:18 2007 CConn: connected to host emu port 5900 CConnection: Server supports RFB protocol version 3.889 CConnection: Using RFB protocol version 3.8
Fri Mar 23 21:09:23 2007 TXImage: Using default colormap and visual, TrueColor, depth 16. CConn: Using pixel format depth 6 (8bpp) rgb222 CConn: Using ZRLE encoding
Fri Mar 23 21:09:24 2007 CConn: Throughput 5125 kbit/s - changing to hextile encoding CConn: Throughput 5125 kbit/s - changing to full colour CConn: Using pixel format depth 16 (16bpp) little-endian rgb565 CConn: Using hextile encoding unknown message type 255 main: unknown message type [summer@bilby ~]$
However, I'm getting along just swimmingly with the TightVND included in OpenSUSE.
Yep. I get the same error with vncviewer... Hmmm, what command options are you using with TightVNC?
David A. Woyciesjes wrote:
John Summerfield wrote:
Justin Cataldo wrote:
Ah I see. Well that should work. It's obviously connecting since you get the dot.
I've had similar issues with TightVNC before. It sits for ages saying it is doing the initial screen draw, but never connects.
I'd suggest trying RealVNC (realvnc.com).
*VNC Free Edition for Linux (x86) http://www.realvnc.com/cgi-bin/download.cgi
The version RH ships does not work - [summer@bilby ~]$ vncviewer emu
VNC viewer for X version 4.0 - built Mar 31 2005 17:48:27 Copyright (C) 2002-2004 RealVNC Ltd. See http://www.realvnc.com for information on VNC.
Fri Mar 23 21:09:18 2007 CConn: connected to host emu port 5900 CConnection: Server supports RFB protocol version 3.889 CConnection: Using RFB protocol version 3.8
Fri Mar 23 21:09:23 2007 TXImage: Using default colormap and visual, TrueColor, depth 16. CConn: Using pixel format depth 6 (8bpp) rgb222 CConn: Using ZRLE encoding
Fri Mar 23 21:09:24 2007 CConn: Throughput 5125 kbit/s - changing to hextile encoding CConn: Throughput 5125 kbit/s - changing to full colour CConn: Using pixel format depth 16 (16bpp) little-endian rgb565 CConn: Using hextile encoding unknown message type 255 main: unknown message type [summer@bilby ~]$
However, I'm getting along just swimmingly with the TightVND included in OpenSUSE.
Yep. I get the same error with vncviewer... Hmmm, what command options are you using with TightVNC?
The absolute minimum; hostname:0
John Summerfield wrote:
Justin Cataldo wrote:
Ah I see. Well that should work. It's obviously connecting since you get the dot.
I've had similar issues with TightVNC before. It sits for ages saying it is doing the initial screen draw, but never connects.
I'd suggest trying RealVNC (realvnc.com).
*VNC Free Edition for Linux (x86) http://www.realvnc.com/cgi-bin/download.cgi
The version RH ships does not work - [summer@bilby ~]$ vncviewer emu
VNC viewer for X version 4.0 - built Mar 31 2005 17:48:27 Copyright (C) 2002-2004 RealVNC Ltd. See http://www.realvnc.com for information on VNC.
Fri Mar 23 21:09:18 2007 CConn: connected to host emu port 5900 CConnection: Server supports RFB protocol version 3.889
Apple pulled a number out of the air for the protocol version. With RealVNC 4, it is close enough to the real number that the viewer picks the wrong encoding. I also believe there are other incompatibilities, but you will have to look at the RealVNC list for more details.
I believe people have had some success with the Windows version of VNCViewer 4.1.2, which has an option to force it to use the older 3.3 protocol. I don't know if 4.0 for Linux implemented this option.
William Hooper wrote:
John Summerfield wrote:
Justin Cataldo wrote:
Ah I see. Well that should work. It's obviously connecting since you get the dot.
I've had similar issues with TightVNC before. It sits for ages saying it is doing the initial screen draw, but never connects.
I'd suggest trying RealVNC (realvnc.com).
*VNC Free Edition for Linux (x86) http://www.realvnc.com/cgi-bin/download.cgi
The version RH ships does not work - [summer@bilby ~]$ vncviewer emu
VNC viewer for X version 4.0 - built Mar 31 2005 17:48:27 Copyright (C) 2002-2004 RealVNC Ltd. See http://www.realvnc.com for information on VNC.
Fri Mar 23 21:09:18 2007 CConn: connected to host emu port 5900 CConnection: Server supports RFB protocol version 3.889
Apple pulled a number out of the air for the protocol version. With RealVNC 4, it is close enough to the real number that the viewer picks the wrong encoding. I also believe there are other incompatibilities, but you will have to look at the RealVNC list for more details.
I believe people have had some success with the Windows version of VNCViewer 4.1.2, which has an option to force it to use the older 3.3 protocol. I don't know if 4.0 for Linux implemented this option.
I have RealVNC viewer vP4.2.8, and get the unknown error 255, even though I chose the Use Protocol 3.3 option. Looking more like I need to use Vine, or some other vncserver on the OSX side...
David A. Woyciesjes wrote:
William Hooper wrote:
John Summerfield wrote:
Justin Cataldo wrote:
Ah I see. Well that should work. It's obviously connecting since you get the dot.
I've had similar issues with TightVNC before. It sits for ages saying it is doing the initial screen draw, but never connects.
I'd suggest trying RealVNC (realvnc.com).
*VNC Free Edition for Linux (x86) http://www.realvnc.com/cgi-bin/download.cgi
The version RH ships does not work - [summer@bilby ~]$ vncviewer emu
VNC viewer for X version 4.0 - built Mar 31 2005 17:48:27 Copyright (C) 2002-2004 RealVNC Ltd. See http://www.realvnc.com for information on VNC.
Fri Mar 23 21:09:18 2007 CConn: connected to host emu port 5900 CConnection: Server supports RFB protocol version 3.889
Apple pulled a number out of the air for the protocol version. With RealVNC 4, it is close enough to the real number that the viewer picks the wrong encoding. I also believe there are other incompatibilities, but you will have to look at the RealVNC list for more details.
I believe people have had some success with the Windows version of VNCViewer 4.1.2, which has an option to force it to use the older 3.3 protocol. I don't know if 4.0 for Linux implemented this option.
I have RealVNC viewer vP4.2.8, and get the unknown error 255, eventhough I chose the Use Protocol 3.3 option. Looking more like I need to use Vine, or some other vncserver on the OSX side...
Well, I installed Vine on the Mac, opened the VNC port, and was able to connect with TightVNC here on Linux. :) Next, I'm gonna try using RealVNC... One neat thing about Vine on OSX, is it could allow more than one person to be logged into the Mac at the same time...
David A. Woyciesjes wrote:
David A. Woyciesjes wrote:
William Hooper wrote:
John Summerfield wrote:
Justin Cataldo wrote:
Ah I see. Well that should work. It's obviously connecting since you get the dot.
I've had similar issues with TightVNC before. It sits for ages saying it is doing the initial screen draw, but never connects.
I'd suggest trying RealVNC (realvnc.com).
*VNC Free Edition for Linux (x86) http://www.realvnc.com/cgi-bin/download.cgi
The version RH ships does not work - [summer@bilby ~]$ vncviewer emu
VNC viewer for X version 4.0 - built Mar 31 2005 17:48:27 Copyright (C) 2002-2004 RealVNC Ltd. See http://www.realvnc.com for information on VNC.
Fri Mar 23 21:09:18 2007 CConn: connected to host emu port 5900 CConnection: Server supports RFB protocol version 3.889
Apple pulled a number out of the air for the protocol version. With RealVNC 4, it is close enough to the real number that the viewer picks the wrong encoding. I also believe there are other incompatibilities, but you will have to look at the RealVNC list for more details.
I believe people have had some success with the Windows version of VNCViewer 4.1.2, which has an option to force it to use the older 3.3 protocol. I don't know if 4.0 for Linux implemented this option.
I have RealVNC viewer vP4.2.8, and get the unknown error 255, eventhough I chose the Use Protocol 3.3 option. Looking more like I need to use Vine, or some other vncserver on the OSX side...
Well, I installed Vine on the Mac, opened the VNC port, and was ableto connect with TightVNC here on Linux. :) Next, I'm gonna try using RealVNC... One neat thing about Vine on OSX, is it could allow more than one person to be logged into the Mac at the same time...
RealVNC connects with Vine just fine. :) Which is nice, I like the added features in RealVNC.
David A. Woyciesjes wrote:
William Hooper wrote:
John Summerfield wrote:
Justin Cataldo wrote:
.
I believe people have had some success with the Windows version of VNCViewer 4.1.2, which has an option to force it to use the older 3.3 protocol. I don't know if 4.0 for Linux implemented this option.
I have RealVNC viewer vP4.2.8, and get the unknown error 255, eventhough I chose the Use Protocol 3.3 option. Looking more like I need to use Vine, or some other vncserver on the OSX side...
One could always submit a bug report to CentOS and/or Red Hat documenting the problem and suggesting TightVNC as the resolution:-)
It might take a while for RH to get it into RHEL, assuming it accepts the suggestion, but it could easily be in a CentOS repo soul after some trusted sould builds it.
Justin Cataldo wrote:
Are you running Vine Server (/OSXvnc/) http://sourceforge.net/project/downloading.php?group_id=64523&filename=VineServer2.1.dmg on your mac?
http://www.redstonesoftware.com/products/vine/server/vineosx/index.html http://www.redstonesoftware.com/downloads/index.html
I'll give Vine a shot today, and see what happens...
-
David A. Woyciesjes -
John Summerfield -
Justin Cataldo -
William Hooper