asked on

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

ASKER CERTIFIED SOLUTION

acseven

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Asta Cu

ASKER

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

Asta Cu

ASKER

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?

acseven

Hi,
Wherever you're experiencing the "resolving host" issue.
Cheers

Asta Cu

ASKER

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.

Asta Cu

ASKER

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.

Asta Cu

ASKER

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

acseven

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!

Asta Cu

ASKER

Cheers and hats off to you!