can not connect to vnc server with 3.0

Hi Space2,

I've just tried with my ARD3.0 + a RealVNC server at WINXP at work and can connect with no problem, specifying the Address, no username and the VNC password.

I connect to it but see a blank screen. Is that what's happening to you?

Hi Space2,

I've just tried with my ARD3.0 + a RealVNC server at WINXP at work and can connect with no problem, specifying the Address, no username and the VNC password.

I connect to it but see a blank screen. Is that what's happening to you?

Hi,

i have the same problem. I cannot connect from ARD 3 to RealVNC-Server 4.19.

;-(((

I'm using TightVNC on my Windows and experiencing the same problem.

Xserve Dual G5 Mac OS X (10.4.6) ... and several iMacs (Intel)

Hi,

Previously I reported that I was unable to connect to a Windows 2000 Server running TightVNC Server. I did some protocol snooping and then proceeded
as follows:

- Removed TightVNC Server
- Downloaded and installed RealVNC 4 ( http://realvnc.com)
- Deleted the Windows Server reference from ARD
- Used the scanner to once again find the Windows Server
- Updated (via "GetInfo") to Login:<blank> and Password: <RealVNC password>

I was able to connect with the following warning generated by ARD:

The computer "...." is running a VNC server that does not
support Remote Desktop keystroke encryption. Text you
type to this computer may be intercepted over the network.
Do you want to continue connecting anyway?

To which I replied, "Yes". And presto, the Windows 2000 Server
appeared.

It is interesting to point out that TightVNC responds with
an RFB 3.003. RealVNC responds with RFB 3.008. From the
protocol dump it seems that ARD 3 may be having trouble
with the earlier protocol.

I consider my problem solved. I hope it will solve yours.

Xserve Dual G5 Mac OS X (10.4.6) ... and several iMacs (Intel)

How were you able to determine that TightVNC was using RFB 3.003?

I have several hundred original WinVNC Version 3.3.3 R9 running in my organization. This is a necessity since we hacked the service so it could not be turned off.

I have tested my MacBook Pro on a machine running RealVNC and it works fine. It fails on the WinVNC Version 3.3.3 R9, which I believe may have the same problem as TightVNC. Here's what interesting. I'm running ARD 3.0 on a XServe and it can connect to the WinVNC.

Do you think the protocol problem may be related on the Intel chipset?

I have confirmed that this is a problem only with the Intel-chipset.

I have installed the new ARD on three different computers. One PowerMac G4, one XServe G5, and one MacBookPro. ARD 3.0 will connect to the older versions of WinVNC only on the PowerPC based processors. The MacBookPro will only connect to systems running the latest versions of the VNC software, like RealVNC 4.1.1 and higher.

This is a major problem. For the mean time I will be downgrading my ARD back to 2.2. I can not afford to be without Remote Access on my Mac.

I have been experiencing the same problem with a "connection failed" error on my MacBook with ARD 3.0 to Windows XP Pro.

I have uninstalled and reinstalled every single VNC server I could find with no luck. Is there anything else I can try or any kind of diagnostic I could run that would help you figure out my problem?

Any help would be great.

Thanks,
Tom

I have confirmed that this is a problem only with the
Intel-chipset.

Me too! I thought I was going insane.

ARD 3.0 connects fine to a VNC Windows machine from my G3 and G4.

Can NOT connect using my Intel MacBook or my Intel Mac Mini!

Same settings, same versions, same VNC machine.

Following some tests with various VNC clients on both WinXP and Tiger it clear that ARD 3 on INTEL is not compatible with many VNC solutions out there wheras on PPC compatibility remains good. This difference appears to be that on INTEL ARD 3 does NOT work with VNC clients that are based on the original AT&T source code. Newer VNC implementations, like REALVNC, resolve the issue and are thus recommended if using an INTEL Mac as your ARD Admin machine.


MacBook Pro Mac OS X (10.4.7)

I am having problems too.

I'm trying to use ARD 3.0 to admin macs, windows and linux boxes.

The windows and linux session will only connect if I force the 3.3 protocol

If I use COTS VNC I can connect fine to my linux/windows boxes fine without needing to force the 3.3 protocol