-
Self built remote desktop through frp The Windows computer at home cannot be managed directly through the remote desktop when people are outside because there is no independent IP. Through the use of frp and a vps with public network ip, intranet penetration can be achieved, and computers can be managed directly anywhere. For server side configuration, click here to download the latest frp software from github. Pay attention to selecting hardware and software versions that conform to vps. Modify the configuration file in frps.ini as follows: (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 (for example, put the frps in the/home/frp/folder): nohup/home/frp/frps - c/home/frp/frps. ini. Modify the configuration file in frpc.ini as follows: [common] server_ Addr=ip # This 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 the cmd or powershell, first cd to the folder of the frp, and then run the following command: frpc - c frpc.ini Connect to the remote desktop Use the ip and port 5200 of vps to achieve intranet penetration and remote desktop connection. The effect of remote desktop connection here depends on the network quality of vps, local and remote computers. The frp client starts automatically when it is powered on (provided by the lob of the hostloc) 1. Create a script with the vbs suffix (change it according to the storage directory of frpc) set ws=WScript. CreateObject ("WScript. Shell") Ws. Run "c: frp frpc.exe - c c: frp frpc.ini", 02. Put this script in C: ProgramData Microsoft Windows Start Menu Programs StartUp to add boot up. If the above directory cannot be found, you can find it through "Run" – "shell: startup". This article is from: https://pa.ci/77.html
