[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3013
  • Last Modified:

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
0
Asta Cu
Asked:
Asta Cu
  • 6
  • 3
1 Solution
 
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
 
Asta CuAuthor 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 CuAuthor 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
NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

 
acsevenCommented:
Hi,
Wherever you're experiencing the "resolving host" issue.
Cheers
0
 
Asta CuAuthor 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 CuAuthor 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 CuAuthor 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 CuAuthor Commented:
Cheers and hats off to you!
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 6
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now