SecureCRT is a good thing. I tried to install and configure it today. You don't need to talk about the software installation process. The following is my configuration process: preparation: RedHatlinux in my virtual machine adopts the bridge mode. I assigned an ip address (192.168.1.104) to linux, and the ip address of my host is 192.168.1.103 (the ping from the host to the virtual machine can be pinged, haha this is nonsense !). When SecureCRT is enabled, such
SecureCRT is a good thing. I tried to install and configure it today. You don't need to talk about the software installation process. The following is my configuration process:
Preparation: RedHat linux is used for bridging the Internet connection. I assigned an ip address (192.168.1.104) to linux, and the ip address of my host is 192.168.1.103 (the ping from the host to the virtual machine can be pinged, haha this is nonsense !).
When SecureCRT is opened, the following interface is displayed:
Enter the host name as prompted, which is the ip address of your VM. The port is 22, so you don't have to worry about it first. The user name is the user name you want to enter to log on to your VM. It is reasonable to say that you can connect to my VM now, but when you click Connect, the following error prompt box will appear:
According to the error message, we can solve the problem by setting the port number. Where should we set our port number?
In fact, there is an sshd_config file under/etc/ssh. Modify the vi sshd_config file. Add the following content to the file:
Port 22
Protocol 2
PermitRootLogin yes
PasswordAuthentication yes
Then, run the service sshd restart command under/etc/init. d/to restart the service. You can try the connection again.
The above is the first time that I have used SecureCRT to connect to a virtual machine linux. This is the first time that we will inevitably have some wrong understandings, so please discover what is wrong and let us know.