本文详细介绍了ARD（Apple Remote Desktop）与VNC（Virtual Network Computing）在不同平台上的互操作方法。包括如何配置VNC服务器以避免与ARD冲突、如何通过ARD连接到运行在不同端口的VNC服务器，以及如何从第三方VNC应用控制运行了ARD-VNC服务器的Mac电脑。
这里有一个很好的关于ARD和VNC的互操作以及不同平台之间通信的文章，比较全面。
The "normal" version:
Yep. All generic VNC software will conflict with ARD. This is a good note for most admins out there.
The "geek" version:
Tell RealVNC to use port 5901. Look at the "Connection Options" section of the documentation for your server-side os/version.
The "too much information?" version:
Actually, VNC servers and ARD do just fine side by side. (Aside from listening and bonjour a
dvertising and that), both servers are actually inactive until they receive a connection request. The clincher is that any services ...from Apache to ARD reports to SMB to VNC... always need to be listening to different sockets on different ports. In the good old days, VNC servers could actually listen on several ports and would serve at different color depths and resolutions based on the port number of an incoming request. In fact even today, because ARD uses a mostly standards-compliant VNC implementation, it has to use a different port for reports and commands and such so it won't conflict with the inbuilt VNC server.
VNC is usually on port 5900 nowadays. ARD uses 5900 for its VNC without asking. ARD also uses (or has used) 3283, 5432, 5433, and 5988 for reports and other non-VNC communication. (See: Apple's list of common ports.) In my experience, ARD's VNC client can very reliably control standards-compliant VNC servers, though your mileage may vary.
I routinely run the standard ARD "Remote Management" services on my servers for normal remote interaction, but then have a Vine Server set up on 5901 with vastly different settings to benefit low bandwidth connections from the internet, from my iPod's VNC client, or through bouncy ssh tunnels.
If you have any other experiences or questions, or especially if anyone wants try any of this and encounters problems, by all means post back.
From: http://discussions.apple.com/thread.jspa?threadID=1722872&tstart=0
The "normal" version:
Yep. All generic VNC software will conflict with ARD. This is a good note for most admins out there.
The "geek" version:
Tell RealVNC to use port 5901. Look at the "Connection Options" section of the documentation for your server-side os/version.
The "too much information?" version:
Actually, VNC servers and ARD do just fine side by side. (Aside from listening and bonjour a
dvertising and that), both servers are actually inactive until they receive a connection request. The clincher is that any services ...from Apache to ARD reports to SMB to VNC... always need to be listening to different sockets on different ports. In the good old days, VNC servers could actually listen on several ports and would serve at different color depths and resolutions based on the port number of an incoming request. In fact even today, because ARD uses a mostly standards-compliant VNC implementation, it has to use a different port for reports and commands and such so it won't conflict with the inbuilt VNC server.
VNC is usually on port 5900 nowadays. ARD uses 5900 for its VNC without asking. ARD also uses (or has used) 3283, 5432, 5433, and 5988 for reports and other non-VNC communication. (See: Apple's list of common ports.) In my experience, ARD's VNC client can very reliably control standards-compliant VNC servers, though your mileage may vary.
-
- To control a non-ARD VNC server via ARD, just do whatever you normally would in ARD. When controlling, it may warn you that the VNC server doesn't support keystroke encryption, etc. but should still work fine.
- To connect ARD to a VNC service running on a different port, choose "Add by Address… ⌥⇧⌘N" and in the address field, type the domain name or IP address as you normally would, but append a full colon ":" and the port number. For example, jsmith.example.com:5901 would connect to the computer named jsmith but would look for the VNC service on port 5901.
- To control a Mac which is running the OS's ARD-VNC server from a third-party VNC app, you must have 'plain' VNC access turned server-side (that is, on the Mac to be controlled: System Prefs > Sharing > Remote Management > Computer Settings > "VNC viewers…"). As long as you use a decent client, it should work reliably after that.
I routinely run the standard ARD "Remote Management" services on my servers for normal remote interaction, but then have a Vine Server set up on 5901 with vastly different settings to benefit low bandwidth connections from the internet, from my iPod's VNC client, or through bouncy ssh tunnels.
If you have any other experiences or questions, or especially if anyone wants try any of this and encounters problems, by all means post back.
From: http://discussions.apple.com/thread.jspa?threadID=1722872&tstart=0
扫一扫
1万+
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
