When I run Internet Connections troubleshooting, I receive the same message as this thread is about.
That's probably not the right troubleshooter to expose your problem cause. Evidently all it knows how to do is check to see if TCP is running and then if it is try to use DNS and then if that fails tell you that DNS is not responding.
The poster credited with the answer for this thread discovered that his addressing was wrong. Cloning excessively could have the same effect.
The real answer for the symptoms stated by the OP is given by the one which currently rated "Most helpful". So, I would still suggest starting your own thread with your own details and use that answer as a guide for the required diagnostics.