Thank you for replying. That was the problem. When KOHA set itself up it used the server name instead of the ip address for the Virtual host name. I had to add in two NameVirtual Host Lines NameVirtualHost=ipaddress:80 NameVirtualHost=ipaddress:8080 and change the <VirtualHost name:port> to <VirtualHost ipaddress:port> After that worked I made the koha.http.conf a bit more generic by using wildcards instead of ip addresses. I thought you may find it interesting. It allows you to set up your virtual host files independent of ip address so it is possible to use a dhcp assigned address or in my case have the server on a test network and then move it to a production network. I included my koha.http.conf which is made part of my apache2.conf with an include. NameVirtualHost *:80 NameVirtualHost *:8080 # KOHA's OPAC Configuration <VirtualHost *:80> ServerAdmin craigrandersen@hotmail.com DocumentRoot /usr/local/koha/opac/htdocs ServerName dino ScriptAlias /cgi-bin/koha/ /usr/local/koha/opac/cgi-bin/ Redirect permanent index.html http://dino:80/cgi-bin/koha/opac-main.pl ErrorLog /usr/local/koha/log/opac-error_log TransferLog /usr/local/koha/log/opac-access_log SetEnv PERL5LIB "/usr/local/koha/intranet/modules" SetEnv KOHA_CONF "/etc/koha.conf" </VirtualHost> # KOHA's INTRANET Configuration <VirtualHost *:8080> ServerAdmin craigrandersen@hotmail.com DocumentRoot /usr/local/koha/intranet/htdocs ServerName dino ScriptAlias /cgi-bin/koha/ "/usr/local/koha/intranet/cgi-bin/" Redirect permanent index.html http://dino:8080/cgi-bin/koha/mainpage.pl ErrorLog /usr/local/koha/log/koha-error_log TransferLog /usr/local/koha/log/koha-access_log SetEnv PERL5LIB "/usr/local/koha/intranet/modules" SetEnv KOHA_CONF "/etc/koha.conf" </VirtualHost> Your documentation is very impressive. Thanks Again Craig

Message: 2 Date: Mon, 27 Feb 2006 08:16:10 +0000 From: Martin Woolley <sysadmin@handsworth.bham.sch.uk> Subject: Re: [Koha] I can connect to Koha locally, but not from another machine To: koha@lists.katipo.co.nz Message-ID: <200602270816.10511.sysadmin@handsworth.bham.sch.uk> Content-Type: text/plain; charset="utf-8"

On Saturday 25 Feb 2006 05:00, Craig Andersen wrote:

...

I can connect and use Koha locally, either by using http://machinename or by http://127.0.0.1 and it works fine.

If I try to connect to it using http:/IPaddress or http://machine name from another machine I get following error:

NOT FOUND the requested URL/ was not found on this server.

I checked the Apache error log which showed:

[error] [client ipaddress] file does not exist /htdocs

If I type the ip address into the browser on the server, rather than http://127.0.0.1 I get the Not Found error.

I'm at a loss. When I first installed Koha I'm pretty sure that I was able to connect to it from another machine, but now when I'm ready to start testing some things out, it seems to get lost after connecting to the apache server.

I'm using Firebox to connect. Same thing happens with IE. The server is running Debian Sarge and Apache2.

You have an error in your apache config, but from your description I can't tell what it is. This url http://www.openhgs.org.uk/it.cgi/koha shows how I fixed a similar problem on our koha box (scroll down to 24/11/2005)

-- Regards Martin Woolley ICT Support Handsworth Grammar School Isis Astarte Diana Hecate Demeter Kali Inanna

************************************************************* This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify postmaster@bgfl.org

The views expressed within this email are those of the individual, and not necessarily those of the organisation *************************************************************

End of Koha Digest, Vol 4, Issue 27 ***********************************