Solved DNS Server not responding

[jelold]

Good afternoon,
I have not been able to connect to the internet for several days in normal mode, although it works fine in safe mode. I had a technician here yesterday from the cable company and he was trying to help out some. I've also been reading various forums to try to find a solution but no luck yet. I have run a virus scan as well as Spybot and Malware Bytes to see if that was the problem. Some of the other solutions I've read about are confusing because I don't know what a lot of it means, and I don't want to change something without receiving some sort of direction. I consider myself somewhat tech savvy but obviously not when it comes to this! So, can anyone help? I've attached the ipconfig file. I am using a cable modem with a splitter. Let me know if you need any other info.
Jenny

Here is the actual error message I receive -- "Windows can't communicate with the device or resource (primary DNS server)"

 

[jelold]

Here is the hijack this log, just in case it is helpful.

 

[mrhiab]

Change DNS to Google public
8.8.8.8 primary
8.8.4.4 secondary

Do you have McAfee A/V by chance?

Your Default Gateway 173.217.20.1 & DHCP Server 172.24.120.114 are on 2 different networks.
On mine they're the same address.

 

[chev65]

Here is the hijack this log, just in case it is helpful.

You have a few potential problems showing up in highjack this starting with McAfee.

Maybe you need to read about the McAfee update problem which has been causing connection problems.

McAfee - Resolving the recent update issues with McAfee Consumer Products


O23 - Service: Bonjour Service - Apple Inc. - C:\Program Files\Bonjour\mDNSResponder.exe

This Bonjour service causes connection problems on Windows systems, you should go into Windows services and disable Bonjour. You can get there by typing services.msc into the run box.

 

[jelold]

Thanks for the help! I actually kept researching since I didn't hear from anyone for a while and found the problem with the last update from McAfee. I ran the fix and I'm online!