<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Dean Humphrey | IT Support &amp; Networking Student on Medium]]></title>
        <description><![CDATA[Stories by Dean Humphrey | IT Support &amp; Networking Student on Medium]]></description>
        <link>https://medium.com/@deanhumphreyab?source=rss-4b19b884093a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ld8sRscZWqqf0gDPIJyLwg.png</url>
            <title>Stories by Dean Humphrey | IT Support &amp;amp; Networking Student on Medium</title>
            <link>https://medium.com/@deanhumphreyab?source=rss-4b19b884093a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 16:52:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@deanhumphreyab/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Windows Networking Commands for Entry-Level IT Support | Dean Humphrey]]></title>
            <link>https://medium.com/@deanhumphreyab/windows-networking-commands-for-entry-level-it-support-dean-humphrey-02cc34e1de0e?source=rss-4b19b884093a------2</link>
            <guid isPermaLink="false">https://medium.com/p/02cc34e1de0e</guid>
            <category><![CDATA[it-support]]></category>
            <category><![CDATA[troubleshooting]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[comptia]]></category>
            <category><![CDATA[windows]]></category>
            <dc:creator><![CDATA[Dean Humphrey | IT Support & Networking Student]]></dc:creator>
            <pubDate>Wed, 10 Jun 2026 06:57:49 GMT</pubDate>
            <atom:updated>2026-06-10T06:57:49.520Z</atom:updated>
            <content:encoded><![CDATA[<h3>A practical learning note on using basic Windows command-line tools for connectivity and network troubleshooting.</h3><p>I am Dean Humphrey, an entry-level IT support and networking candidate based in Edmonton, Alberta, Canada. As part of my IT support and networking learning path, I have been practicing basic Windows networking commands and learning how they fit into a structured troubleshooting process.</p><p>This article is a beginner-friendly learning note. It is not meant to be an advanced networking guide. The goal is to understand how common Windows commands can help identify whether a problem is related to IP configuration, connectivity, routing, DNS, or active network connections.</p><p>In entry-level IT support, a user may describe many different problems as “the internet is not working.” The job of troubleshooting is to slow that down and check what is actually failing.</p><h3>Why Windows networking commands matter</h3><p>Windows networking commands are useful because they give quick information about what the computer is doing on the network.</p><p>They can help answer questions like:</p><ul><li>Does the computer have an IP address?</li><li>Does it have a default gateway?</li><li>What DNS servers is it using?</li><li>Can it reach the router?</li><li>Can it reach the internet?</li><li>Can it resolve a website name?</li><li>Where does traffic appear to stop?</li><li>Are there active network connections?</li></ul><p>These commands do not fix every issue by themselves, but they help narrow the problem.</p><p>That matters because good troubleshooting is not guessing. It is testing one layer at a time.</p><h3>Start with the user’s symptom</h3><p>A user might say:</p><pre>The internet is down.</pre><p>That could mean many different things.</p><p>It could be:</p><ul><li>Wi-Fi is disconnected</li><li>the device has no valid IP address</li><li>the router is not reachable</li><li>DNS is failing</li><li>a website is down</li><li>a browser issue is causing the problem</li><li>a VPN or firewall is interfering</li><li>the internet connection is working, but one service is not</li></ul><p>Before changing settings, it helps to gather basic information.</p><p>That is where commands like ipconfig, ping, tracert, netstat, and nslookup are useful.</p><h3>ipconfig</h3><p>The ipconfig command shows basic network configuration on a Windows computer.</p><pre>ipconfig</pre><p>This can show information such as:</p><ul><li>IPv4 address</li><li>subnet mask</li><li>default gateway</li><li>network adapter status</li></ul><p>The default gateway is especially important because it usually points to the router or network device the computer uses to reach other networks.</p><p>If a computer has no valid IP address, the problem may not be DNS or the website. It may be a local network or DHCP issue.</p><p>One warning sign is an address like:</p><pre>169.254.x.x</pre><p>That can mean Windows assigned itself an automatic private IP address because it did not receive a valid address from DHCP.</p><p>In that case, the next troubleshooting step would be different than if the device had a normal local IP address.</p><h3>ipconfig /all</h3><p>The more detailed version is:</p><pre>ipconfig /all</pre><p>This shows more information, including:</p><ul><li>physical address / MAC address</li><li>DHCP status</li><li>DNS servers</li><li>lease information</li><li>adapter descriptions</li></ul><p>This is useful when checking whether a computer is receiving expected network settings.</p><p>For example, if DNS is failing, ipconfig /all can show which DNS server the computer is trying to use. That can help separate a DNS problem from a more general connectivity problem.</p><h3>ping</h3><p>The ping command tests whether another device or address can be reached.</p><p>A common first test is the default gateway.</p><p>For example:</p><pre>ping 192.168.1.1</pre><p>The exact address depends on the network.</p><p>If the computer cannot reach the default gateway, the issue may be local: Wi-Fi, Ethernet, adapter settings, router connection, or local firewall rules.</p><p>Another useful test is pinging a public IP address:</p><pre>ping 8.8.8.8</pre><p>If the computer can reach an IP address but cannot reach websites by name, DNS becomes more likely.</p><p>A simple troubleshooting idea is:</p><pre>If IP works but names fail, check DNS.<br>If both IP and names fail, check broader connectivity.</pre><p>Ping does not prove everything, because some systems block ICMP traffic. But it is still useful as an early test.</p><h3>ping with a hostname</h3><p>You can also ping a website name:</p><pre>ping example.com</pre><p>This tests two things:</p><ol><li>whether the name can resolve to an IP address</li><li>whether the system can attempt to reach it</li></ol><p>If pinging an IP address works but pinging a hostname fails, that points more strongly toward DNS or name resolution.</p><p>However, if the hostname resolves but the ping does not reply, that does not always mean the website is broken. Some servers do not respond to ping.</p><p>That is why results need to be interpreted carefully.</p><h3>nslookup</h3><p>The nslookup command is used to test DNS name resolution.</p><pre>nslookup example.com</pre><p>This can show:</p><ul><li>the DNS server being used</li><li>whether the domain resolves</li><li>the IP address returned</li><li>timeout or lookup errors</li></ul><p>This is one of the most useful commands when trying to separate DNS issues from general connectivity issues.</p><p>If nslookup fails but general IP connectivity works, DNS may be the issue.</p><p>If nslookup works but the website still does not load, the problem may be elsewhere, such as the browser, firewall, website, proxy, VPN, or application layer.</p><h3>ipconfig /flushdns</h3><p>Sometimes DNS issues can involve cached records.</p><p>Windows has a local DNS resolver cache. To clear it, the command is:</p><pre>ipconfig /flushdns</pre><p>This clears the local DNS cache.</p><p>This is not a fix for every DNS issue, but it can help if the system has stored an old or incorrect DNS result.</p><p>After clearing the DNS cache, it makes sense to test again using:</p><pre>nslookup example.com</pre><p>or by trying the website again.</p><h3>tracert</h3><p>The tracert command shows the route traffic takes toward a destination.</p><pre>tracert example.com</pre><p>This can help show where traffic appears to stop or slow down.</p><p>For entry-level troubleshooting, I think of tracert as a way to understand the path, not as a magic answer. It can show whether traffic leaves the local network, reaches the ISP, or stops somewhere along the way.</p><p>Some routers or networks may block responses, so missing hops do not always prove a failure. Still, it is useful when comparing results and looking for obvious breaks.</p><h3>netstat</h3><p>The netstat command shows active network connections and listening ports.</p><pre>netstat</pre><p>A more detailed version is:</p><pre>netstat -ano</pre><p>This can show:</p><ul><li>local addresses</li><li>foreign addresses</li><li>connection states</li><li>process IDs</li></ul><p>For beginner IT support learning, netstat is useful for understanding that the computer may have many active connections at once.</p><p>It can also help when investigating whether an application is communicating over the network, though interpreting the output takes practice.</p><h3>A basic troubleshooting flow</h3><p>A simple Windows networking troubleshooting flow could look like this:</p><pre>1. Ask what the user is experiencing.<br>2. Check whether the device is connected to the network.<br>3. Run ipconfig.<br>4. Confirm the IP address, subnet, gateway, and adapter status.<br>5. Ping the default gateway.<br>6. Ping a public IP address.<br>7. Test a hostname.<br>8. Use nslookup to check DNS.<br>9. Use tracert if the route needs to be checked.<br>10. Document the results.</pre><p>This type of flow helps avoid random changes.</p><p>Instead of immediately changing DNS servers, restarting everything, or assuming the website is down, the process checks one layer at a time.</p><h3>Example: possible DNS issue</h3><p>A basic DNS-related pattern might look like this:</p><pre>ping 8.8.8.8 works<br>ping example.com fails<br>nslookup example.com fails</pre><p>That could suggest a DNS problem.</p><p>Possible next checks:</p><ul><li>confirm DNS server settings with ipconfig /all</li><li>test another domain</li><li>compare with another device</li><li>clear the DNS cache</li><li>check whether a VPN or filtering tool is changing DNS behavior</li><li>confirm whether the issue affects one site or all sites</li></ul><p>This is useful because the user’s original complaint might still be “the internet is down,” even though the network connection itself may be working.</p><h3>Example: broader connectivity issue</h3><p>A broader connectivity problem might look like this:</p><pre>No valid IP address<br>No default gateway<br>Cannot ping gateway<br>Cannot ping public IP<br>Cannot resolve names</pre><p>In that case, DNS may not be the main issue.</p><p>Possible next checks:</p><ul><li>Wi-Fi or Ethernet connection</li><li>adapter status</li><li>router/modem status</li><li>DHCP issue</li><li>physical cable or signal problem</li><li>local network outage</li><li>firewall or security software</li></ul><p>This is why it is important not to jump straight to DNS without checking basic connectivity first.</p><h3>What I learned</h3><p>The biggest lesson from practicing Windows networking commands is that each command answers a different question.</p><p>ipconfig helps check configuration.</p><p>ping helps test reachability.</p><p>nslookup helps test DNS.</p><p>tracert helps look at the route.</p><p>netstat helps review active connections.</p><p>Together, they support a structured troubleshooting process.</p><p>The goal is not just to memorize commands. The goal is to understand what each command can confirm or rule out.</p><h3>How this connects to entry-level IT support</h3><p>These commands are useful for entry-level IT support because they support practical troubleshooting habits:</p><ul><li>checking the basics first</li><li>separating local network issues from internet issues</li><li>separating DNS problems from general connectivity problems</li><li>documenting test results</li><li>avoiding random changes</li><li>communicating findings clearly</li></ul><p>This kind of structure matters in help desk and technical support work because users usually describe symptoms, not causes.</p><p>A support technician needs to translate the symptom into testable questions.</p><h3>Commands covered in this note</h3><pre>ipconfig</pre><p>Shows basic IP configuration.</p><pre>ipconfig /all</pre><p>Shows detailed adapter, DHCP, and DNS information.</p><pre>ping</pre><p>Tests reachability to an IP address or hostname.</p><pre>nslookup</pre><p>Tests DNS name resolution.</p><pre>ipconfig /flushdns</pre><p>Clears the local DNS resolver cache.</p><pre>tracert</pre><p>Shows the route traffic takes toward a destination.</p><pre>netstat</pre><p>Shows active network connections and related network information.</p><h3>Conclusion</h3><p>Windows networking commands are a practical part of entry-level IT support learning. They help turn a vague issue like “the internet is not working” into a structured troubleshooting process.</p><p>By checking IP configuration, testing reachability, reviewing DNS, looking at routes, and documenting results, it becomes easier to understand what is actually failing.</p><p>This is part of my ongoing learning in IT support, networking fundamentals, troubleshooting, and technical documentation.</p><p>Portfolio:<br><a href="https://deanhumphrey.ca/">https://deanhumphrey.ca</a></p><p>Lab Log:<br><a href="https://deanhumphrey.ca/lab.html">https://deanhumphrey.ca/lab.html</a></p><p>GitHub:<br><a href="https://github.com/deanhumphreyab">https://github.com/deanhumphreyab</a></p><p>Medium:<br><a href="https://medium.com/@deanhumphreyab">https://medium.com/@deanhumphreyab</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=02cc34e1de0e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DNS Troubleshooting Basics for Entry-Level IT Support | Dean Humphrey]]></title>
            <link>https://medium.com/@deanhumphreyab/dns-troubleshooting-basics-for-entry-level-it-support-dean-humphrey-49d52dda8b8c?source=rss-4b19b884093a------2</link>
            <guid isPermaLink="false">https://medium.com/p/49d52dda8b8c</guid>
            <category><![CDATA[it-support]]></category>
            <category><![CDATA[dns]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[troubleshooting]]></category>
            <category><![CDATA[comptia]]></category>
            <dc:creator><![CDATA[Dean Humphrey | IT Support & Networking Student]]></dc:creator>
            <pubDate>Mon, 18 May 2026 00:08:34 GMT</pubDate>
            <atom:updated>2026-05-18T00:08:34.371Z</atom:updated>
            <content:encoded><![CDATA[<h4>A practical beginner-friendly walkthrough of how to separate DNS problems from general network connectivity issues.</h4><p>I am Dean Humphrey, an entry-level IT support and networking candidate based in Edmonton, Alberta, Canada. As part of my IT support and networking learning path, I have been practicing basic troubleshooting methods for common network issues.</p><p>One area I have been focusing on is **DNS troubleshooting**. DNS is one of those topics that comes up often in IT support because users may describe the problem as “the internet is down,” when the actual issue might be name resolution.</p><p>This article is a basic learning note about how I approach DNS troubleshooting at an entry level. It is not meant to be an advanced networking guide. The goal is to understand the first steps: how to tell whether the issue is DNS, general connectivity, or something else.</p><h3>What DNS does</h3><p>DNS stands for **Domain Name System**.</p><p>A simple way to think about DNS is that it helps translate human-friendly names into IP addresses.</p><p>For example, when someone types a website name into a browser, the computer needs to find the IP address for that website before it can connect.</p><p>The basic idea is:</p><pre>Website name → DNS lookup → IP address → connection attempt</pre><p>That is why DNS troubleshooting is important. It helps separate a name-resolution problem from a broader network problem.</p><h3>Example user complaint</h3><p>A common support-style complaint might sound like this:</p><pre>“I can’t get to the website.”</pre><p>That does not immediately tell us what is broken.</p><p>It could be:</p><ul><li>the user has no network connection</li><li>Wi-Fi is disconnected</li><li>the router or modem is having issues</li><li>the website itself is down</li><li>DNS is not resolving the hostname</li><li>the browser has a cached or extension-related problem</li><li>a firewall, VPN, or security tool is interfering</li></ul><p>The first step is not to guess. The first step is to narrow the problem.</p><h3>Step 1: Check basic connectivity</h3><p>Before assuming DNS is the problem, I would first check whether the device has network connectivity.</p><p>On Windows, a basic command is:</p><pre>ipconfig</pre><p>This can show whether the system has an IP address, default gateway, and DNS server assigned.</p><p>Things I would look for include:</p><ul><li>Does the device have an IPv4 address?</li><li>Does it have a default gateway?</li><li>Does it have DNS servers listed?</li><li>Is the address expected for the network?</li><li>Does it look like an automatic private address, such as 169.254.x.x?</li></ul><p>If the device has no valid IP address or no gateway, the issue may be more basic than DNS.</p><h3>Step 2: Test reachability by IP address</h3><p>A useful next step is testing whether the computer can reach something by IP address.</p><p>For example:</p><pre>ping 8.8.8.8</pre><p>If this works, the computer may have general internet connectivity.</p><p>If this does not work, the problem may be with connectivity, routing, Wi-Fi, the router, the ISP connection, a firewall rule, or another network issue.</p><p>This step matters because DNS is about resolving names. If IP connectivity does not work either, then DNS may not be the main problem.</p><p>A simple way to think about it:</p><pre>If IP address works but website name fails, DNS becomes more likely.<br>If both IP address and website name fail, the issue may be broader than DNS.</pre><h3>Step 3: Test a website name</h3><p>After checking IP reachability, I would test a hostname.</p><p>For example:</p><pre>ping example.com</pre><p>This checks whether the system can resolve the name and attempt to reach it.</p><p>If pinging an IP address works but pinging a domain name fails, that points more strongly toward DNS.</p><p>However, it is also important to remember that some websites block ping. So the result needs to be interpreted carefully. A failed ping does not always prove the website is down.</p><p>That is why DNS-specific tools are useful.</p><h3>Step 4: Use nslookup</h3><p>On Windows, one common DNS testing tool is:</p><pre>nslookup example.com</pre><p>This asks DNS to resolve the domain name.</p><p>With nslookup, I would look for:</p><ul><li>whether the name resolves to an IP address</li><li>which DNS server answered the request</li><li>whether there is a timeout</li><li>whether the domain returns an error</li><li>whether the DNS server looks expected</li></ul><p>If nslookup fails, but general internet connectivity appears to work, that gives a stronger sign that DNS resolution may be the issue.</p><h3>Step 5: Check the configured DNS server</h3><p>If DNS lookups are failing, I would check which DNS server the computer is using.</p><p>Again, this can be seen with:</p><pre>ipconfig /all</pre><p>The DNS server might come from:</p><ul><li>the router</li><li>the ISP</li><li>a manually configured DNS server</li><li>a VPN client</li><li>a workplace network configuration</li><li>security software or filtering software</li></ul><p>If the DNS server is wrong, unreachable, or not responding, websites may fail by name even when other parts of the network are working.</p><h3>Step 6: Try clearing the DNS cache</h3><p>Sometimes DNS problems can be related to cached records.</p><p>On Windows, a common command is:</p><pre>ipconfig /flushdns</pre><p>This clears the local DNS resolver cache.</p><p>This is not a magic fix for every problem, but it can help when the computer has cached an old or incorrect DNS result.</p><p>After clearing the cache, I would test again using:</p><pre>nslookup example.com</pre><p>or by trying the website again in the browser.</p><h3>Step 7: Compare with another device</h3><p>Another useful troubleshooting step is comparing the issue with another device on the same network.</p><p>For example:</p><pre>Does the website work on another computer?<br>Does it work on a phone using the same Wi-Fi?<br>Does it work on mobile data?<br>Does every website fail, or only one website?</pre><p>This helps determine whether the issue is:</p><ul><li>device-specific</li><li>network-wide</li><li>related to one website</li><li>related to DNS</li><li>related to the browser</li><li>related to the ISP or router</li></ul><p>In IT support, comparison testing is useful because it helps narrow the scope.</p><h3>Step 8: Avoid jumping to conclusions</h3><p>One of the main things I am learning is that troubleshooting should be structured.</p><p>It is easy to assume:</p><pre>“The internet is broken.”</pre><p>But that could mean many different things.</p><p>A better process is:</p><pre>Check IP configuration.<br>Check basic connectivity.<br>Test by IP address.<br>Test by hostname.<br>Use nslookup.<br>Check DNS server settings.<br>Clear DNS cache if appropriate.<br>Compare with another device.<br>Document what happened.</pre><p>That process is more reliable than randomly changing settings.</p><h3>Basic DNS troubleshooting flow</h3><p>Here is a simple beginner-friendly flow:</p><pre>1. Can the device connect to the network?<br>2. Does it have a valid IP address?<br>3. Can it reach an IP address?<br>4. Can it resolve a domain name?<br>5. What DNS server is it using?<br>6. Does nslookup return an answer?<br>7. Does another device have the same issue?<br>8. What changed recently?</pre><p>This kind of checklist helps keep troubleshooting organized.</p><h3>What I learned</h3><p>From practicing DNS troubleshooting basics, the biggest lesson is that DNS issues can look like general internet problems to the user.</p><p>A user may say:</p><pre>“The internet is not working.”</pre><p>But the actual technical issue might be:</p><pre>The device has internet connectivity, but DNS name resolution is failing.</pre><p>That distinction matters.</p><p>It changes what you test, what you document, and what fix you try next.</p><h3>How this connects to entry-level IT support</h3><p>DNS troubleshooting is a useful entry-level IT support skill because it combines several important habits:</p><ul><li>asking what the user is actually experiencing</li><li>checking the basics first</li><li>separating connectivity from name resolution</li><li>using command-line tools</li><li>comparing results across devices</li><li>documenting symptoms and test results</li><li>avoiding random changes without evidence</li></ul><p>The goal is not to memorize commands without understanding them. The goal is to learn what each command helps confirm or rule out.</p><h3>Commands used in this learning note</h3><p>Here are the basic Windows commands from this note:</p><pre>ipconfig</pre><p>Shows basic IP configuration.</p><pre>ipconfig /all</pre><p>Shows more detailed network configuration, including DNS servers.</p><pre>ping 8.8.8.8</pre><p>Tests reachability to an IP address.</p><pre>ping example.com</pre><p>Tests name resolution and reachability to a hostname.</p><pre>nslookup example.com</pre><p>Tests DNS name resolution.</p><pre>ipconfig /flushdns</pre><p>Clears the local DNS resolver cache.</p><h3>Conclusion</h3><p>DNS troubleshooting is an important basic skill for IT support because DNS problems can make a working connection appear broken.</p><p>A structured approach helps separate DNS issues from general connectivity problems. By checking IP configuration, testing reachability, using nslookup, reviewing DNS server settings, and comparing with another device, it becomes easier to understand what is actually failing.</p><p>This is part of my ongoing learning in IT support, networking fundamentals, troubleshooting, and documentation.</p><p>Portfolio:<br> <a href="https://deanhumphrey.ca/?utm_source=chatgpt.com">https://deanhumphrey.ca</a></p><p>GitHub:<br> <a href="https://github.com/deanhumphreyab">https://github.com/deanhumphreyab</a></p><p>Medium:<br> <a href="https://medium.com/@deanhumphreyab">https://medium.com/@deanhumphreyab</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=49d52dda8b8c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a Simple Audio and Video Muxing GUI with Python and FFmpeg | Dean Humphrey]]></title>
            <link>https://medium.com/@deanhumphreyab/building-a-simple-audio-and-video-muxing-gui-with-python-and-ffmpeg-dean-humphrey-f4f5aee095d5?source=rss-4b19b884093a------2</link>
            <guid isPermaLink="false">https://medium.com/p/f4f5aee095d5</guid>
            <category><![CDATA[it-support]]></category>
            <category><![CDATA[learning-in-public]]></category>
            <category><![CDATA[troubleshooting]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[ffmpeg]]></category>
            <dc:creator><![CDATA[Dean Humphrey | IT Support & Networking Student]]></dc:creator>
            <pubDate>Mon, 11 May 2026 15:26:31 GMT</pubDate>
            <atom:updated>2026-05-11T15:26:31.010Z</atom:updated>
            <content:encoded><![CDATA[<h4>A practical learning project by Dean Humphrey using Python and FFmpeg to replace audio in video files without re-encoding the video stream.</h4><p>I am Dean Humphrey, an entry-level IT support and networking candidate based in Edmonton, Alberta, Canada. I recently worked on a small technical project called **audio-video-mux-gui**. The goal was simple: build a basic graphical tool that can replace or append audio in a video file without re-encoding the video stream.</p><p>This was not meant to be a large software project. It was a practical learning exercise focused on workflow, troubleshooting, documentation, and using existing tools properly. The project uses **Python** for the interface and **FFmpeg** for the actual media processing.</p><p>For me, this fits into my broader IT learning path because it involves several useful technical habits: understanding dependencies, working with files, testing outputs, documenting a repeatable process, and solving a real workflow problem with a small tool.</p><blockquote>The problem I wanted to solve</blockquote><p>When working with video files, sometimes the video itself is fine, but the audio needs to be changed. For example, you may have a video file where the original audio needs to be replaced with a restored version, a corrected track, or a cleaner final mix.</p><p>The inefficient way to do this is to re-export the entire video through an editor. That can take longer, reduce quality if the settings are wrong, and create unnecessary extra work.</p><p>What I wanted was a simpler workflow:</p><p>Original video file + new audio file = video with updated audio</p><p>The important part was avoiding unnecessary video re-encoding. If the video stream does not need to change, it should be copied as-is while only the audio track is replaced or added.</p><p>That is where FFmpeg is useful.</p><blockquote>Why FFmpeg</blockquote><p>FFmpeg is a command-line tool used for working with audio and video files. It can inspect, convert, copy, combine, and process media streams.</p><p>For this project, the main value of FFmpeg is that it can copy the video stream without re-encoding it. That means the video quality can be preserved while the audio is changed.</p><p>A simplified version of the idea looks like this:</p><p>ffmpeg -i input-video.mp4 -i new-audio.wav -c:v copy -c:a aac output-video.mp4</p><p>The exact command can vary depending on the file types and the desired output, but the core idea is:</p><p>-c:v copy</p><p>That tells FFmpeg to copy the video stream instead of re-encoding it.</p><p>This was one of the main technical points of the project. The tool is not trying to rebuild video processing from scratch. It is using a reliable existing dependency and wrapping the workflow in a more convenient interface.</p><blockquote>Why build a GUI?</blockquote><p>A command-line workflow is powerful, but it is not always the fastest option when repeating the same task. A GUI can make the process easier by letting the user select files, choose an output location, and run the process without manually typing long commands every time.</p><p>The goal of the GUI was not to hide the technical process completely. It was to make the workflow more repeatable and reduce the chance of simple mistakes, such as selecting the wrong file or typing the wrong output path.</p><p>This project helped me think about how small tools can support practical troubleshooting and workflow improvement.</p><h3>What I learned from the project</h3><blockquote>1. Dependencies matter</blockquote><p>The Python script depends on FFmpeg being installed and available on the system. That means the program is not fully self-contained unless FFmpeg is bundled or properly installed.</p><p>This is an important IT support lesson. A program may be written correctly but still fail if a required dependency is missing, installed incorrectly, or not available in the system PATH.</p><p>A useful troubleshooting question is:</p><p>Is the problem in the program, or is the required tool missing from the environment?</p><p>That same pattern applies to many support situations, not just media tools.</p><blockquote>2. Clear workflow matters</blockquote><p>The technical process is only part of the project. The workflow also matters.</p><p>A good basic workflow needs to answer:</p><p>What file is being used as the video source? <br>What file is being used as the audio source? <br>Where should the new file be saved? <br>What should happen if the command fails? <br>How does the user know the process completed successfully?</p><p>Thinking through those questions helps make the tool more practical. Even a small project benefits from predictable steps and clear outputs.</p><blockquote>3. Preserving quality requires understanding the command</blockquote><p>One of the biggest reasons for using FFmpeg in this project was to avoid re-encoding the video. Re-encoding can take more time and may reduce quality if the settings are not chosen carefully.</p><p>Using stream copy for the video is a better approach when the video does not need to be changed.</p><p>That is a useful technical distinction:</p><p>Changing the container or audio track is not the same as re-encoding the video.</p><p>Understanding that difference helps prevent unnecessary processing and keeps the workflow cleaner.</p><blockquote>4. Documentation makes small projects more useful</blockquote><p>A small project can still be difficult to use later if it is not documented.</p><p>For this kind of project, useful documentation should explain:</p><p>What the tool does <br>What it does not do <br>What dependencies it needs <br>How to run it <br>What kind of input files are expected <br>What kind of output file it creates</p><p>This is something I am working on improving. Documentation is part of the project, not an afterthought.</p><blockquote>How this connects to IT support learning</blockquote><p>This project is media-related, but the learning process connects well to IT support and troubleshooting.</p><p>It involved:</p><p>- identifying a practical problem<br>- choosing an appropriate tool<br>- understanding an external dependency<br>- building a repeatable workflow<br>- testing whether the output worked<br>- documenting the process<br>- keeping the scope realistic</p><p>Those same habits are useful in help desk and technical support work.</p><p>For example, when troubleshooting a system issue, the process is usually not just “try random fixes.” A better approach is to understand the problem, isolate the cause, check dependencies, test one change at a time, and document what worked.</p><p>That is the mindset I am trying to build through small projects and lab notes.</p><blockquote>Project scope</blockquote><p>This project is intentionally simple. It is not a full video editor. It is not meant to replace professional editing software.</p><p>The purpose is narrower:</p><p>Use a Python GUI to make an FFmpeg audio/video muxing workflow easier to run.</p><p>That limited scope is useful because it keeps the project realistic and focused. Small tools can still be valuable when they solve a specific problem clearly.</p><blockquote>Future improvements</blockquote><p>Some possible improvements for the project include:</p><p>- improving the README documentation<br>- adding clearer setup instructions for FFmpeg<br>- adding better error messages<br>- showing the generated FFmpeg command before running it<br>- adding progress feedback<br>- supporting more output options<br>- testing the workflow on Windows and Linux</p><p>Those improvements would make the project easier to use and easier to troubleshoot.</p><blockquote>Conclusion</blockquote><p>The **audio-video-mux-gui** project was a practical exercise in using Python, FFmpeg, file handling, and documentation to solve a specific workflow problem.</p><p>The main lesson was not just how to replace audio in a video file. The more important lesson was how to approach a technical problem in a structured way: understand the goal, identify the right tool, manage dependencies, preserve quality where possible, and document the process.</p><p>I am continuing to build small projects and lab notes as part of my path toward entry-level IT support and networking work.</p><p>Project repository: <br><a href="https://github.com/deanhumphreyab/audio-video-mux-gui">https://github.com/deanhumphreyab/audio-video-mux-gui</a></p><p>Portfolio: <br><a href="https://deanhumphrey.ca/">https://deanhumphrey.ca</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f4f5aee095d5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Journey into IT Support and Networking]]></title>
            <link>https://medium.com/@deanhumphreyab/my-journey-into-it-support-and-networking-a7c25c287356?source=rss-4b19b884093a------2</link>
            <guid isPermaLink="false">https://medium.com/p/a7c25c287356</guid>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[it-support]]></category>
            <category><![CDATA[comptia]]></category>
            <dc:creator><![CDATA[Dean Humphrey | IT Support & Networking Student]]></dc:creator>
            <pubDate>Tue, 05 May 2026 06:33:45 GMT</pubDate>
            <atom:updated>2026-05-07T00:16:32.237Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A perspective on IT Support and Networking by Dean Humphrey Alberta Canada</em></p><p>I am currently building a foundation in IT support and networking, focusing on practical skills that are essential for diagnosing and solving real-world technical issues.</p><p>My interest in IT comes from understanding how systems work behind the scenes and how to approach problems in a structured way. Rather than guessing, I’ve been working on breaking issues down step by step, identifying root causes, and applying consistent troubleshooting methods.</p><p>At the moment, my learning is centered around core concepts such as TCP/IP, DNS, and basic network communication. These fundamentals are critical for understanding how devices interact and where problems can occur in a system. Alongside networking, I am also developing skills in hardware and software diagnostics, system setup, and general technical support practices.</p><p>I am currently preparing for CompTIA A+ and Network+ certifications as part of building a solid entry-level skill set. In addition to studying theory, I am focusing on hands-on learning through practice scenarios and lab-based exercises. This helps reinforce not just what to do, but why systems behave the way they do when something goes wrong.</p><p>One of the main areas I am working to improve is troubleshooting efficiency. Being able to approach a problem methodically, rule out possibilities, and arrive at a solution is a key skill in IT support. I am consistently practicing this approach to build confidence and accuracy over time.</p><p>My goal is to move into an entry-level IT support or help desk role where I can apply these skills in a real environment, continue learning, and contribute to solving technical problems effectively.</p><p>I am focused on steady progress, building practical knowledge, and developing a strong technical foundation that can grow over time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DSTiSG9Gf92POBFJrG0TTg.png" /><figcaption>IT Support — Networking — CompTIA Path — Dean Humphrey</figcaption></figure><p>Connect with me on LinkedIn: <a href="https://www.linkedin.com/in/deanhumphreyab/">https://www.linkedin.com/in/deanhumphreyab/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a7c25c287356" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>