windows 7 - Chrome - resolving host problems- Homegroup and McAfee Trust new network

One of our systems after an outage consistently gives "resolving host" delay when logging in using updated Google Chrome on Windows 7 PC.  Had issues upgrading from WEP to WPA initially, and had AT&T outage, but since that was resolved.  However, this "resolving host" when attempting to get into Chrome is baffling.  

Also, using the McAfee Total Protection product to view home network, shows one computer to be "trusted" and that never completes.  Shows "trusting new network" and when chosen, just cycles and never completes.

Thought it was a problem with Homegroup, so tried to delete homegroup and Windows responds could not remove computer from homegroup.

Where to start.

Thanks,
Asta
LVL 27
Asta CuTechnical consultant & graphic designAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

acsevenCommented:
Hi,

"Resolving host" is usually associated with DNS issues.

If you can, try disabling McAfee's protections temporarily to see if the issue goes away. If it does, then the issue is most likely related to one of its components. You then might uninstall and reinstall them, and contact McAfee support to assist you on the issue.

Considering that disabling McAfee's protections does not result in any benefit, you can also try one of the following:

1. Clearing Windows's DNS cache:
Open a Command Line window (Start > type cmd and press enter
Type: ipconfig /release
Type: ipconfig /flushdns
Type: ipconfig /renew


2. Clearing Chrome's DNS cache:
In Chrome, go to: chrome://net-internals/#dns
Click "Clear host cache" button in "Host resolver cache" section

3. Try using Google's DNS servers, check the instructions at Google's link below, Microsoft Windows section:
https://developers.google.com/speed/public-dns/docs/using?hl=pt-pt
If you find that these DNS servers work better then you should evaluate what is wrong with your network's DNS.


Cheers
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Asta CuTechnical consultant & graphic designAuthor Commented:
Thank you very much.  Spent roughly 4.5 hours yesterday with McAfee who tried many things, after I had already reinstalled McAfee and between the two computers involved, problems persisted.  After escalating to Tier 2 at McAfee and again many problems with it and inability due to access denied on the MHN elements, gave up for the day and will be getting a call back from them within the next 3 hours.

I will try the recommendations you've posted as well.

Cheers, until more is known ...

":0)  Asta
0
Asta CuTechnical consultant & graphic designAuthor Commented:
OOPS, need to clarify.  When you said ...
 1. Clearing Windows's DNS cache:

•Open a Command Line window (Start > type cmd and press enter


•Type: ipconfig /release


•Type: ipconfig /flushdns


•Type: ipconfig /renew

is this to be done on both desktop computers which are having problems communicating?
0
Firewall Management 201 with Professor Wool

In this whiteboard video, Professor Wool highlights the challenges, benefits and trade-offs of utilizing zero-touch automation for security policy change management. Watch and Learn!

acsevenCommented:
Hi,
Wherever you're experiencing the "resolving host" issue.
Cheers
0
Asta CuTechnical consultant & graphic designAuthor Commented:
On one of the systems, flushing dns worked so that McAfee can trust the other computer.   I had to also remove/disable all wireless on the Dell 660 before the dns issues could resolve.  In the interim, also had an unhandled UI error on the other system, error 403126943.  More soon.  Thank you so much.
0
Asta CuTechnical consultant & graphic designAuthor Commented:
Both systems resolved with your DNS recommendations.  Brilliant!!!!!

McAfee's tech yesterday thought that having "renamed" a computer could cause this problem.  Since I now want to rename within Windows 7, one of the PCs to make more sense to us in controlling the hard-wired and wireless devices, can you let me know if renaming computers should be any issue?  When I look at one of the desktop computers within Windows, it is called Michelle.  But when within the command prompt, it was identified as Michelle-PC.  I'd like to make them equal but not at the cost of jeopardizing our progress.

thank you so much again.
0
Asta CuTechnical consultant & graphic designAuthor Commented:
Will close and award points with gratitude.  Sure do hope to hear from you about the renaming of computer impact.  If that should be another Q, please advise.

Have a terrific rest of this week.

":0)  Asta
0
acsevenCommented:
Hi, glad you worked it out.

Renaming the computers might result in similar behavior, and for which it should be resolved after flushing DNS on the machine(s).

Cheers!
0
Asta CuTechnical consultant & graphic designAuthor Commented:
Cheers and hats off to you!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Network Security

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.