Date: Sat, 25 Feb 2006 20:17:22 +0530 From: "Gargi Bodke" <gargibodke@gmail.com> To: "Ken Stevenson" <ken@allenmyland.com> Cc: freebsd-questions@freebsd.org Subject: Re: Ping timeout Message-ID: <d0d845080602250647h272e4948j2837cc70fe209e5a@mail.gmail.com> In-Reply-To: <44004C21.9010300@allenmyland.com> References: <d0d845080602242013u58f19cd2ta7c3ce9a0939cb00@mail.gmail.com> <44004C21.9010300@allenmyland.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I ping the IP. DNS is fine. I use the same ISP as the server. So when it works the server is 2 hops away. Will check out on Freebsd firewalls. On 2/25/06, Ken Stevenson <ken@allenmyland.com> wrote: > > Gargi Bodke wrote: > > Hi > > I am new to this list and new to freebsd also. I have a Freebsd > server > > set up with apache and qmail on it, with an ADSL connection to the > > internet. Most of the time the server works fine but it is not > available > > early mornings and weekends. The machine is physically at my workplace > and > > has a static IP mapped to it by a Service provider. When I say not > available > > I am unable to ping it from home and a tracert also fails. When it > started > > happening I went to my work place to see if the server was down, But it > has > > always been up and running. Also even if the server is not rebooted th= e > > machine becomes accessible after some time. Thinking it to be a network > > problem I have complained to the ISP but they are unable to provide any > > solution. > > > > Is it possible that a freebsd machine sleeps after being idle for some > time? > > Early mornings and weekends is the time when no one is in office that's > why > > am asking. Sorry if this sounds stupid but I ab unable to figure out th= e > > cause so though I should give it a try on this list. > > > > > I bet that your initial diagnosis is correct: your Internet connection > at work is going down periodically. You need to try to get to work > early or on the weekend when the problem is happening, and ideally > have somebody at home or wherever you're doing the tracert from. > > It could also be a DNS problem. When you ping your server, are you > pinging it by name or by IP address? > > Also, do you manage the firewall that your server sits behind? It > sounds like the firewall may be programmed to block traffic during > non-work hours. > > -- > Ken Stevenson > Allen-Myland Inc. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d0d845080602250647h272e4948j2837cc70fe209e5a>