Dns Socket Error 11004
Contents |
ease planning, as well. Free PRTG Download >> What is this? This knowledgebase contains questions and answers about PRTG Network Monitor dns could not be resolved socket error 11004 and network monitoring in general. You are invited to get involved by
Socket Error 11004 Windows Live Mail
asking and answering questions! Learn more Top Tags 5730× prtg 1832× snmp 1462× sensor 932× wmi 621× socket error 11004 ftp notifications 463× maps View all Tags "DNS could not be resolved (socket error # 11004)" although nslookup and "ipconfig /displaydns" prod Votes:0 Your Vote: Up Down We have an
Socket Error 11004 Error Number 0x800ccc0d
HTTP sensor that went into error state with the message "DNS could not be resolved (socket error # 11004)". However on the probe (core server) nslookup returns the correct address. Also when we run "ipconfig /displaydns" to see the resolver cache the correct address is listed for the website. Even more, if we fire up firefox we are able to outlook express socket error 11004 successfully bring up the sensor's page. Short of restarting the probe or core services, what can we do to fix this problem? dns falsealarms http-sensor Created on Jul 28, 2011 8:44:28 PM by Jim Kirby (181) ●2 ●1 Permalink Best Answer Accepted Answer Votes:0 Your Vote: Up Down Pause/resume does not change anything. I forgot to mention, this sensor is part of a PRTG cluster and both probes in the cluster exhibit the same behavior (the machine resolves but PRTG does not). Also, this problem started when we changed the glue records (authoritative DNS as listed in Whois) for that domain. A clone of the sensor had the same problems but a new sensor that we created from scratch worked fine. We figured out that there was an invisible character trailing the URL on the settings page. Apparently the servers at the previous DNS provider were ignoring this trailing character but our new DNS was throwing a NXDOMAIN response which is the response we want for lookups with invalid characters. (a cheap hedge against DNS poisoning)
account only takes a few minutes. Join Now Read More Reply Subscribe RELATED TOPICS: No such address or other
Socket Error 11004 Grabit
socket error. No such address or other socket error. Socket Error  
Socket Error 11004 Hatası
This discussion has been inactive for over a year. You may get a better answer to your question socket error 11004 jane by starting a new discussion. Text Quote Post |Replace Attachment Add link Text to display: Where should this link go? Add Cancel × Insert code Language Apache AppleScript Awk BASH Batchfile https://kb.paessler.com/en/topic/23303-dns-could-not-be-resolved-socket-error-11004-although-nslookup-and-ipconfig-displaydns-prod C C++ C# CSS ERB HTML Java JavaScript Lua ObjectiveC PHP Perl Text Powershell Python R Ruby Sass Scala SQL VB.net Vimscript XML YAML Insert Cancel Follow this vendor page Reply × Users who spiced this post Read these next... Feedback Friday on Saturday: Is it October already?! Spiceworks Originals We have some things for you to check out and tell us https://community.spiceworks.com/topic/301208-dns-could-not-be-resolved-socket-error-11004 about. 30+ free ransomware removal tools Security Fact: No IT pro likes ransomware. Another fact: Most people like free stuff. Here's more than 30 tools to help remove ransomware. Boom. Snap! US says Russia is meddling in elections, Verizon seeks discount on Yahoo Spiceworks Originals A daily dose of today's top tech news, in brief. © Copyright 2006-2016 Spiceworks Inc. About Advertising Privacy Terms Help Sitemap × Join millions of IT pros like you Log in to Spiceworks Reset community password Agree to Terms of Service Connect with Or Sign up with your email address First Name Last Name Email Join Now or Log In Email Password Log In Forgot your password? Email Reset Password Cancel Need to recover your Spiceworks IT Desktop password? By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks. By creating an account, you're agreeing to our Terms of Use and our Privacy Policy Not a member? Join the community Back I agree Powerful tools you need, all for free. Help Desk » Inventory » Monitor » Community »
Policies Pricing License Guidance Get Help Contact Support Forum Learn Network Nirvana Articles Knowledge Base Account Home » Categories » PingPlotter » Alerts Socket error 11001 or 11004 https://www.pingman.com/kb/article/socket-error-11001-or-11004-when-testing-an-alert-45.html when testing an alert Question I am trying to setup auto email alert but get a 'Socket error 11001' when testing it. What's wrong? Solution The most common cause of this error in either PingPlotter or MultiPing is an invalid SMTP server specified. The error means that the name entered couldn't be resolved to an IP address. In MultiPing, socket error this is in the 'Edit' -> 'Options', Email tab. In PingPlotter, this is on the Edit->E-mail... setup menu. Make sure you're using the right SMTP Server name or IP address there. If you're not sure what to use, check the settings in your email client, or check with your ISP. It's also possible that the network may have been down socket error 11004 right when you did this test. If this was the case during a network 'event', then the email would have been retried until it went through. Because this error is related to resolving a name to an IP address, one way to eliminate it is to enter an IP address as the SMTP server. Note: This could show up as 11001 or 11004. 11001 means that the host is not found at all. 11004 means that the DNS naming system has some knowledge of this name, but not anything useful for us. Print Article Export to PDF Article Rating (64 Votes) Rate this article Select One 5 - Excellent 4 - Above Average 3 - Average 2 - Below Average 1 - Unhelpful Article Number: 45 | Last Updated: October 10, 2015This article has been viewed 23472 times since June 10, 2005 Filed Under: Alerts Attachments There are no attachments for this article. Related Articles Socket error 10053 when testing email alerts Viewed 35796 times since January 14, 2005 Using SSL for sending alert emails. Viewed 16135