Remotely log in to Linux (this is the main introduction to virtual machine connections)
- Network classification of virtual machines
Well, then, first of all, let's introduce the virtual machine's network settings. (I wasn't going to write this, but I thought about it later!) The above mentioned remote connection is somewhat general. So here's the main emphasis.)
The network mode of virtual machine actually uses three kinds:
1. Bridge mode: The virtual machine uses the real machine's network card and the real-time communication, occupies one IP address of the same network segment, and communicates with the PC in the local network segment. A simple explanation!!! Bridge mode is to use your real network card, so that you are on the local area network to assign a "true" IP address.
2. Nat mode: With host only, the difference is the use of VMnet8 that fake network card, if the real machine can access the Internet, the virtual machine can also. To say here is, if your local area network IP address conflict seriously recommended or use this mode, the same can achieve the results of bridging mode!! But what we care about is not the connection, but the Linux system that connects to our virtual machines.
3. Host only mode: the virtual machine only communicates with the real machine, does not occupy the real network segment IP address, uses VMNET1 that false network card. For this model, how to say?? That's the pattern! Not even on the network, if you learn the network command, it can not choose this mode. But if there is no network, then you can only choose this mode to connect!!! Now the main purpose is to be able to connect to our system, so for no network conditions can use this mode!!
There are several modes on the virtual machine that are introduced first, but give some advice, and if you're using a laptop, the suggestion is to help solve some minor problems.
Virtual Machine Connection recommendations: Here the suggestion (for laptop users) is to choose the NAT mode, because this mode can be online, of course, the Internet is not my reason to give advice, the reason is very simple, that is, for notebook users because there are two of network cards, one is WiFi, one is wired. This way you have the choice of network, should be two kinds of Internet access, the Linux system assigned to the IP address is different, so for the connection will be a problem!!! Here are just a few suggestions, and if the proposal is not acceptable, the suggestion can be omitted directly. (These two suggestions should always have one to be accepted!!) ^_^!! )
On the introduction of virtual machine installed after the problem of virtual network card! This behavior generally occurs because Windows prohibits or does not have a service that starts a virtual machine.
Here's a quick solution (only this is the problem, so you can write down this one)
1. Right-click My Computer----> select "Manage"----> select "Services"----> and then find the VMware Services process, view the properties and select them as self-starter to solve.
- Xshell Connecting Linux issues:
For this problem is generally not connected to the basic Linux is not installed SSH service, if not installed directly installed on it. If you download a CD that does not have an SSH installation package, download one. If you download the RPM package, you can install the full name of the package directly using the command rpm-y. Or you can install the yum-t installed sshd directly under Linux (provided that your Linux is able to surf the internet and the source can be found). Well, let's introduce these first!!
#望穿杯中酒, I just pity the flowers in the water
#来时忧心中, it's hard to leave the dead
Virtual Machine Network connectivity issues