> For the complete documentation index, see [llms.txt](https://ajmal-anwar.gitbook.io/zyberspace-by-ajmal/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ajmal-anwar.gitbook.io/zyberspace-by-ajmal/zyberlab/01-lab-setup/vmware-networking-basics.md).

# VMware Networking Basics

Before Active Directory is installed, `DC01` and `CLIENT01` must be able to communicate reliably.

This page covers only the networking concepts needed for the beginner ZyberLab environment.

## Objective

Understand the basic VMware network modes, confirm both VMs are on the same virtual network, and verify connectivity.

## The Three Common VMware Network Modes

### NAT

The VM shares the host computer's internet connection through VMware.

Use NAT when you want:

* a simple beginner setup
* internet access for updates
* the VMs to communicate with each other on the same VMware NAT network

For the first ZyberLab build, NAT is the default choice.

### Host-Only

The VM communicates only with the host and other VMs on the same host-only network.

This is useful for isolated exercises and intentionally vulnerable systems.

### Bridged

The VM appears directly on the same physical network as the host computer.

Bridged networking is not required for the beginner lab and should not be the default for intentionally vulnerable or experimental systems.

## Beginner Network Design

The initial lab remains simple:

```
Internet
   │
Windows Host
   │
VMware NAT
   │
 ┌─┴──────────┐
 │            │
DC01       CLIENT01
```

Both VMs should use the same VMware NAT network.

## Check the IP Configuration

On each VM, open Command Prompt and run:

```
ipconfig
```

Record:

* IPv4 address
* subnet mask
* default gateway
* DNS server

The exact addresses depend on the VMware network configured on your computer.

## Confirm the VMs Are on the Same Network

For a typical `/24` network, addresses similar to the following would be on the same subnet:

```
DC01      192.168.100.10
CLIENT01  192.168.100.20
```

Do not copy these example addresses into your environment unless they match your actual VMware network design.

## Test Connectivity

### Test 1 — Check the local network configuration

Run on both systems:

```
ipconfig
```

Confirm each system has a valid IPv4 address.

### Test 2 — Test the default gateway

Run:

```
ping <default-gateway>
```

A reply indicates that the VM can communicate with the VMware gateway.

### Test 3 — Test VM-to-VM communication

From `CLIENT01`:

```
ping <DC01-IP>
```

From `DC01`:

```
ping <CLIENT01-IP>
```

If ping is blocked, check Windows Firewall before changing the network configuration.

### Test 4 — Check the route

Run:

```
route print
```

Look for the default route and the local subnet.

## DHCP vs Static IP Addresses

At the beginning, DHCP is acceptable while the VMs are being created.

Before `DC01` becomes a domain controller, it should use a stable IP address. We will configure that in the Active Directory setup section because DNS and domain services depend on predictable addressing.

`CLIENT01` can continue using DHCP initially.

## Security Note

Keep experimental systems separated from production or business networks whenever possible. Later, vulnerable web applications and offensive-security exercises should use an isolated VMware network rather than a normal bridged connection.

## Verification

Before continuing, confirm that:

* `DC01` and `CLIENT01` use the same VMware virtual network
* both systems have valid IPv4 addresses
* both systems can reach the VMware gateway
* VM-to-VM connectivity has been checked
* you have recorded the network information in your lab notes

## Key Takeaway

The purpose of this stage is simply to create reliable communication between two virtual machines. More advanced segmentation, firewalls, VLANs, and monitoring networks can be introduced later when there is a clear learning reason.