7.6.1. Remote Node versus Remote Control

Remote clients can associate with a network in two essential ways: remote node and remote control. A remote node association is one in which the remote PC turns into a node on the network. Data streams between the remote node and the network much as it would for a LAN-associated client, but more often than not at much slower rates. When you associate with an ISP to get to the Internet, you are utilizing a remote node association.

A remote control association is one in which a remote client takes control of another PC specifically associated with the LAN, with just the screen, console, and mouse data being transmitted through the association. Since the remote control PC is specifically associated with the LAN, its network execution is pretty much as quick as that of whatever other LAN workstation. The data really transmitted—the screen data, console data, and mouse data—as a rule doesn't require much transfer speed. (One special case to this guideline is a profoundly graphical application, for example, a PC helped drafting drawing program.) Remote control associations additionally have approaches to exchange records forward and backward from the remote PC to the controlled PC, so documents can even now be downloaded from the LAN to the remote PC and the other way around.

Remote control is refined utilizing extraordinary applications intended for this reason. You run the remote control programming on both the LAN-associated PC and the remote PC. The association is built up over a dial-up line or through the Internet.

Two sorts of remote control apps are accessible. The one keeps running on a solitary PC and supports a solitary remote PC at once. pcAnywhere and GoToMyPC are case of this sort. Another sort permits numerous sessions to keep running on a solitary PC, so you can permit more than one client making utilization of a solitary PC associated with the LAN. Windows NT T͞e͞r͞m͞i͞n͞a͞l Server, Windows Terminal Services, and C͞i͞t͞r͞i͞x XenServer are case of this sort. The multiuser arrangements utilize the LAN PC's multitasking capacities to build numerous virtual PCs, windows, and desktops, kind of like a workstation with different terminal sessions.

Any of the remote association technologies can work with both remote node and remote control. You can associate with a remote control framework through modems associated specifically to the remote control PC, through ISDN cables, over the Internet, or even over a LAN or WAN connection.

How would you know whether to pick remote node or remote control associations? Think about these points:

a)   When a remote client needs just LAN document access and email access, a remote node association can address these issues and is regularly less complex to set up and keep up on both sides of the association.

b)  If a remote client needs to run an application that is LAN-associated, pick remote control. A couple of software’s may have the capacity to run sensibly well over a remote node association, gave the application itself is now introduced on the remote PC and the application must get to just moderately little measures of data through the remote connection. For instance, getting to email through Microsoft Outlook works fine over a remote node association gave the remote clients as of now have Outlook introduced on their nearby PC.

c)   Many apps are currently web-empowered, so a remote client can utilize a web browser to access and utilize such applications. These sorts of apps run similarly well, pretty much, over a remote node or remote control association. For instance, Microsoft Exchange Server bolsters various association sorts, including web access to mailboxes and calendars, through a component called Outlook Web Access. Numerous client/server bookkeeping frameworks are additionally beginning to actualize web access.

d)  If you have to keep up an application straightforwardly for the clients, remote control may be the approach, since it leaves the application on the LAN-associated machine, where you can without much of a stretch access it to roll out arrangement improvements or perform other upkeep. The remote client runs just the remote control programming and directly profits from any work you do on the LAN-associated machine. This ability can give a genuine favourable position if your network's clients are not open to doing their own upkeep or investigating on the software. With such an association, you can all the more effortlessly handle any issues that emerge, without expecting to go to some remote area or obliging clients to send their PCs to you for repair or support.

Remote control is the best wagered when the remote clients need to get to applications that don't function admirably over low transfer speed associations. Also, on the grounds that most applications don't run well over slower associations, remote clients will more often than not find that a LAN-associated application works preferred with remote control over with remote node.