Map Your PC's Route to the Internet

Use Windows commands to map your PC's local network and route to the internet.

Introduction

30 Second Summary

A website can stop loading while your Wi-Fi icon still looks normal. Without a clear map of the journey, you cannot tell where communication stops.

In this project, you will use Windows Command Prompt to map how traffic moves from your PC through your local network toward an internet destination. You will test each layer separately before revealing the routers along the path.

What You'll Build

You'll see your PC's network journey as a numbered route that reveals where communication succeeds or stops.

By the end of this project, you'll have:

A documented network identity containing your active adapter's IPv4 address, subnet mask, physical address, and default gateway.
A layer-by-layer diagnosis using loopback, gateway reachability, and the ARP cache to pinpoint how far local traffic gets.
A hop-by-hop route that reveals numbered routers, round-trip times, and partial results you can interpret without overclaiming.
Secret Mission: Correlate the first routed hop with the local ARP table. Explain why remote routers do not appear as local neighbors.

Are there any prerequisites?

You need a Windows device with no extra software setup. An active network connection helps with external tests, while blocked or unavailable connectivity still provides useful diagnostic evidence.

Before We Start

Before running any network tests, commit to the question each command will answer. Separating the local TCP/IP stack, default gateway, and internet destination turns one vague connection problem into three clear checkpoints without changing any network settings.

Open and Verify Command Prompt

A reliable network diagnosis needs a command workspace you can trust. Before inspecting an adapter, you need proof that Windows can reach each required networking tool.

Windows gives you Command Prompt for running these tools directly. This step checks four built-in commands through their help output.

In this step, get ready to:

Open Command Prompt through the Run dialog box.
Verify every required networking command through its help output.

Open Command Prompt

The Run dialog box provides a direct route to the Windows command shell. You only need its short command name to start it.

Press Windows key+R to open the Run dialog box.
Enter cmd in the Open field.
Press Enter to start Command Prompt.

You should see a command window with a blinking cursor. That cursor shows that the shell is ready for your first command.

Did Command Prompt Open in Windows Terminal?

On newer Windows devices, Command Prompt may appear inside Windows Terminal. You can follow the same commands because the active shell is still Command Prompt.

Verify Configuration and Reachability Tools

The ipconfig command reads Windows TCP/IP configuration. The ping command checks IP-level reachability with ICMP echo messages.

Check both tools by running these help commands:

ipconfig /?
ping /?

What Do These Help Checks Prove?

The ipconfig /? command asks the configuration tool to display its help content.
The ping /? command asks the reachability tool to display its help content.
The /? option confirms availability without changing your network settings.

You should see help text after the first command. You should see another help screen after the second command.

Good progress. Your configuration tool and reachability tool are responding inside Command Prompt.

No Help Text?

Check that the slash touches the question mark in each command.
Check that you entered each command in the Command Prompt window.

If either tool still fails to display help, help me diagnose why the Windows networking command is unavailable.

Verify Neighbor and Path Tools

The ARP cache records local IPv4-to-physical-address mappings.

The tracert command discovers a path through increasing TTL values.

Check both tools by running these help commands:

arp /?
tracert /?

What Do These Help Checks Prove?

The arp /? command asks the neighbor-table tool to display its help content.
The tracert /? command asks the path-discovery tool to display its help content.
Both help screens confirm that Windows can run the tools needed for later network checks.

You should see ARP help content after the first command. You should see tracert help content after the second command.

Your full diagnostic toolkit is now available. Each required command has responded without changing the network.

Is One Tool Missing?

Check the spelling of the command that did not display help.
Rerun the affected command with no space between / and ?.

If the command still does not respond, help me troubleshoot the missing Windows networking tool.

Before the final check, pause on one question: will the configuration help screen appear again.

Complete the final availability check by running this command:

ipconfig /?

Why Repeat This Check?

The fresh ipconfig /? result is the final proof that Command Prompt remains ready. The output also gives you a visible success state for your worksheet.

You should see the ipconfig help content again. This result confirms that the configuration command responds consistently.

Record in your diagnostic worksheet that ipconfig /?, ping /?, arp /?, and tracert /? displayed help output in Command Prompt.
Leave Command Prompt open for the next network check.

Your worksheet now contains evidence that all four commands are available. It also records that no network settings were changed.

That's the groundwork complete. Your four networking commands are ready for the map.

Next, you'll capture the active adapter's IPv4 address, subnet mask, physical address, and default gateway.

Capture Your Network Identity

Your Windows networking commands are ready in Command Prompt. A test only becomes useful when you know the connection it starts from.

In this step, you'll identify the network adapter carrying your current connection. You'll record its addressing details as the baseline for every test that follows.

In this step, get ready to:

