ThePocketWeasel said:
I restarted just under an hour ago and it's working fine so far.
Thank you so much for your help.
One last question, if it happens again I assume I can just do that again and it'll sort it out?
You're very welcome, hopefully that took care of it. You can use those commands again if necessary, but if you're having to repeatedly do it, it suggests that there's a program or somesuch screwing up your connection settings.
cleverlymadeup said:
i'm going to say this is bs, simply because if msn works, then so does the web because msn uses http to get it's stuff done
tho i could say is it specific sites or all of them?
The web is still working in her case, but not the DNS resolution, at least that was my (seemingly correct? Better not jinx it.) assumption. It's one of the more common things that breaks with Windows, at least in my experience, so I started there. MSN, AIM, and other internet client programs would still work since they either connect directly by IP, or because they resolved the domain name and connected before the point that the DNS resolver died, and kept the connection alive. HTTP was not the problem. I don't think I've ever seen a case where a computer would not properly execute/interpret HTTP.
