Apple’s Mac keyboards actually do have a Control (Ctrl) key, but the Control key doesn’t function like the Control key on Windows. Keyboard shortcuts like Ctrl+C to copy text won’t work. Think of Force Quit as “End Task” for Mac users. Shortcut of the Day highlights a great shortcut on various platforms from the desktop to mobile devices to the web. On a Windows PC the CTRL-ALT-END key combination can be used to send the CTRL-ALT-DEL sequence to the remote session. As you rightly point out this is not possible on a MAC keyboard. For a MAC the key sequence to use is actually CTRL-ALT-DEL. Mac keyboard shortcuts By pressing certain key combinations, you can do things that normally need a mouse, trackpad, or other input device. To use a keyboard shortcut, press and hold one or more modifier keys and then press the last key of the shortcut.
Remote control of your Macintosh allows you to access a remote (host) computer across a network or the Internet from a local (client) system. The screen of the shared host computer appears locally, and you use your mouse and keyboard to control the other system from afar. Historically there have been fewer options to accomplish this for Macs than PCs, but the situation has been improving steadily.
Part 1 of this covers general considerations and Apple-supported methods available for remote system control that will generally work on any version of Mac OS X (Jaguar, Panther, Tiger, and Leopard). Part 2 addresses some commercial solutions that also support multiple OS versions, along with how to force-reboot a remote Mac. Part 3 looks at on new options provided by Mac OS X 10.5 Leopard.
Remote control capabilities vary by method used and include remote desktop control (screen sharing), file transfers, and system management (patches and updates). With any remote desktop method, access to the remote system is slower than when you are sitting in front of that computer. The method used, network bandwidth available, and types of traffic will determine the “sluggishness” factor.
Minimizing the amount of data you need to transmit for screen sharing will make the process run more quickly. Closing unnecessary windows on the remote system and using a flat single-color desktop (instead of a complicated picture or pattern) will speed up response. Patience is a must, but remember it’s usually faster than traveling there!
Needs and realities often dictate your options. Some remote control methods work across different versions of the Mac OS (or cross-platform), while others require the same OS version on local and remote machines. Detective conan prelude from the past english patch. Some methods require you to know the IP address of the remote system to connect and may require special firewall configurations, while others will work without any special settings or knowledge – usually!
It’s often helpful to use two remote control methods simultaneously (if possible), especially if you’re running a server or access is otherwise critical. Programs crash, network and Internet conditions vary, and you may find yourself locked out at a critical time. Sometimes method B works when method A doesn’t; then you can fix method A or reboot the machine from afar.
Apple’s native remote control solution is Apple Remote Desktop (ARD). ARD server software has been built into Mac OS X since 10.3 Panther and was available as an optional install for earlier versions of OS X. ARD provides the full gamut of remote system control: scalable screen sharing, file transfers to and from the remote systems, and remote software updating of individual machines and whole networks at a time. On a LAN, network admins with multiple Macs to manage will find this tool indispensable.
To enable an ARD host (server) in Panther and Tiger, go to System Preferences –> Sharing and turn on Apple Remote Desktop, then click Access Privileges and enable all desired services for one or more users. In Leopard you also enable ARD via System Preferences –> Sharing, but control capabilities have been split into separate Screen Sharing and Remote Management sections; click Options for choosing Remote Management services. ARD access from afar is via your host Mac’s account password.
To control an ARD-shared host computer, you need to use the Apple Remote Desktop administrator software. Apple sells two versions, a 10-client version for $299 or an unlimited client version for $499. The client limit dictates how many remote systems you can manage simultaneously; most home users and small business will be fine with the 10-client version. Bonjour support is available to find systems on your local network, or you can add them by IP address.
Across the Internet you must know the IP address of the remote computer or network gateway to establish a connection; this requires either a static IP address on the remote end or the use of a dynamic DNS locator service (like DynDNS) to find your remote system in times of need. ARD requires forwarding TCP and UDP ports 3283 through firewalls. Traffic can be routed across VPNs if one is available.
ARD is a powerful tool, but power comes at a price. Fortunately for home and small business users there are other options.
VNC is an open source software effort to provide cross-platform remote screen sharing capabilities. Long an option for Windows, VNC support was spotty on Mac OS 9 but is solid on Mac OS X. It has become my primary method of controlling remote Macs and PCs from other Macs (and PCs) when static IP addresses are available.
The remote Mac needs to run a VNC server; starting with Mac OS X 10.4 Tiger the built-in ARD software has included the option to use VNC for screen sharing. Go back to System Preferences –> Sharing –> Apple Remote Desktop (Tiger) or Screen Sharing (Leopard) and click the Access Privileges or Options button (as applicable). Enable Share Screen with VNC clients and use a strong password.
On pre-Tiger Macs or as an alternate option for all Macs, the free Vine VNC Server (for OS X and OS 9) and it’s older precursor, OSXvnc, offer excellent VNC server packages with more options than Apple’s built-in server. In my experience the Vine and OSXvnc packages are more stable and resilient than Apple’s built-in server – I’ve had onboard VNC stop working many times and require a reboot to fix, while the standalone server rarely fails. I use Vine VNC Server on many of the business systems I support.
A VNC client viewer application is required to view your remote Mac on your local system. Apple did not provide a VNC viewer in Mac OS X until 10.5 Leopard (see Part 3 of this series), but the open source market came earlier to the rescue. Chicken of the VNC is a good free VNC viewer with a silly name, and it runs on Mac OS X 10.3 Panther through 10.5 Leopard.
For a step up, $30 will get you the Vine VNC Viewer; this software is faster and more stable than Chicken of the VNC, and it offers screen size scaling (invaluable when controlling a big screen from a small laptop) and clipboard sharing. Mac OS X Tiger or Leopard is required.
Both Vine and Chicken of the VNC will find local network systems using Bonjour. Across the Internet you will need to know the IP address of the remote computer or use a dynamic DNS locator service. VNC uses TCP port 5900 for control and, as with ARD, requires port forwarding through firewalls and routers. VNC works fine across VPNs.
VNC provides screen sharing capabilities without file transfers. To work around this limitation you can use a network and/or Internet-accessible resource that both systems can reach: an FTP server, a shared Mac disk using AFP (AppleShare), a shared Windows volume using SMB, or a webserver with upload/download capability. Post the software or document from one system and grab it from the other via your shared disk or server.
Continued in Software to Remotely Control and Reboot Your Mac.
This article was originally published on Adam’s Oakbog website. It has been adapted and reprinted here with his permission.
State gambling ages. https://coollup934.weebly.com/freespin-casino-no-deposit.html. Keywords:#appleremotedesktop #vnc
Short link: http://goo.gl/DZUs4C
searchword: macremotecontrol
With the introduction of Mac OS X 10.5 Leopard, Apple upped the ante on Mac remote control. All of the methods covered in previous articles still work, but new options now exist in the operating system and via associated services.
Part 1 of this series covers general considerations and Apple-supported methods available for remote system control that will generally work on any version of Mac OS X (Jaguar, Panther, Tiger, and Leopard) – and even OS 9. Part 2 addresses some commercial solutions that also support multiple OS versions, along with how to force-reboot a remote Mac.
Apple now offers Apple Remote Desktop (ARD) and VNC viewer application for screen sharing called Screen Sharing (how original) in the Sharing pane of System Preferences. On a local network, shared systems will appear via Bonjour in the Finder’s sidebar. Click on them, and you’ll see a Share Screen… button.
Access is usually fast and elegant on a local network, although shared systems sometimes come and go in the sidebar. Restarting the local and/or remote Mac usually fixes the problem. I attribute this behavior to bugs in early Leopard releases and suspect this will become more stable with subsequent updates.
You can use Screen Sharing to access remote systems not on your local network, but you need to manually launch the program and know the IP address of the remote computer. Screen Sharing.app is located in System/Library/CoreServices (along with lots of other useful things).
Don’t move the program from this location. Instead put an alias in the Dock or on the desktop for easy access. When launched this way, you will be asked for the IP address of a server to connect to.
Power users may want to turn on a hidden window of the Screen Sharing app by entering these lines at a Terminal prompt:
Highlight shortcut mac word. LocalMac:~ localuser$ defaults write com.apple.ScreenSharing ShowBonjourBrowser_Debug 1
This adds a menu of VNC enabled systems accessible via Bonjour. Screen Sharing.app is a basic VNC viewer; it will satisfy many users, and the price is right.
Here’s a screen shot of a Mac running Leopard displaying and controlling the screen of one running OS X 10.6 Snow Leopard via Screen Sharing:
A companion service for remote system control across the Internet is Apple’s Back to My Mac capability. [The rest of this paragraph has been updated. The .mac service originally discussed no longer exists. It was replaced by MobileMe, which was subsequently replaced by iCloud.] You must have a current iCloud account to use this service, and all systems must be running Leopard or later. Use Leopard’s MobileMe System Preference pane to login to the same account on both systems and enable Back to My Mac on each machine. On the Mac to be controlled, you must also enable Screen Sharing and (if desired) File Sharing from the Sharing Preference Pane.
On the control (local) Mac, when you’re away from your home or office the remote Mac should show up in the Finder’s sidebar. You can choose to share the remote screen using Screen Sharing or mount one or more drives if File Sharing is enabled. The combination provides the one-two punch of (scalable) screen sharing and file transfers, and when it was available it worked very efficiently in my tests.
There’s one big potential impediment to Back to My Mac working correctly, however: Both the local and remote network routers must support pass through of Universal Plug’n’Play (UPnP) services. Some routers do this by default, some can be configured appropriately, and others are incompatible. At my home office I could not get a Sonicwall TZ170 small business router configured to pass Back to My Mac traffic, but an inexpensive Linksys WRT54G worked fine. Apple says its AirPort Extreme routers support Back to My Mac and publishes a list [no longer on Apple’s servers but avaialble on archive.org] of known compatible third party hardware.
One security consideration: Once enabled, this service is available for anybody who has access to your MobileMe account. Apple recommends using a strong password for MobileMec, which is always a good idea, but for additional security turn on Fast User Switching on the remote system in System Preferences –> Accounts –> Login Options. This creates a menu with your account name in the right side of the menu bar (right). Choose Login Window from this menu when you’re done using your shared machine or otherwise away from home to hide the screen and require a password for subsequent access.
NOTE: iChat in OS X 10.5 and 10.6 no longer appears to support screen sharing after the discontinuation of Apple’s MobileMe service. It may still work using Bonjour, but several attempts to make it work at Low End Mac headquarters have not worked.
iChat continues to mature and expand in capability, and with Leopard it has expanded to include screen sharing and file transfer capabilities. Implementation is excellent, and for the computer guy or gal in the family who always has to support their parent’s and grandparent’s computers, Apple has delivered a nice – and free – solution with this package. For this option, somebody needs to be present at the remote computer during the session.
You will need a different iChat account setup on each system to establish communication; you can use an existing MobileMe, iCloud, or AIM account if one is available, otherwise you can signup for an iChat account upon first launch. On a local network, iChat can also use Bonjour to find remote systems, but this option in initially disabled in iChat preferences.
You must have Leopard or later on both systems, and iChat must be launched on both Macs before attempting a connection.
The remote system will show up in either the AIM Buddy List or the Bonjour List, depending on the protocol used. Double-click a name to connect a chat session. The remote system will be prompted to accept the incoming connection (here’s where the remote user assistance is needed), then off you go.
Once connected, use the Buddies menu and Ask to Share the remote screen. Another dialog box at the far end requires acceptance of the sharing request. Apple uses it’s graphics wizardry to show both the local and remote screens, properly scaled, simultaneously on your screen. Very slick. Click on the smaller window in the bottom right corner to switch between local and remote screens.
To transfer files, go to the Buddies menu and choose Send File… The remote user must again accept the request. Once transferred the sent file shows up in the Downloads folder in the remote user’s home directory. Download office 2018 for mac.
By itself iChat doesn’t make a good option for unattended systems, due to the acceptance prompts which must be answered on the remote end before an action takes place. For attended remote desktop systems, or as a second option where you have another screen sharing solution in place like VNC, iChat is a viable solution. You don’t need to know any IP addresses or perform firewall configurations, and it can perform file transfers between computers. You also have good security, since you don’t have to leave the remote control on at all times – when you quit iChat the session is done.
As a final option, system administrators running the Leopard version of Apple’s Server Admin application can take advantage of Apple’s built-in screen sharing (ARD/VNC) direct from Server Admin.app – just choose Share Screen from the File menu when connected to a remote server. I typically use VNC alongside the Server Admin app for this purpose, but it’s always nice to have multiple options.
Leopard and Leopard Server both show a maturation of remote access and sharing capabilities, which is welcomed on the Macintosh. Options should only improve with time.
This article was originally published on Adam’s Oakbog website. It has been adapted, slightly updated, and reprinted here with his permission.
Keywords: #macremotecontrol #vnc 3screensharing
Short link: http://goo.gl/y7AaTa
searchword: macremotecontrol
0 
Star