CompTIA A+, Troubleshooting Network Connections; unable to solve connection issues

---

Hi,
I tried to apply the info from the videos on "Troubleshooting Network Connections" to my own connectivity issues, but I could not solve the problem, and I could not even find out what was wrong.
A short description: I have two computers, one is fine, and the other one refuses to work on the Internet. Both computers go via the same gateway.
Following the instructions in Wes' video, I tried the following with the "bad" computer:

1. Ping to 127.0.0.1 - it worked.
2. Ping to the "bad" computer's own IP - it worked.
3. Ping to another computer on the same network - it worked.
4. Ping to the gateway device - it worked.
5. Ping to a computer on another network. This worked when I pinged to the IP address of a computer. It did not work when I tried to ping to the "name" of the website, e.g. to "www.google.com".
   So, it looks like there only is a problem with accessing a DNS server.
   However, the problem unfortunately is bigger than that.
   If I use the browser, and I put in the IP address (instead of the name, e.g. "www.google.com") into the browser, then I am still unable to access the website.
   So, I cannot access websites, but I am able to ping to them.
   In the notification area at the bottom right corner of the screen, it says that the computer does not have Internet access.
   I have checked the network interface card (NIC), and I received the info that this device would work properly.
   What did I do wrong, or what did I miss, when trying to resolve the connectivity issue?

Thank you very much.

@Wilfried-Roessler sounds like you have done the right T-shooting steps, can you give me a screenshoot of an IPConfig /all output or maybe a screenshot of the NIC configuration.

Also can you statically map the DNS server settings to

DNS Server: 8.8.8.8 and 8.8.4.4

Then retry the ping test.

Another thing you can use nslookup to test DNS by bypassing the locally configured DNS server and bouncing the resolution request off of another DNS server and see if it gets replies.

nslookup www.google.com 8.8.8.8
nslookup www.google.com 8.8.4.4

Give these a try and let me know what you find!

Thank you, @wes-bryan .

First of all, this is the screenshot of "ipconfig /all":

Then I would like to add some info about the NIC:

I tried to change the DNS server the NIC points to, per your instructions, but I did not manage to do so. Why? I did not find the NIC in the list!

I know that this is strange.

Let us first look into Device Manager. Here you can see the wireless NIC:

However, in Network and Sharing Center, I could not find it.

Therefore, I was not able to right-click it, and to go to Properties, and then to change the DNS server that the NIC points to.

Still, on the positive side, and quite surprisingly, the Ping-Test to Google.com was successful. When I did a NSLookup, I even found a valid IP address of Google.com, namely 216.58.211.4 .

So, it seems to work at least... a little bit...

But, as described in my first post, it does certainly not work as it should.

Maybe you have an idea about what could be wrong?

Thank you very much.

It seems you have a lot of virtual adapters on this machine

VirtualBox
VMWare
Hyper-V

Is this correct?

@wes-bryan Well, yes, but virtual adapters are already a bit above my level of understanding. I tried to work a bit with virtualization, but really not very successfully. Maybe we could call it a failed experiment.

Hey @Wilfried-Roessler, the virtual adapter is a software-based representation of a physical network adapter. When you create virtual machine, it is really just a folder with a set of files. Virtual machines still use resources such as CPU, drives, RAM as well as network adapters. The hypervisor is what allocates these components as "virtual" resources. This is what is meant by "virtual network adapters." When you create VPN connection, the VPN client will also create a "virtual network adapter" as well and judging by the screenshot it seems that you have several of these "adapters" created, so the communication breakdown is most likely a direct result of all these adapters being in contention. I hope this helps with the virtual adapter concepts.