How to connect two virtual machines in VirtualBox the NetBEUI Protocol?

You have a virtual machine with a network connection in the settings which you have enabled the NetBEUI Protocol and TCP is disabled. Should this PC communicate with other PCs in a virtual network, the NetBEUI Protocol .
Network configuration twisted in different ways, but no result:(

In this connection, several questions arise:
1. Do I check the availability of the remote machine, just pingwa it by computer name?
2. On the second machine in network settings, no component of "NetBEUI", I understand it is necessary as that to install, and where to get?

Looks like a network setup like this:
5df2ecdb3825d751473138.png
April 3rd 20 at 17:45
2 answers
April 3rd 20 at 17:47
Solution
1. Do I check the availability of the remote machine, just pingwa it by computer name?

No. Prchem here the ping program based on icmp Protocol (for Windows it is attributed to the TCP/IP banned, all of it is not)
2. On the second machine in network settings, no component of "NetBEUI", I understand it is necessary as that to install, and where to get?

Potentially - in components of Windows. But NetBIOS (aka NetBEUI) no I think starting with Win7. The Protocol is very old, only supports peer-to-peer network (i.e., only one segment of the network, the nearest router), any security in principle absent.
It is unclear why in 2019 might need it.
Sorry for incorrect question, it was necessary to start with another.
In General, there is an old system consisting of one PC running Windows 2000, and clients running DOS. They communicate with each other via the NetBEUI Protocol.
As hardware platform support is difficult because of the complexities of purchasing old equipment, the need to drive it in a virtual machine.
In General the way servers (one on Windows 2000) failed to deploy on a virtual machine in VirtualBox.
The network connection works there, in components of the NetBEUI Protocol is.
But the problem is that the data does not pass through the network to the host machine (i.e. VirtualBox which itself is deployed, and on it Windows 10).
In such case, the work with TCP I know.
But as with NetBEUI, it is not clear(
I don't even know how to check whether a virtual machine host via NetBEUI.
As you can check the availability of remote machines for NetBEUI? - linwood.Douglas commented on April 3rd 20 at 17:50
@linwood.Douglas, Well, it is theoretically possible slabat ' dozovuju the car and put it in the same LAN with the car on win2k (this is important in NetBIOS no routing). If Dosova car will see win2k (just to be his presence in the network) - so there. No means no. NetBIOS was very simple Protocol, there is not much fooled on the subject of diagnosis. Another question is how to have it all on virtual hardware, when the wood under him long gone.
I had a similar story. FreeBSD is times 2006 (actually I tried). It is a emulator Novell Netware mars_nwe, which simulates the IPX dasovich customers NetWare who cling to a certain resource and run a test to check some iron. It's all a big pile of nekropolista still works, but if you fall it will not rise, because the attempt to translate the FreeBSD dev came to nothing. No, the machine itself has been virtualized, but mars_nwe does not work. Well, that is Dosova car to see it.
All this is what I? You may have the task to review :) Unless you want to look for the description of the Protocol, to take traffic analyzers, remove the dump and delve into the jungle :) - Nikolas.Conn91 commented on April 3rd 20 at 17:53
In my case, while I'm not so bad.
Dozovuju the car to carry on dev while sharp is not necessary. As in the bins I found some Mat. plat and I managed to deploy them on the way desaveu system and download and install the driver for the network card. Now spec. FOR requests connection to the server. But stick it in a network with a server, the hand does not rise yet:( that was the idea, to deploy the server image (remember that it is under Windows 2000) that on virtualke, that would at least check the work of freshly baked doasage client, and in future will go in as a hot spare (in case of failure of the server)...

I think that without the traffic analyzer and the study Protocol was not enough:(
The question is what, again:
1. There is a virtual machine with Windows 2000 on Board (On VirtualBox)
2. Have a client running DOS (this is a physical machine)
3. And between them the host machine under Windows 10 (that is, it is the VirtualBox)

The server is Win 2000 with the DOS client communicates over NetBEUI.

According to the idea, if the network card on the host machine to make it work like a switch that he passed on through the network, got all that, then I think no problem... right?

There is still plan B, I tried to raise the Win2000 server on a real hardware but failed to install fire wood on a network card, found under the chip, only on Win XP, ideas have Win 2000 and under to go, but for some reason didn't go:( If you can run, you can at least Deavy client to check... - linwood.Douglas commented on April 3rd 20 at 17:56
@linwood.Douglas, Fuck knows how the network card VB emulates. If it was in hyperspace the first level, there we can say with some certainty that we can say that for e1000 there is full emulation of hardware. But in VB I can not say, it seems to me that to raise the bare-metal server on win2k will be faster. And to find balance in the beginning of zero problems at all it should not :) the Wood under XP can not start - compatibility-downwards, that is to XP from win2k firewood could earn. - Nikolas.Conn91 commented on April 3rd 20 at 17:59
The wood under XP can not start - compatibility-downwards, that is to XP from win2k firewood could earn.

You want to say from the bottom up? That is like 2000 appeared earlier, and XP is based on?
it seems to me that to raise the bare-metal server on win2k will be faster.

While it is necessary to move in this direction, because if we can find firewood, but still will not work, and virtual reality and even more so or Vice versa, if the gland is working, then you can already with the dev to think and mesh filigree... - linwood.Douglas commented on April 3rd 20 at 18:02
@linwood.Douglas, Yes. Win2k came - suddenly - 2000 :) WinXP later in 2001. - Nikolas.Conn91 commented on April 3rd 20 at 18:05
April 3rd 20 at 17:49
Solution
The result is not and never will be.

