Use of CentOS 6.5 remote logon management tool SecureCRT

Use of CentOS 6.5 remote logon management tool SecureCRT

[Body]

Virtual Machine version: VMware Workstation_10.0.3

Linux: CentOS_6.5 (64-bit)

I. Preface:

I installed CentOS 7, the latest version released last month, a few days ago. I found that many of my learning experiences are not the same as the old CentOS version, so many problems have occurred (of course, for beginners like me), so now we have re-installed CentOS 6.5 for learning. Let's go to the topic.

After CentOS is successfully installed in the vmwarevm, two virtual NICs: VMnet1 and VMnet8 will be created in the win7 system. Let's check them, click Control Panel> View network status and task> change adapter settings. The following page is displayed:

Open the Virtual Machine and select "virtual machine ---> Settings". The following page is displayed:

To ensure that the virtual machine can communicate with the physical machine or access the Internet normally, make sure that the "device status" in the upper-right corner is: connected.

There are three methods for network connection. The following describes the three methods in detail.

Two-way communication between Windows 7 and Linux using SecureCRT and file transfer solution

How to Use SecureCRT6.6.2 to log on to Ubuntu through SSH

SecureCRT connects to Ubuntu

Ubuntu 12.04 + Virtual Machine VMware 9 + Secure CRT + EditPlus local C ++ Development Environment setup

Use SecureCRT to transfer files between Linux and Windows

Install SecureCRT 14.10 on Ubuntu 7.3

2. Bridge, NAT, and Host-only modes:

• Bridge Mode: the virtual machine uses a real Nic for communication, and the configuration is simple. As long as it is in the same network segment as the real computer, it can directly communicate. If there are other computers in the LAN, you can also access it. Disadvantage: it will occupy an IP address in the CIDR block. (Similar to a truly independent computer)
• NAT mode: Use the virtual network card VMnet8 for communication. It can only communicate with the local machine. On this basis, virtual machines can access the Internet through the host.
• Only Host Mode: Use VMnet1 as the virtual network card to communicate with the local computer.

 

Iii. Host-only configuration in Host mode only:

(1) Check the VMWare services first:

Select "computer ---> Management --- service and application --- service", find VMware NAT service and VMware DHCP service, and start it:

(2) view the network segment of the vm nic:

Now that you are using VMnet1, check the network segment of VMnet1:

It is shown that the IP address of VMnet1 is 192.168.154.1, that is, the network segment is 192.168.154.X (the address automatically allocated by the virtual machine, and each user's computer may be different)

Enable sharing of local connections: (do not enable sharing of virtual network cards)

Then we enter the vmwarevm and set the connection mode to Host-only:

Next, open VMware's Virtual Network editor and check the Configuration:

, You can see that the virtual network segment is also 192.168.154.X

(2) Configure in the VM:

Open the CentOS terminal, enter the root user, and enter the following command to view the current Nic information: (Note: if yes, It is an interface)

ifconfig 

The following information is displayed:

No available Nic is displayed (lo is the local back-to-ring Nic, which is mainly used for communication and testing on the local machine. You can ping yourself without inserting the network cable. It doesn't make much sense ).

Enter the following command to assign an IP address to eth0: (Make Sure That VMnet1 and VMnet1 are in the same network segment 192.168.154.X)

ifconfig eth0 192.168.154.2ifconfig 

The following information is displayed:

(3) Verify in Windows:

Open the cmd console in Win7 and enter the following command:

ping 192.168.154.2 

The result is as follows. If you receive such a request response packet, ping is successful:

 

Iii. NAT mode configuration:

The steps are the same as those in the Host-only mode above.

Note that the virtual network card VMware8 and the virtual machine IP address must be in the same network segment:

The most critical commands are:

ifconfig eth0 192.168.221.2  

For more details, please continue to read the highlights on the next page:

1 2 Next Page