Misplaced Pages

#681318

22-636: Network Control Program might refer to: Network Control Program (ARPANET) , the software in hosts which implemented the original protocol suite of the ARPANET, the Network Control Protocol IBM Network Control Program Topics referred to by the same term [REDACTED] This disambiguation page lists articles associated with the title Network Control Program . If an internal link led you here, you may wish to change

44-471: A local area network can be remotely administered. For non-malicious administration, the user must install or enable server software on the host system in order to be viewed. Then the user/client can access the host system from another computer using the installed software . Usually, both systems should be connected to the internet, and the IP address of the host/server system must be known. Remote administration

66-462: A remote machine. One form of remote administration is remote desktop software , and Windows includes a Remote Desktop Connection client for this purpose. Windows XP comes with a built-in remote administration tools called Remote Assistance and Remote Desktop, these are restricted versions of the Windows Server 2003 Terminal Services meant only for helping users and remote administration. With

88-522: A simple hack/patch (derived from the beta version of Windows XP ) it's possible to "unlock" XP to a fully featured Terminal Server. Windows Server 2003 comes with built-in remote administration tools, including a web application and a simplified version of Terminal Services designed for Remote administration. Active Directory and other features found in Microsoft 's Windows NT Domains allow for remote administration of computers that are members of

110-575: Is VNC , which offers similar functionality. Computers infected with malware such as Trojans sometimes open back doors into computer systems which allows malicious users to hack into and control the computer. Such users may then add, delete, modify or execute files on the computer to their own ends. Windows Server 2003 , 2008 , Tablet PC Editions, and Windows Vista Ultimate, Enterprise and Business editions come with Microsoft's Microsoft Management Console , Windows Registry Editor and various command-line utilities that may be used to administer

132-515: Is often used when it's difficult or impractical to be physically near a system in order to use it or troubleshoot it. Many server administrators also use remote administration to control the servers around the world at remote locations. It is also used by companies and corporations to improve overall productivity as well as promote remote work. It may also refer to both legal and illegal (i.e. hacking ) remote administration (see Owned and Trojan ). Any computer with an Internet connection or on

154-447: Is some confusion over the name, even among the engineers who worked with the ARPANET. Originally, there was no need for a name for the protocol stack as a whole, so none existed. When the development of TCP started, a name was required for its predecessor, and the pre-existing acronym 'NCP' (which originally referred to Network Control Program , the software that implemented this stack) was organically adopted for that use. Eventually, it

176-496: Is therefore less practical if the host uses a dial-up modem , which is not constantly online and often has a Dynamic IP . When the client connects to the host computer, a window showing the Desktop of the host usually appears. The client may then control the host as if he/she were sitting right in front of it. Windows has a built-in remote administration package called Remote Desktop Connection . A free cross-platform alternative

198-459: The Telnet protocol has been phased out due to security concerns). X-server connection forwarding, often tunneled over SSH for security, allows GUI programs to be used remotely. VNC is also available for these operating systems. Apple Remote Desktop provides Macintosh users with remote administration capabilities. NX and its Google fork Neatx are free graphical Desktop sharing solutions for

220-516: The Transmission Control Protocol (TCP) as a transport layer protocol used during the early ARPANET. NCP was a simplex protocol that utilized two port numbers , establishing two connections for two-way communications. An odd and an even port were reserved for each application layer application or protocol. The standardization of TCP and UDP reduced the need for the use of two simplex ports per application to one duplex port. There

242-418: The ARPANET. It was almost universally referred to by the acronym, NCP. This was later taken over to refer to the protocol suite itself. NCPs were written for many operating systems , including Multics , TENEX , UNIX and TOPS-10 , and many of those NCPs survive (although of course they are now used by only vintage computer enthusiasts). On January 1, 1983, in what is known as a flag day , NCP

SECTION 10

#1732848265682

