Server loses internet connection
in [Windows Servers]
|
From: Jonathan de Boyne Pollard on 26 Jan 2010 17:11 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> <blockquote cite="mid:udBM$ypnKHA.5552(a)TK2MSFTNGP05.phx.gbl" type="cite"> <p wrap="">By 'internet connectivity' I mean I'm just getting page cannot be displayed on any website, not just the one we use to manage the backups. <br> </p> </blockquote> <p>Come now! Conflating "Internet" and "World Wide Web" is a well-known error to avoid.</p> <p>You have a WWW browser problem. There are many potential causes. For all we know, you could have misconfigured HTTP proxy settings or an erroneously shaped hole knocked in a firewall or a (mal)functioning malware filter. (JohnB is leaping to conclusions with no factual justification.) You need to do proper diagnosis. That starts with looking at the error messages. Look at the error messages. If you want help from other people, tell those other people the error messages, too. Then you run tests, systematically, to eliminate possibilities.<br> </p> </body> </html>
From: Jonathan de Boyne Pollard on 26 Jan 2010 17:15
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> <blockquote cite="mid:%23QlbdRqnKHA.3636(a)TK2MSFTNGP06.phx.gbl" type="cite"> <p>Sounds like it may be a DNS configuration problem.</p> </blockquote> <p>You're leaping to conclusions with no factual basis. M. Zebby hasn't actually <a href="http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/dns-narrow-problem-locus.html">proven that that xyr WWW browser problem is a DNS problem</a>. I can think of three potential non-DNS causes for such a problem off the top of my head, and those are just for starters. We have no information for narrowing the problem down.<br> </p> <blockquote cite="mid:%23QlbdRqnKHA.3636(a)TK2MSFTNGP06.phx.gbl" type="cite"> <p>Your DNS server(s) should be configured with <em>Forwarders</em> that point to your ISP DNS servers. </p> </blockquote> <p>Balderdash. This is received wisdom that is wrong. There's nothing universally wrong with doing query resolution onesself, and there are good reasons for doing so. <a href="http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/dns-server-roles.html#ChoosingProxy">The decision about forwarding is a complex one</a>, with factors for and against that have to be weighed. Simplistic "You should always do X." recipes are just plain wrong. Moreover, please think about what a DNS problem would cause before leaping to conclusions. M. Zebby hasn't proven that this is a DNS problem in the first place, and in fact the datum that other machines have no WWW browser problems indicates that this most certainly isn't a problem that is in any way affected by whether or not xyr proxy DNS server is doing forwarding.</p> <p>"Doctor, I have a pain in my elbow."<br> "Ah, you must have cancer of the liver. Here's what to do when one has cancer of the liver ..."</p> </body> </html> |