1) Ping and never will be. This is for TCP
2) Component and never will be. The OS is not supported. Can not be set.
1. I mean, are you saying that without the inclusion in the settings of the network card TCP will not work?
Probably not only TCP but also UDP?

2. What specific OS do you mean?
On Windows 7, I present a Protocol able to establish, at least he appeared in the components settings of the network card... - linwood.Douglas commented on April 3rd 20 at 17:52
1. Or do you want to say that the last Windows which worked NetBEUI without TCP was Windows 2000? - linwood.Douglas commented on April 3rd 20 at 17:55
@linwood.Douglas, NetBIOS is dead. And has been dead for a very long time. Does not work. Point. - Nikolas.Conn91 commented on April 3rd 20 at 17:58
@linwood.Douglasagain - ping uses the icmp Protocol. NetBIOS it is any relation has no. Set the TCP settings of the network card - ping will check the availability for TCP. - Nikolas.Conn91 commented on April 3rd 20 at 18:01
Yes you are right.
But whether it is possible to NetBIOS to check the availability of a remote machine?
Similar to ping in TCP ? - linwood.Douglas commented on April 3rd 20 at 18:04
@linwood.Douglasnet /view
or browse the network in Explorer
but displayed only the shared resources. to check the availability of the client it is impossible in principle - Sandrine commented on April 3rd 20 at 18:07
@Sandrine, I tried to use the command net view, but that is not anything worthwhile ever came of it, for some reason on this network it doesn't work correctly:( And the manual I read:(
But I found where to look, who to charitites for your network folders in the "computer management" > "shared folders > Sessions". And monitor the client connection:) - linwood.Douglas commented on April 3rd 20 at 18:10
@linwood.Douglas, you kind of described that in the virtual server only? and customers are more physics?
your hypervisor can also iskiate the work of the NetBIOS or host operating system, traffic is actually using it the driver is - Sandrine commented on April 3rd 20 at 18:13
@Sandrine, I've confused myself:(
Yeah right, I tried to get the system and a fully virtual and physical but on another platform...
And hybrid (i.e., when the virtual server and the client physical).
At the moment, managed to get the system on a physical piece of hardware. But still busy to those that deal with the intricacies of configuring specialized software...
And virtual machines is only able to raise virtual NIC and virtual server and virtual client, but not yet tested the software, but driver initialized:)
In General, the work continues:(
On the virtual client is likely to be more backed up with the virtual COM ports under DOS ( - linwood.Douglas commented on April 3rd 20 at 18:16

Find more questions by tags Computer networksWindows