Shulou(Shulou.com)06/01 Report--

In this issue, the editor will bring you the continuous appearance of "Connection was reset." about the SecureCRT connection CentOS. What to do? the article is rich in content and analyzes and narrates it from a professional point of view. I hope you can get something after reading this article.

Today, an error occurs from time to time when using SecureCRT to connect to a virtual machine: Connection was reset, resulting in disconnection.

The cause of the problem:

It is suspected that the IP address of the virtual machine conflicts with other addresses.

The solution is as follows:

Shut down the virtual machine and see if the IP address can be ping

After shutting down the virtual machine, it was found that it could ping, indicating that it was really caused by the IP address conflict. After investigation, it was found that the IP of a port of the VMkernel configured in the virtual switch in vCenter was also 10.1.1.46, which led to the IP address conflict.

Problem solving:

1. Modify the IP address of the Vmkernel port configured in the virtual switch in vCenter

2. Modify the IP address of the CentOS virtual machine

The above is the continuous appearance of "Connection was reset." the SecureCRT connection CentOS that the editor shared with you. What to do, if you happen to have similar doubts, you might as well refer to the above analysis to understand. If you want to know more about it, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.