Video - Troubleshooting Connectivity Issues With Virtualization

10 minutes
Share the link to this page
A short video on troubleshooting connectivity issues between Kali and your target machines. Use this video to ensure your Kali and other virtual machines have connectivity between them.


Greetings and in this short video presentation, we're going to cover connectivity between a virtual machines in both virtual box and in VMware. We're going to begin by talking about some basic networking fundamentals. First off with Kali and Windows XP, for either one to see the other, they have to be on the same network. Now, when we talk about networking, we're talking about IP addresses. IP addressing, in this case happens to be centered around the network. So the network portion of an IP address will always be the first three octets right, so we're talking here 192 dot 168 dot 1454 Class C network.

This is the network portion for the address for this machine, the host IP is 177. And if you look over here at the Windows XP, you'll see that this IP address is the same network 192 dot 168 dot 145. It has a host IP that's going to be different of 133. But they are both on the same network. That is to say they are on the 192 dot 168 dot 145 network. So we look at these network as being the cornerstone or the rock foundation of how these devices are going to communicate without it.

There's nothing so when you say that the session failed or the session cannot be established, or whatever the reasons Maybe, or whatever the error might be. It has nothing to do with anything except networking. If we can't ping these machines, that is to say, if I can't ping from Cali to XP and from XP to Cali, then there is no connectivity. So I ping and I get a response. That means those devices are talking to each other. There I have connectivity.

Now you won't get that. If these two devices do not share the same network, they can't share. They cannot share the same host IP, but they have to share the same network. Okay. Now, the problem that people have with these Virtual Machines is their host machine. It all comes down to whether or not VMware or VirtualBox can actually virtualize their hardware.

Now, when it comes to industry standards, that's Microsoft. Microsoft works with all kinds of different industries as far as networking adapters, hard drives, motherboards, CPUs, the BIOS, that's all based on industry standard and Microsoft is designed to work with all these different manufacturers because they all use the same standard. Now, when you get to a different manufacturer, such as Apple, they're proprietary. And this is where we're running into problems. Because Macs and apples don't have an open source or a industry standard, hard set of hardware. Were configurations to deal with.

So when we look at an apple, we have something that only Apple is going to have and that is the arrow net adapter. You won't find this adapter anywhere else, arrow net, it belongs to a Mac or an apple. But unfortunately, Windows XP does not know how to virtualize that and neither does VMware or anything else. Because it is proprietary. Alright, so when we get up here on VirtualBox, and we look at the settings and we go into the network here, this is like on a Mac, we have to use a different adapter. Now the most common adapter that you can find up inside of VirtualBox is going to be the PC net, dash fast three.

This is the most common it is the oldest. It is Drivers are found in just about any operating system and used today. So even XP is going to be able to recognize this and even a Mac or an apple can recognize it. So when you go in here, and you pull this down and you see that it's using an arrow net, it's not going to work. Their own out adapter is not going to work period. All right, so you've got to go to bridge adapter, you've got to push down the Advanced tab, and you have to select the PC net dash fast three adapter.

It's a virtual adapter, it doesn't really exist, except in memory, but that's fine. Now you go over here to your Windows XP box. Close this one out. I'm up in VirtualBox. So I go over to my virtual install of Windows XP and I go into the network. And I go down here.

And I'm going to use the same adapter. I'm going to tell it to virtualize this same adapter. Now, they will both work because they can both see the hardware. Windows XP is not going to work with your arrow net adapter, forget it, but it will work with the PC net. Okay. So make sure that we check the bridged adapter.

And you're going to go down here to advanced, and you're going to select the adapter type. And that's what's going to get you connected. Now once you do that, you come up and you're going to do an IP config on both machines, so you do an IP config on a Linux is if config and what are you going to check You're going to check the network portion and make sure that they both got the same network ID, if they don't have the same network ID is because you probably got one configured as bridge. The other one is Nat. But they both for for for for Mac users, it needs to be bridged to that a bridged networking. Now for VMware, it can be that VMware can use Nat.

That's not a problem. So if I go over here, and I want to go to my settings for this Windows XP box here, and I go to the network adapter I can use now if I'm using VMware. Alright, so that's, that's fine. So that's the problem that people have with networking. They're not looking. They're not looking in the right place.

And they're not doing basic troubleshooting. You have to assume the physical layer. When we talk about troubleshooting network connectivity, always assume the physical layer, and that's going to be your adapters. So, if the adapters aren't right, then it's not going to work. So what happens if you go up here and there's no IP address in Windows XP. That means that Windows XP could not virtualize the onboard adapter, even in VMware.

So if that's the case, then you have to go inside of your adapter, and you have to find another one. Right. So you just have to keep playing with the adapters until you find one. VMware and VirtualBox are not going to be able to virtualize every piece of hardware on your machine. It works great. It works much better.

Not great. It works much better with older hardware than it does with newer hardware. So if you go down, you get a new motherboard and a new GPU, and all that fun stuff that comes on it. It may not be able to recognize or virtualized some of the hardware that's on your motherboard, such as the video, or the network adapter, or some of the controllers, just the way it is, right. But you can make it work, you just going to have to play around with the network setting. But this is the troubleshooting right here.

Confirm that you have an IP address, confirm that the first three octets of that IP address are the same on both Kali and Windows XP. And if you do that, then you're halfway home. Right? Then all you have to do then just be able to ping each other and every lab will be successful. Alright, that's all I got for you. So if you have any questions or you need help troubleshooting your network connectivity, don't hesitate to contact your instructor.

I'll talk with you later. Bye bye.

Sign Up


Share with friends, get 20% off
Invite your friends to LearnDesk learning marketplace. For each purchase they make, you get 20% off (upto $10) on your next purchase.