Display the full TCP/IP configuration for every adapter.
Identify the adapter carrying your current connection.
Record the active adapter baseline in your diagnostic worksheet.

Inspect every network adapter

Windows can list several adapters because your PC may support different connection types. The full configuration groups each adapter with the settings Windows currently assigns to it.

Display the full TCP/IP configuration in the Command Prompt from the previous step by running this command:

ipconfig /all

What does this command show?

The ipconfig command asks Windows to display its current TCP/IP configuration.
The /all option expands the output to include the full configuration for every adapter.
The command reads the current configuration without changing any network settings.

You'll see separate sections for the adapters known to Windows. Each section contains the configuration associated with that adapter.

No adapter details in the output?

Check that the command contains one space before the option.
Return to the Command Prompt window where the networking tools displayed help output earlier.

Help me understand why the full network configuration is missing.

Choose the adapter carrying your connection

The adapter list can be fiddly because Windows may show connections you are not currently using. Your current connection type helps narrow the search.

Identify whether your PC currently uses Wi-Fi or a wired Ethernet connection.
Find the adapter section that matches that connection type.
Set aside sections for connection types you are not currently using.
Choose the matching section that contains an IPv4 address.
Confirm that the same section contains a subnet mask.
Confirm that the same section contains a default gateway.

You should now have one adapter section selected as the source of your network baseline. This is the connection Windows is using for the tests ahead.

Build your adapter baseline

Each baseline value answers a different networking question. Together, they describe your PC's local identity and its route beyond the local network.

What do these values mean?

The IPv4 address identifies your adapter on its current IP network.
The subnet mask helps Windows determine which IPv4 destinations belong to the local network.
The MAC address is the adapter's physical address on the local link.
The default gateway is the nearby router Windows uses for traffic leaving the local network.

Return to the diagnostic worksheet from the previous steps.
Record the active adapter name as your active adapter name.
Compare the recorded adapter name with the heading of your chosen Command Prompt section.

The adapter name in your worksheet should match the section you selected.

Record the IPv4 address as your IPv4 address.
Record the subnet mask as your subnet mask.
Compare both recorded values with your chosen adapter section.

The IPv4 address and subnet mask in your worksheet should match the values shown under the same adapter.

Record the physical address as your physical address.
Record the default gateway as your default gateway.
Compare both recorded values with your chosen adapter section.

Your worksheet should now contain the adapter name plus all four baseline values from one adapter section.

Before you rerun the final check, do you expect every worksheet value to appear in the same adapter section?

Display the full configuration again by running this command:

ipconfig /all

What does this final check prove?

The fresh output gives you one source for checking the completed worksheet. Matching every recorded value to one adapter confirms that your baseline does not mix details from unrelated connections.

Find the selected adapter section in the new output.
Compare its adapter name with your worksheet entry.
Compare its IPv4 address with your worksheet entry.
Compare its subnet mask with your worksheet entry.
Compare its physical address with your worksheet entry.
Compare its default gateway with your worksheet entry.

The selected adapter section should match every worksheet entry. This confirms that your active adapter baseline is ready for the next diagnostic layer.

Do the worksheet values come from different sections?

Choose one adapter section that matches your current connection type. Replace any worksheet value copied from a different section.

Help me identify which adapter values belong together.

Good work. Your diagnostic worksheet now has the network identity that anchors every test you run next.

Your active adapter baseline is recorded. Next up, you'll test the local network in layers to discover how far traffic can travel.

Test Local Network Layers

Your active adapter baseline is ready in the diagnostic worksheet. It tells you what IPv4 settings Windows intends to use.

Those values do not demonstrate how far traffic can travel. This step tests each local layer separately.

You will start with the local TCP/IP stack in Command Prompt. You will then test the default gateway before inspecting the ARP cache.

In this step, get ready to:

Verify the local TCP/IP stack with a loopback test.
Test reachability to your recorded default gateway.
Inspect the ARP cache for the gateway's physical-address mapping.

Test the loopback address

The 127.0.0.1 target belongs to the loopback address space. Traffic sent there stays on your PC.

Before you run this, consider whether the local TCP/IP stack should answer its own loopback test.

Test the local TCP/IP stack by running this command:

ping 127.0.0.1

What does this test prove?

Ping sends ICMP echo requests to the loopback target.
Replies confirm that the local TCP/IP stack can answer without traffic leaving your PC.
A failed test becomes evidence of a problem inside the local TCP/IP stack.

When the local stack responds, you will see echo replies with round-trip times. A failure still gives you useful local diagnostic evidence.

Record the result under local TCP/IP stack evidence in your diagnostic worksheet.

You have your first layer documented. Your worksheet now shows whether the local stack can answer traffic addressed to itself.

No loopback replies?

