Learn Understand first, then practice while the concept is still fresh.

M29 - Network Config: GUI

Inspect network settings in graphical tools and understand when a static IP is appropriate versus when DHCP should remain in control.

Networking

Network Config: GUI

Inspect network settings in graphical tools and understand when a static IP is appropriate versus when DHCP should remain in control.

25 min BEGINNER BOTH Curriculum-reviewed
Prerequisites
Module M28 - Network Model: How Networks Work
What you should be able to do after this
  • Find the main GUI network settings on your platform.
  • Read current IP, gateway, and DNS information visually.
  • Explain when a static IP is useful and when DHCP is the better default.

Why This Matters

GUI networking tools are useful because they surface the main network settings without requiring command syntax first.

For beginners, the first goals are:

  • see which connection is active
  • read the current address details
  • understand whether the system is using DHCP or manual settings

1. Inspect Before Changing

Before touching anything, use the GUI to answer:

  • what is my current IP address?
  • what gateway is listed?
  • what DNS servers are listed?
  • is this interface using automatic or manual settings?

On Windows, Network Connections and adapter properties remain one of the clearest routes to detailed settings.

On Linux desktops, NetworkManager-based settings panels or equivalent desktop tools often show the same information in a friendlier layout.

2. DHCP Versus Static Configuration

DHCP is usually the safer default for laptops and ordinary client devices.

A static IP makes more sense when the machine needs a predictable address, such as a server, appliance, or carefully managed lab setup.

But a static address is not just one number. You also need the surrounding configuration to make sense:

  • IP address
  • subnet or mask
  • default gateway
  • DNS settings

Important Caution

If you set a static address without the right gateway, subnet, or DNS settings, the system may look configured but still fail to reach the network properly.

3. Why Static IPs Need Care

Common problems from casual static configuration include:

  • choosing an address already in use
  • choosing an address outside the expected subnet
  • forgetting a working gateway
  • replacing good DNS settings with bad ones

That is why the first networking habit is inspection and understanding, not aggressive manual editing.

What to Ignore for Now

  • enterprise wireless profiles
  • advanced VPN adapter policy
  • multi-homed server design

The goal here is recognizing the key settings and understanding the DHCP-versus-static decision.

Before You Move On

You are ready for the CLI lesson when you can:

  1. find the main GUI network settings on your platform
  2. identify IP, gateway, and DNS information
  3. explain when a static IP is appropriate and when DHCP is better

Next, we inspect and troubleshoot the same ideas from the command line.