The solution to the problem that the remote tool (SecureCRT) cannot be connected to the computer of the Windows 11 system

The problem appears as shown below,

Reason: The physical IP address (you can use the right mouse button -> click the terminal to view) does not match the virtual machine IP address (check it in the virtual machine editor -> virtual network editor), and the solution is also based on these two aspects.

Solution:

1. Right mouse button --> enter the terminal --> enter the command ipconfig , and then check the physical IP address of VMnet1 and the IP address of VMnet8, (if you don't have these two, check my previous article to solve it)

The network adapter VMnet1 and VMnet8 disappear in the computer of Windows11 system to solve the problem link: https://blog.csdn.net/bc_1024512/article/details/129979859

 

2. Open the virtual machine --> click Edit , the following picture appears,

 3. Open the virtual network editor (N)

 4. Check whether the physical IP address is the same as the virtual machine IP address. Generally, the problems are different, or they may be the same. For example, I can use the following methods to solve them.

5. Click on the Win window , enter in the search box to view the network connection

 6. Appears after opening

7. Click VMnet1  to appear ---- (the same solution as VMnet8)

 8. You can click Diagnosis (G) first

 9. Click Try these fixes as administrator ,

10. Click to apply this repair, the following two situations occur,

The first,

It is also possible that the second

 

11. Get the problem through diagnosis, then you will know how to start, click close , and return to

12.j To solve the first problem, press the key combination Win+R to open the running window, enter services.msc ,

 13. Click OK , after the service window appears, find the " DHCP Client " service

 14. After opening the dhcp service, change its enabling type to automatic , the service status is running , and then press OK to save the settings, as shown in the figure

 15. Re-enable the local area connection and the problem will be solved, but if it is the second kind, the diagnosis will appear again

16. Then return to

17. Right-click on VMnet1 to appear

18. Click Properties (R)

 19. Select internet protocol version 4 (tcp/ipv4) and click to find the alternate configuration , as shown in the figure

20. Click User Configuration and manually enter its IP address. Its IP address must be in the same LAN as the subnet address of the virtual machine network editor, that is, for example: 192.168.112.0, you can enter 192.168.112.2 (0~255), Its gateway must be 192.168.112.1

 As shown below,

21. Click OK twice , then the computer automatically diagnoses, and the following picture appears

 22. At this point, all problems are solved, and you can connect remotely again

 Disclaimer: The above is the solution I used. If you have different opinions and ideas, you can share them. Thank you for your guidance.

Guess you like

Origin blog.csdn.net/bc_1024512/article/details/129985671