-
Realization of self built remote desktop by FRP Windows computers at home, because there is no independent IP, can not directly through remote desktop management when people are outside. Through the use of FRP and a VPS with public network IP, the intranet penetration can be realized, and the computer can be directly managed at any place. For server-side configuration, click here to download the latest FRP software on GitHub, and pay attention to select the hardware and software versions that conform to VPS. Modify FRPs The configuration file in ini is changed as follows: (where 7000 is the communication port between the server and client of FRP) [common] bind_ Port = 7000 use the following command to run the FRP server in the background. Pay attention to the file path (such as putting FRPs in the / home / FRP / folder): nohup / home / FRP / FRP - C / home / FRP / FRP For ini - & > / dev / null client configuration, download the FRP version of windows on the GitHub page just now. Note that the software should be consistent with the number of digits in windows. Modify FRPC The configuration file in ini is changed to the following: [common] server_ Addr = IP ා here is the IP of VPS server_ Port = 7000 ා is consistent with the server [rdp] type = tcp local_ ip = 127.0.0.1 local_ port = 3389 remote_ Port = 5200 in CMD or shell, first CD to the folder of FRP, and then run the following command: FRPC - C FRPC Ini connects to the remote desktop, uses VPS IP and port 5200 to realize intranet penetration and remote desktop connection. The effect of Remote Desktop Connection depends on the network quality of VPS, local and remote computers. FRP client booting (provided by lop of hostloc) 1 Create a new VBS suffix script (change it according to the FRPC storage directory) set WS = wsscript CreateObject("WScript.Shell") ws. Run "c:\frp\frpc.exe -c c:\frp\frpc.ini",02. Put the script into C: programdata / Microsoft / Windows / start menu / programs / startup to add bootstrap. If you cannot find the above directory, you can find it through "run" – shell: startup. This article is from: https://pa.ci/77.html
