Thanks, everyone, for the advice; it has been beneficial.
As promised, I am blogging about every networking discovery I find. To that end, this post is about how I solved my first networking setback I have come across. I followed a guide written by David Bombal on installing Cisco Virl appliances using Virtualbox as the hypervisor to host GNS3 VM. Meaning I was trying to get GNS3 Server and GNS3 VM to all run on the same machine. It was quite a challenge; the reason it was challenging is THe instructions are for Windows only, and I had to figure out how to adapt the guide for Linux since Kubuntu is the only operating system on my computer, without knowing a lot about how Linux works. I know many readers of this forum would say adapting a guide designed for Windows should be easily adapted to work on Linux; well, the installation instructions were easy; fortunately, the GNS3 community as installation instructions on their web site on how to install the GNS3 program and GNS3 server on all the major Linux operating systems. The problem didn’t lay with installing GNS3 on Linux but with the program not working as it should after everything was installed. I would find a solution that seemed to fix one error, but a different error would take its place. I tried to uninstall GNS3 and reinstall it eight different times completely, but the result would be a different error; finally, at the last try, the original error showed up (the error had to do with the GNS3 server and the GNS3 VM being on different networks.) instead of trying one more time uninstalling GNS3 and then reinstalling it I did a quick Google search and found some article that mentions the GNS3 server and the GNS3 VM need to be on the same network, as soon as I change the network the GNS3 Server was on to the one the GNS3 VM was on all my problems went away, at least so far.