*Os X Vnc Client
*Ultravnc For Mac Os X
Simple, secure, ready-to-use remote access software for professionals and enterprises. Toolkits and solutions for integrating secure, real-time remote access. VNC® Viewer Plus. Lights-out remote access for Intel Core vPro computers. The first commercial Mac OS X Intel boxes may appear as early as January 2006 and certainly by June 2006. So maybe it will be practical, next year, to port UltraVNC to Mac OS X for Intel only, and forego any backward-compatibility to Mac OS X on IBM G4 or G5.
When you say you installed RealVNC, do you mean the RealVNC server? If so you have at least 2 VNC servers fighting for control of port 5900, unless you did something special to avoid that.
If the RealVNC server got control of port 5900, then it would ONLY want the VNC password that you would have needed to give to RealVNC (totally separate from your user account and any System Preferences -> Screen Sharing -> Computer Settings -> VNC viewers may control screen with password: xxxxxxx setting.Os X Vnc Client
NOTE: RealVNC client would not ask for the username as it would ONLY want the VNC password either from the above mentions 'VNC Viewers may control screen with password' field if Mac OS X Screen Sharing is in control, or if the RealVNC server is in control the VNC password RealVNC server was configured with.
Apple Remote Desktop is a software package intended for managing a classroom full of Macs, or a company's Macs. ARD is also what System Preferences -> Remte Management is used for. ARD is overkill for home use, and it is better to stick with System Preferences -> Screen Sharing, or if you want your own VNC server then disable that so that you do not fight over port 5900.
Ultravnc For Mac Os X
LogMeIn should not matter.
