<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.16.1">
</HEAD>
<BODY>
To touch on something Chad said:<BR>
<snip><BR>
<TT>If the problem is only affecting the browser, then it sounds like you </TT><BR>
<TT>need to focus on things that would cause the browser to not work. The </TT><BR>
<TT>problem affects multiple machines, so the problem is more likely to be </TT><BR>
<TT>centralized. If you have a proxy or caching server that proxies and/or </TT><BR>
<TT>caches HTTP traffic, that would be a good place to check. It would only </TT><BR>
<TT>affect HTTP traffic. You could also verify that DNS is resolving </TT><BR>
<TT>correctly when the problem occurs. If the URL can't be resolved to an IP </TT><BR>
<TT>address, it could act as you described.</TT><BR>
</snip><BR>
<BR>
An easy way to check this is:<BR>
On an effected machine. <BR>
Open a command prompt and type:<BR>
<BR>
ping google.com<BR>
<BR>
This should (if DNS is working correctly) return a response.<BR>
<BR>
If not type:<BR>
<BR>
ping 72.14.207.99<BR>
<BR>
This should return a response as well. This just verifies that your network is connected to the net.<BR>
If the first times out, you definitely have a DNS problem. If both time out then you have a network problem.<BR>
<BR>
<BR>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<PRE>
--
Dan Will
Technology Supervisor
Meigs County District Public Library
Pomeroy, Ohio 45769
740.992.5813
740.992.6140 (fax)
<A HREF="mailto:willda@oplin.org">willda@oplin.org</A>
The difference between fiction and reality?
Fiction has to make sense.
Tom Clancy
</PRE>
</TD>
</TR>
</TABLE>
</BODY>
</HTML>