Koozali.org: home of the SME Server

Legacy Forums => Experienced User Forum => Topic started by: Jason Ephraims on September 29, 2003, 04:13:28 PM

Title: Unable to Browse
Post by: Jason Ephraims on September 29, 2003, 04:13:28 PM
i am having some trouble at a client site. They are unable to browse www through any of there workstations. The machine was running fine for about 6 months and just the other day they said that they could not browse.
After looking at the site i have found the following
1. They can ping a www address through a dos prompt and get a response
2. They can receive email
3. They can log into ftp site through the browser
4. The SME internet test works
5. Connecting a pc directly to the router you can browse web sites
6. I can not see any evidence in the logs as to what is going on (nothing noticable)

If you try to browse through internet explorer no go both with and without the proxy settings in the browser.

Any ideas would be great
Thanks Jason
Title: Re: Unable to Browse
Post by: Graeme Fleming on September 29, 2003, 04:23:51 PM
Check the logs to see if Squid has a probelm - SME uses a transparent proxy so if the SME box is your gateway then web requests will be handled by Squid.

HTH
Title: Re: Unable to Browse
Post by: Michiel on September 29, 2003, 04:33:23 PM
I saw something similar on a machine that ran out of diskspace. Just a thought.
Title: Re: Unable to Browse
Post by: RayG on September 29, 2003, 07:49:32 PM
You may not see anything in the logs if Squid died quietly. Pull up a console and do:


service squid restart



I suspect it will respond with a message saying it failed to stop squid and another saying it started ok.
Title: Re: Unable to Browse
Post by: Jason Ephraims on September 29, 2003, 08:49:56 PM
I will give that a try tomorrow thanks i will post back the results
Title: Re: Unable to Browse
Post by: Ed Form on September 30, 2003, 03:47:07 AM
Jason Ephraims wrote:
>
> i am having some trouble at a client site. They are unable to
> browse www through any of there workstations. The machine was
> running fine for about 6 months and just the other day they
> said that they could not browse...

It's probably too much of a coincidence to be the cause, but a colleague of mine came across a couple of Windows installations that had mysteriously lost the ability to browse. Neither he nor I could explain the situation and full reinstalls solved the problem so no further info I'm afraid, but we're suspicious of a virus based situation.

Ed Form
Title: Re: Unable to Browse
Post by: Manuel Lazo on September 30, 2003, 10:45:16 PM
Well, that happens to me last year with a E-smith Server 5.0, but the problem was that I forgot to apply the SSL patch, so my E-smith was affected with the SSL exploit, so my Server was used to do a DOS attack (it was using all the bandwith), so that was the reason no one could browse!

I don't think that this could be an issue with SME servers (5.5, 5.6, 6.0b3), but if you don't have applied all the updates, you are at risk!!
Title: Re: Unable to Browse
Post by: Jason Ephraims on October 01, 2003, 01:33:07 PM
Hi i restarted squid and it worked. For some reason it did not start on startup and even if you kept rebooting it would not start. THe computer does not have a monitor so i could not see if it started up on startup. After i did the restart on squid it has been fine. I even did a restart and it started ok. Thanks
Title: Re: Unable to Browse
Post by: Klaus Eckert on October 01, 2003, 09:04:49 PM
you do not need a local monitor to see what happened on startup.
there are several files in "/var/log" which log the startup-procedere.
this are "boot.log" and "dmesg".
have a look at these files and you'll see what happened or not happened.

cheers klaus
Title: Re: Unable to Browse
Post by: Tobias Zimmergren on October 12, 2003, 04:10:39 AM
Hi.

Thanks for that tip.. But how and where do I get updates and security patches?

Thanks