A loopback failure is unusual. Keep the result because it points to the local TCP/IP configuration.

Confirm that the target was entered as 127.0.0.1.

Use this if you want help interpreting the result: Help me understand why my Windows loopback ping did not return replies.

Reach the default gateway

The default gateway is the local router Windows uses to send traffic beyond your PC. Testing it checks whether traffic can reach the first off-PC layer.

Copy the default gateway IPv4 address from your diagnostic worksheet into this field: your recorded default gateway IPv4 address.

Before you run this, predict whether traffic will reach the first device beyond your PC.

Test your PC's path to the default gateway by running this command:

ping [[DEFAULT_GATEWAY_IPV4="your recorded default gateway IPv4 address"]]

What does the gateway result prove?

The gateway is the first off-PC target in this diagnostic sequence.
The ping command checks IP-level connectivity to that target.
Replies show that off-box connectivity to the gateway is possible.
A missing reply may mean that the gateway does not return ICMP replies.

You may see echo replies, Request timed out, or another unreachable result. Each outcome becomes part of your diagnostic record.

Record the gateway result as replies, timeout, or unreachable in your diagnostic worksheet.

Your second layer is now documented. You know whether the gateway answered an IP-level reachability test.

No gateway reply?

A timeout does not prove that the gateway is offline. Some gateways do not return ICMP replies.

Confirm that the address in the command matches the default gateway from your active adapter.
Keep the timeout or unreachable result in your worksheet as evidence.

Use this if you want help reading the result: Help me interpret my default gateway ping result.

Inspect the ARP cache

The ARP cache connects local IPv4 neighbors to physical addresses. A physical address is also called a MAC address.

Before you check, predict whether the gateway will have a current physical-address mapping.

Inspect the current ARP entries by running this command:

arp -a

What does the ARP output show?

The arp -a command displays current ARP entries for applicable adapters.
Each matching entry connects an IPv4 address to a resolved physical address.
The gateway entry represents a neighbor reachable on the local network.

Find the ARP table section for the active adapter from your worksheet.
Look for your recorded default gateway IPv4 address.
Record whether the gateway has a physical-address entry in your diagnostic worksheet.

A matching row documents a current physical-address mapping for the gateway. If no matching row appears, document that no current entry was visible.

That completes your local-layer map. Your worksheet now shows where local communication succeeds or stops.

Can't find the gateway entry?

ARP output can contain separate tables for different adapters. Compare the gateway only with the table for your active adapter.

Compare the gateway address character by character with the value in your worksheet.
Document the entry as absent if no exact match appears.

Use this if the ARP sections are difficult to match: Help me compare my Windows ARP output with my active adapter.

Your local layers are mapped. Next, you'll test how far ping can see beyond the gateway.

Test External Reachability

Your earlier Command Prompt checks confirmed the local TCP/IP stack. They also tested your default gateway.

Traffic can still stop beyond the gateway. This step checks an external IPv4 destination with ICMP echo requests while leaving every network setting unchanged.

In this step, get ready to:

Test whether an external IPv4 destination responds to ping.
Document the destination result with any displayed round-trip times.
Determine the boundary of the evidence that ping provides.

Reach beyond the gateway

The address 8.8.8.8 belongs to Google Public DNS. This target lets you test external reachability without changing your DNS settings.

Switch back to the Command Prompt from earlier.
Predict whether the output will show only a destination result or reveal the path as well.
Test external IPv4 reachability by running this command:

ping 8.8.8.8

What does this command test?

The ping command sends ICMP echo requests to 8.8.8.8.
Returned echo replies provide IP-level connectivity evidence for the destination.
Displayed round-trip times show how long the responses took.

Classify the output as echo replies, Request timed out, or another destination result.
Record that classification in your diagnostic worksheet.
Record any displayed round-trip times in your diagnostic worksheet.

Replies show that the destination returned ICMP echo responses. A timeout means no echo response arrived within the timeout.

Seeing a Timeout or Another Result?

Some networks block ICMP echo responses. A timeout alone does not prove that all internet connectivity is broken.

Keep the result as diagnostic evidence. Help me interpret my external ping result.

Inspect the evidence boundary

The ping output reports whether the destination replied. It can also show round-trip times.

Scan the output for numbered hop rows.
Try to identify the intermediate routers using only the output.

Your output contains no numbered list of intermediate routers. That missing list is the intended shortfall.

The ping result provides endpoint reachability evidence. It cannot identify the routers that handled the traffic.

Add a note to your diagnostic worksheet that ping cannot identify intermediate routers.
Confirm that your worksheet contains the destination result.
Confirm that your worksheet contains any displayed round-trip times plus the missing-router observation.

You have turned either a reply or a timeout into usable diagnostic evidence. Next, you will reveal the responding routers as numbered hops.

