If you can access the IIS sites then the problem seems to be with your apache configuration, either way it isn't really a MediaWiki problem (unless you can access other sites on the apache setup). I suggest you post your question to the apache mailing list, unless there is someone here who has encountered this problem before.

Arthur Guy

arthur@astarsolutions.co.uk a star solutions www.astarsolutions.co.uk

Audio & Video Leads Adapters and Accessories -----Original Message----- From: mediawiki-l-bounces@Wikimedia.org [mailto:mediawiki-l-bounces@Wikimedia.org] On Behalf Of Ferry Sent: 29 September 2005 09:29 To: mediawiki-l@wikimedia.org Subject: [Mediawiki-l] Can't access Mediawiki on Windows 2000 Server fromclients

Hi there! - I'm new - :)

I'm been attempting to install Mediawiki on Windows 2000 Server to use over a LAN.

Installation method: EasyPHP.

If I use the server directly, the wiki works (using http:\localhost\wmwiki). But I can't access the wiki from any of the client computers (using http:\wmserver\wmwiki). "wmserver" is the DNS name for my server.

I do have IIS installed, but I have moved it to port 8080, while Apache runs on port 80. (I can access the IIS websites from the client computers with no problems.)

So how do I get the client computers to see my wiki?

Thanks for any advice!

Ferry

_______________________________________________ MediaWiki-l mailing list MediaWiki-l@Wikimedia.org http://mail.wikipedia.org/mailman/listinfo/mediawiki-l

'a star solutions' disclaimer The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you are not the intended recipient of this message you are hereby notified that any use, review, retransmission, dissemination, distribution, reproduction or any action taken in reliance upon this message is prohibited. If you received this in error, please contact the sender and delete the material from any computer. Any views expressed in this message are those of the individual sender and may not necessarily reflect the views of the company. We believe that this communication is free from viruses and other potentially dangerous programmes, but the recipient opens this communication at their own risk. We assume no responsibility for any loss or damage arising from the receipt or use of this communication