264-660: The Host/IMP Protocol in BBN Report 1822 , which was written by Bob Kahn . Under the auspices of Leonard Kleinrock at University of California Los Angeles (UCLA), Stephen D. Crocker , then a graduate student in computer science at UCLA, formed and led the Network Working Group (NWG). Working with Jon Postel and others, they designed a host-to-host protocol, known as the Network Control Program, which

286-647: The NWG developed these application-level protocols, TELNET and FTP . Since lower protocol layers were provided by the IMP-host interface, NCP essentially provided a transport layer consisting of the ARPANET Host-to-Host Protocol (AHHP) and the Initial Connection Protocol (ICP). AHHP defined procedures to transmit a unidirectional, flow-controlled data stream between two hosts. The ICP defined

308-553: The X Window System with Clients for different platforms like Linux, Windows and Mac OS X. There is also an enhanced commercial version of NX Server available. Remote administration software has recently started to appear on wireless devices such as the BlackBerry , Pocket PC , and Palm devices, as well as some mobile phones . Generally these solutions do not provide the full remote access seen on software such as VNC or Terminal Services , but do allow administrators to perform

330-596: The capabilities of the software require a very loose definition of what "administration" entails. Remote Server Administration Tools for Windows 7 enables IT administrators to manage roles and features that are installed on remote computers that are running Windows Server 2008 R2 VNC can be used for remote administration of computers , however it is increasingly being used as an equivalent of Terminal Services and Remote Desktop Protocol for multi-user environments. Linux , UNIX and BSD support remote administration via remote login, typically via SSH (The use of

352-456: The domain, including editing the Registry and modifying system services and access to the system's "Computer Management" Microsoft Management Console snap-in. Some third-party remote desktop software programs perform the same job. Back Orifice , whilst commonly used as a script kiddie tool, claims to be a remote-administration and system management tool. Critics have previously stated that

374-411: The link to point directly to the intended article. Retrieved from " https://en.wikipedia.org/w/index.php?title=Network_Control_Program&oldid=1248641555 " Category : Disambiguation pages Hidden categories: Short description is different from Wikidata All article disambiguation pages All disambiguation pages Network Control Program (ARPANET) NCP preceded

396-520: The procedure for establishing a bidirectional pair of such streams between a pair of host processes. Application protocols (e.g., FTP) accessed network services through an interface to the top layer of NCP — a forerunner to the Berkeley sockets interface. Network Control Program (usually given as NCP ) was the name for the software on hosts which implemented the Network Control Protocol of

418-483: Was developed in the ARPANET's earliest RFC documents in 1969 after a series of meetings on the topic with engineers from UCLA , University of Utah , and SRI . Crocker said "While much of the development proceeded according to a grand plan, the design of the protocols and the creation of the RFCs was largely accidental." After approval by Barry Wessler at ARPA, who had ordered certain more exotic elements to be dropped, it

440-612: Was finalized in RFC ; 33 in early 1970, and deployed to all nodes on the ARPANET in December 1970. NCP codified the ARPANET network interface, making it easier to establish, and enabling more sites to join the network. It provided connections and flow control between processes running on different ARPANET host computers. Application services, such as remote login and file transfer , would be built on top of NCP, using it to handle connections to other host computers. Other participants in

462-571: Was officially rendered obsolete when the ARPANET changed its core networking protocols from NCP to the more flexible and powerful TCP/IP protocol suite, marking the start of the modern Internet . Remote login Remote administration refers to any method of controlling a computer or other Internet-connected device, such as a smartphone, from a remote location. There are many commercially available and free-to-use software that make remote administration easy to set up and use. Remote administration

SECTION 20

#1732848265682

484-590: Was realized that the original expansion of that acronym was inappropriate for its new meaning, so a new quasi- backronym was created, 'Network Control Protocol' — again, organically, not via a formal decision. On the ARPANET, the protocols in the physical layer , the data link layer , and the network layer used within the network were implemented on separate Interface Message Processors (IMPs). The host usually connected to an IMP using another kind of interface, with different physical, data link, and network layer specifications. The IMP's capabilities were specified by

#681318