Reveal the Router Path

Your ping 8.8.8.8 test showed what happened at the destination. It left the intermediate routers hidden.

Now, Windows Command Prompt can expose that missing path with tracert. The command sends ICMP probes with increasing TTL values to reveal responding routers one hop at a time.

In this step, get ready to:

Trace the route toward Microsoft's public hostname.
Read the details in each responding hop.
Compare the first responding hop with your saved network baseline.

Trace the route to Microsoft

Windows waits for responses from each hop along the route. The trace may pause while those probes complete.

Before you run the trace, do you expect every router to answer? The output will test your prediction.

Reveal the path to Microsoft's public hostname by running this command:

tracert www.microsoft.com

How Does Tracert Reveal the Path?

The tracert command starts with a low TTL value.
A low TTL expires at an early router. The resulting ICMP response identifies that hop.
Windows increases the TTL until the destination responds or the maximum hop count is reached.

Wait for Command Prompt to complete the trace or reach its stopping point.
Check the output for a completed route or a partial route with numbered rows.

You'll see a numbered route toward www.microsoft.com. Some rows may contain router details while other rows may contain * characters.

Seeing Only Asterisks?

A row may show only * characters. That router did not return the expected ICMP response.

A partial trace still documents where responses stopped. It does not prove that all network communication failed.

Help me interpret my partial tracert output.

Read each responding hop

Each responding tracert row is a compact report for one hop.

Locate the first numbered row that contains a router address or name.
Read the hop number at the left edge of that row.
Read the three round-trip measurements shown in milliseconds.
Identify the router address or name at the right edge.
Repeat this reading pattern for each responding row.
Record the completed or partial numbered route in your diagnostic worksheet.

Your worksheet now preserves the route exactly as Windows reported it.

Compare the first hop with your gateway

Your default gateway is the local router Windows uses to send traffic beyond your network. Comparing it with the first responding hop connects your saved baseline to the live route.

Asterisks indicate missing ICMP responses from individual probes. They do not by themselves prove that the total route failed.

Before you compare the values, do you expect the first responding hop to match the gateway you recorded? The comparison comes next.

Locate the address of the first responding hop in your trace.
Compare that address with the default gateway in your diagnostic worksheet.
Record whether the two addresses match.
Record your interpretation of any * characters.
Check for responding rows after any row containing * characters.

Your comparison now shows whether the first responding hop matches your default gateway. Any later responding rows prove that the trace continued beyond an earlier missing response.

You have closed ping's visibility gap. Your worksheet now maps the numbered path from your PC toward www.microsoft.com.

Secret mission

Correlate the Routed Path with ARP

Turn your existing route into a local-link diagnosis. Correlate the first responding hop with your recorded default gateway and current ARP entries. Then explain why remote routers do not appear as local ARP neighbors.

Clean Up Your Resources

This project used only Windows Command Prompt plus your diagnostic worksheet. Everything ran locally with no paid resources or ongoing costs.

Resources you used:

Your diagnostic worksheet containing the active adapter baseline plus your network test observations.
Your open Windows Command Prompt session used for read-only networking tests.

Keep everything running

No action is required. Choose this option if you want to repeat the diagnostic workflow or keep your results for comparison.

Keep your diagnostic worksheet as a baseline for future network troubleshooting.
Keep Command Prompt open if you plan to repeat any tests now.
Leave your network configuration unchanged because every command in this project was read-only.

Pause - I'll come back to this later

This project has no background process to pause. Your recorded observations remain useful after Command Prompt closes.

Close the Command Prompt window.
Keep your diagnostic worksheet so you can compare future results with this baseline.

Delete - I don't want to use this again

Removing your notes is safe here. Your network configuration stays unchanged because the project only inspected network state.

Delete the diagnostic worksheet from the place where you recorded it.
Close the Command Prompt window.

Your Network Settings Stay Intact

This cleanup removes only your recorded observations. No adapters or addresses were changed during the project.

Nice Work!

Excellent work! You mapped how traffic leaves your Windows PC with a repeatable diagnostic workflow that preserved every network setting.

You've learned how to:

Captured your active adapter baseline with ipconfig /all. Your worksheet records its IPv4 address, subnet mask, physical address, plus default gateway.
Tested the local TCP/IP stack, default gateway, plus an external destination as separate layers. Interpreted ICMP replies, round-trip times, timeouts, plus unreachable results as diagnostic evidence.
Exposed ping's visibility limit before revealing the route with tracert. Read hop numbers, latency measurements, router identities, plus asterisks without assuming that a silent hop stopped the entire route.
Secret Mission: Correlated the first responding hop with the ARP cache. Explained the local-link boundary that keeps remote routed hops out of the local neighbor table.

Ready to quiz yourself?