【51CTO.com Quick Translation】Let's assume that your VirtualBox virtual machines have been running smoothly for a long time. Your virtual machines have been successfully serving applications and/or services without any problems. But on a certain important day, your company migrates the network solution or completely migrates the business system. Since all virtual machines are set to use bridged networking, VirtualBox should continue to serve those virtual machines smoothly. But that wasn't the case. Suddenly something was wrong. Although the VMs seemed to be able to access both the LAN and WAN, no one in the company could access any of the VMs. What happened? This problem can leave you helpless. No matter what you do with the network configuration in the VM, nothing changes. Why? Because the problem lies with VirtualBox, not with the individual VM. Fortunately, I have a solution. It's time to know that solution. Solution Unfortunately, you have to fix this problem for each VM (there is no global solution). Open VirtualBox, select one of the VMs, and click Settings. Click the Networking tab, and you'll see that your adapter is still set to Bridged (Figure A). Figure A: Our network adapter was working fine before the change Pay attention to the "Name" setting. This is the name associated with the adapter in the previous LAN setup. This is the culprit. You also understand that the named adapter retains information from the previous network. Even if you change providers and the internal network scheme remains the same, you may find that the named adapter does not allow traffic to enter the virtual machine. What to do? Click the "Name" drop-down. You should see a brand new name (that didn't exist before) listed (Figure B). Figure B: A new adapter name appears. Select the new adapter name and click OK. Once you have done this, start or restart the virtual machine. Once the virtual machine is started, you should now be able to access it without any problems. Simple Problem, Simple Solution This is one of those problems that can bother you for days. Luckily it's a simple problem with a simple solution. The other way around is that you'd have to reinstall all those VMs, and no admin wants to do that. Original title: How to fix a VirtualBox Bridged Network issue, author: Jack Wallen [Translated by 51CTO. Please indicate the original translator and source as 51CTO.com when reprinting on partner sites] |
<<: Five driving forces and four challenges for 5G development
>>: Network Access Control-Network Address Translation
Wi-Fi currently sends signals on the 2.4 and 5GHz...
edgeNAT recently opened a new cabinet in the Core...
[51CTO.com original article] On the afternoon of ...
Currently, 5G and the Internet of Things have bec...
Connectivity across campus, branch, cloud, and ed...
Recently, the most exciting things are the comple...
The tribe once shared information about UCloud, U...
Wi-Fi 6E: When is it coming? New wireless spectru...
According to Reuters, British Secretary of State ...
[[381477]] The Ministry of Industry and Informati...
In order to respond to public concerns, People...
In September 1830, the world's first intercit...
With the continuous development of information te...
As a low-power wide area network communication te...