Now, there is a little problem that still needs to be resolved: OSXvnc needs user interaction (clicking the add button), to make it initiate the connection. Obviously, to make this work, the vncviewer would have been started in listening mode on the machine with the given IP. OSXvnc allows you to enter an IP address and by clicking the Add button, let the vnc server call the client (the vncviewer). In this case, like with almost all clients, the viewer initiates the communication. That machine starts to listen for request from a vncviewer, on the predefined port. Usually, you open port 5900 on the machine you would like to remotely control. OSXvnc to the rescueįortunately, there is the OSXvnc open source project, while providing only a subset of Apple’s ARD, it has the nice feature, allowing the server to make the initial communication request. However, opening a server port is usually unacceptable and not tolerated by your IT folks – for a good reason, I might add. VNC is one of the very few – if not the only – cross platform solutions, allowing to access a Mac from a Windows box or vice versa. ![]() By doing so, your Mac starts listing on port 5900 and you could access it via any VNC viewer, like Chicken of the VNC (for the Mac), or RealVnc, or TightVnc (on Windows). ![]() You could simply open System Preferences / Sharing, enable ARD (Apple Remote Desktop) and check the VNC viewer checkbox. Accessing your Mac remotely isn’t really that difficult, if it weren’t for your resident IT-Department.
0 Comments
Leave a Reply. |