rlogind

Service

rlogind provides remote command shell facilities with
authentication based on privileged port numbers from trusted hosts.
Like any other 7/2008R2/8/2012/10/2016 service, you can use the service
utility to start and stop rlogind.

rlogind listens for service requests at port 513.
When a service request is received, the following protocol is initiated:

The service checks the client's source port.
If the port is not in the range 512-1023, the service aborts the connection.

The server checks the client's source address.
If an entry for the client exists in both /etc/hosts and
/etc/hosts.equiv, a user logging in from the client is not
prompted for a password.
If the address is associated with a host for which no corresponding entry
exists in /etc/hosts, the user is prompted for a password,
regardless of whether or not an entry for the client is present in
/etc/hosts.equiv.

rlogind loads the user's profile and runs the
command shell specified in the MKS Toolkit control panel applet.

installs and starts the rlogind service.
To start the service without installing it, use the service
command:

service start rlogind

-remove

stops and removes the rlogind service.
To stop the service without removing it, use the service
command:

service stop rlogind

-debug

runs rlogind as a normal program in the current console
for debugging purposes.

To use this option, you require the following privileges:

Replace a process level token (SeAssignPrimaryTokenPrivilege)Increase quotas (SeIncreaseQuotaPrivilege)Act as part of the operating system (SeTcbPrivilege)

If you are lacking any of these privileges, rlogind reports
which are missing.
You can use priv to add these privileges and then log out
and back in.
For example, the following assigns all three privileges required for using
this option:

There is a very brief period of time when rlogind is
establishing a connection with a client that it is unavailable to establish
a new connection with another client. Up to a limited number of connection
attempts from other clients are buffered until rlogind
is free to service one of them. Additional connection attempts beyond that
limit fail.
An error results from the client indicating that it was unable to find the
rlogind service. In real world usage, this limitation is
unlikely to be encountered.
This limit is operating system dependent.

If your MKS Toolkit license only includes a single-connection license for
the connectivity tools, rlogind only allows one
connection at a time.