2.7.16 Issuing connection requests from remote computers to controllers
A controller cannot initiate a connection to a remote computer in NAT or NAPT environment where the remote computer is invisible to the administrator's computer. In DHCP environments where IP addresses are assigned dynamically, there is a significant amount of work involved in finding out the IP address you need to specify in the controller.
In this type of environment, because the end user's computer does not have this issue when connecting to the administrator's computer, you can initiate a remote control session by having the user send a connection request to the controller.
- Important
-
Only online-managed computers can send connection requests to a controller.
Having the user send a connection request saves the administrator the trouble of entering a connection destination. This helps avoid situations in which the connection fails because the administrator enters the wrong IP address, and prevents unauthorized controllers from remotely controlling the computer.
The following figure shows the process of starting a remote control session in response to a connection request from a user.
![[Figure]](GRAPHICS/ZU100017.GIF)
A request server must be present in the connection list in order to receive connection requests from remote computers. After starting the request server, if a request for a remote connection is received from a user (step 1 in the figure), an icon representing the user's computer appears in the connection list. You can then initiate a remote control session by double-clicking the icon (step 2 in the figure).
Related Topics:
- Organization of this subsection
(1) Receiving requests from request agents
When the request server receives a connection request, the computer that issued the connection request appears below the request server. This computer is referred to as a request agent. The following figure shows an example of a connection list that contains request agents.
![[Figure]](GRAPHICS/ZU100016.GIF)
By double-clicking the icon for a request agent, the administrator can connect to the remote computer and begin a remote control session.
You can reject a connection request by deleting the request agent or closing the connection list.
When a request server stops, the request agent icon automatically disappears from the connection list. The icon is active as long as the connection request is in effect. It becomes inactive when the connection request is declined.
- Important
-
A request agent icon is a temporary representation of an agent that has issued a connection request. It is not retained after the connection list has closed. To save the information for an agent that issued a connection request, drag the icon to a group of your choice. After you move the icon to another folder, you can save the icon as an item in the agent list. You can then treat the agent as an ordinary computer and change its name and description.