Appendix 2: Using OmniHTTPd as an Intranet Server

Using OmniHTTPd as an Intranet Server

OmniHTTPd runs very well as an Intranet Server. If you have at least two computers networked together through network cards, you have an Intranet. Wow! What hype! You are close to becoming an Intranet Master!

The following steps outlines how to get OmniHTTPd running efficiently on your Intranet:

Step 1: Setup your local network with TCP/IP

Crucial step here. You should make sure you have a functional network first. The only protocol OmniHTTPd requires is TCP/IP. We have had no problems running TCP/IP along side with IPX on my machine but there have been some reports of protocol stacks not working well under high loads when too many protocols were installed. This is especially true with NetBEUI.

Step 2: Setup your IP addresses

If the computer on the network have not been assigned IP addresses, then you must do this before running the server. The TCP/IP protocol will not work without IP addresses. You can assign any address you want to any machine since you are not on the internet. Try 218.1.1.x where x is any number between 1 and 254 and a subnet mask of 255.255.255.0.

Step 3: Setup OmniHTTPd

Setup the site address under the server tab to the IP address of the machine running OmniHTTPd. Turn off Dynamic Lookup and DNS Reverse.

Step 4: Test the Server

First test the server locally using http://127.0.0.1 and if that works, go to another machine on the network and access it through its assigned IP address.

Back to the Technical Appendices page

Casa de Bender