In this chapter, you’ll learn how to configure your Windows Server network settings. Why is there a whole chapter on this? Well, because it’s a complex topic! It’s a good idea to know what you’re doing and the possibilities.
Prepare Your Virtual Machine
This first stage on your virtual machine is like connecting a network cable to a physical server.
By default, your machine on VirtualBox is protected from the outside for now. It only has access to the NAT network managed by VirtualBox.
Essentially, your server can access the internet, but it is not directly accessible from other devices across the internet.
Look at your network settings. If VirtualBox is configured correctly, you should have a default IP address, mask, gateway, and a DNS server.
Now that I’ve got all that, where do I start? What’s the first thing I need to do?
Like with a Linux distribution where you launch sudo apt update (or sudo apt-get update) followed by sudo apt upgrade (or sudo apt-get upgrade), you’ll check for updates available for your Windows Server.
Get on with these updates – see you on the other side!
Wait, how do I do that?
Head to Server Manager, then the Local Server page:
Here you have all the information you need for networking:
Your server name (WIN-MJVPG2ALISE), the workgroup (WORKGROUP), on the same line the previously installed updates and the update method ("Install updates automatically using Windows Update”), and the date of the last check for updates. All you have to do is click on “Install updates automatically using Windows Update”:
Click on Install now, and I’ll see you in a few minutes!
Excellent, your Windows Server is now ready to go! It’s time to give it a more interesting name than the random one generated by Microsoft.
Name Your Server
Selecting names is not an activity to be taken lightly. Correctly naming a device – in this case, your server – lets you follow its lifecycle.
For example, to name your servers, you could use a code like SRVADNY01 for a server (SRV) with the role ADDS located in New York (NY), which is the first server of its type (01).
It will be easy to find all servers hosted in New York simply by searching for “*NY*” or all Active Directory servers using “*AD*”. Think about a naming convention that makes sense for you.
To rename the server, simply click on its name in the dashboard and click Change:
You’ll have to restart to save the name change.
Next, you need to configure your server's IP address.
Configure Your Server’s TCP/IP Settings
This stage will depend on your existing network setup, including subnets and any addressing plan you may use.
If you click on IPv4 Address Allocated by DHCP, IPv6 Compatible on your dashboard, you’ll see your network interface configuration. If you’re familiar with Windows 10, you’ll recognize this menu.
IPv6 is enabled by default. If your network doesn’t need it, you can disable it by unchecking the box.
You’ll see that Microsoft has several default services on an interface:
Client for Microsoft Networks
File and Printer Sharing for Microsoft Networks
QoS Packet Scheduler
Internet Protocol Version 4 (TCP/IPv4)
Microsoft LLDP Protocol Driver
Internet Protocol Version 6 (TCP/IPv6)
Link Layer Topology Discovery Responder
Link Layer Topology Discovery Mapper I/O Driver
View even more options by selecting properties for Internet Protocol Version 4 (TCP/IPv4) and then clicking Advanced:
Configure your IP settings: address, mask, alias, and gateways under the first tab.
Then configure everything to do with name management in the second tab (DNS). Finally, you’ll configure the addresses of DNS servers in the first section:
If you’re familiar with Linux, this is the equivalent of the resolv.conf file. In the Suffixes section, you’ll specify how DNS requests will be made to the server, either directly or by appending a suffix.
Now onto the final tab, WINS, a similar protocol to DNS but specific to Microsoft and Windows (it stands for Windows Internet Naming Service). It was essential before the 2000s and the democratization of the Active Directory (which uses DNS). It lets you find an IP address using a NetBIOS name:
What’s NetBIOS? And why is it enabled by default?!
NetBIOS is not a protocol! It’s a naming system and software interface that establishes sessions between different computers on the same network. The DNS protocol is doing away with the need for this communication program, but Microsoft still uses it on TCP/IP for compatibility with the Windows NT and XP systems.
Once you’ve finished your IP configuration, your server is almost ready to be joined to your network.
Just a few more settings to go!
Set Up Windows Firewall
Windows includes a built-in firewall letting you block or allow traffic to and from your server. Additional security is essential these days! Why leave port 80 open on a server that doesn’t have the Web Server role?
Once again, head to your local server dashboard:
As you can see, I’ve chosen to configure my first DHCP server in New York, SRVDHCPNY01. I now only have IPv4 configured with an address, mask, gateway, and DNS server (no NetBIOS or other Microsoft network services). My server is operational.
Click on the line that says Windows Defender Firewall: Private On:
The default configuration is pretty good – it blocks any connection to applications not on this list! However, for peace of mind, click Firewall notification settings, Manage Notifications, and select Notify me:
Now your server can access the network (which is practical for configuring roles, features, and services) but will not be fully accessible from the network.
Bravo! Your server is now ready to connect to a network.
Let’s Recap!
Configure Windows Server before connecting to a network (especially if this is a production network!).
Windows Server has various settings that need to be changed before others (the server name, IP, DNS, NetBIOS, etc.).
Windows integrated firewall secure access by blocking any (or all) ports.
You must configure the network correctly before the server becomes active.
In the next chapter, you’ll learn how to handle different configurations (roles, features, services, etc.). Let’s go!
