hundreds of these over last week
Name resolution for the name data.hackerwatch.org timed out after none of the configured DNS servers responded
Hundreds more of these over the last week
Name resolution for the name devicediscovery.ccs.mcafee.com timed out after none of the configured DNS servers responded.
What is causing this? It is a cause for alarm? Could these site have gotten on a blacklist to where my home system cannot connect?
[EDIT]
Not sure if it is significant, but I cannot ping either of the two sites
C:\Users\josep>ping data.hackerwatch.org
Pinging data.hackerwatch.ORG [161.69.38.96] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 161.69.38.96:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\josep>ping devicediscovery.ccs.mcafee.com
Pinging devicediscovery.ccs.mcafee.com [161.69.45.182] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 161.69.45.182:
Packets: Sent = 4, Received = 0, Lost = 4 (100%
If I ping google or microsoft I invariably get one timeout followed by 3 successful replies
Thank you for contacting us for help. Please let us know the below information which helps us to investigate further.
Please try the below steps and update us the status
Regards
Siva
Unaccountably, my reply got deleted. Best I can remember posting:
The pre-test found and fixed a few things. There was no report so I dont know what was fixed. In any event the pings still fail both from a linux system and my my Dell Area51-R3 with McAfee LiveSafe subscription
I can ping devicediscovery.ccs but not devicediscovery.ccs.mcafee.com
C:\Users\josep>ping devicediscovery.ccs.mcafee.com
Pinging devicediscovery.ccs.mcafee.com [161.69.17.39] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 161.69.17.39:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\josep>ping devicediscovery.ccs
Pinging devicediscovery.ccs [23.202.231.169] with 32 bytes of data:
Reply from 23.202.231.169: bytes=32 time=108ms TTL=52
Reply from 23.202.231.169: bytes=32 time=98ms TTL=52
Reply from 23.202.231.169: bytes=32 time=104ms TTL=52
Reply from 23.202.231.169: bytes=32 time=60ms TTL=52
Ping statistics for 23.202.231.169:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 60ms, Maximum = 108ms, Average = 92ms
Why is that.
ipconfig/flushdns had not effect nor rebooting.
Oldest entry in event viewer system log is 8/28/2020 11:53 pm
First mcafee DNS error was 8/29/2020 1:14 pm and there were 1067 of them through today
[edit]
BIG PROBLEM:
Your pre-instlall tool put in VS C++ 2010 runtime and I now have over 100 error messages "A fatal error occurred while creating a TLS client credential. The internal error state is 10013."
These were not there earlier
i am replying to my previous post as, I am guessing, if I edit a post too many times it is tagged as spam and deleted. I thought only the Dell Community did that.
Anyway, what your Pre-Install put in was not the redistributable, it was the security update for the 2010 redistributable.
I unstalled McAfee and the DNS and SChannel TCL errors went away. I will try reinstalling after I get with microsoft support about why TLC1.2 is not working with your DNS servers. I think their dotnet update caused the problem.
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.
Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership: