If you have a LAN adapter or permanent Internet link, then use "ping" to determine whether your interface is working. For example, if your IP address is 196.12.34.56, then use ping 196.12.34.56 and check whether the ping packets are being transmitted successfully. If they are not coming through, your TCP/IP configuration is not setup correctly, and you will need to run the TCPCFG.EXE (the icon labelled "TCP/IP Configuration" in your TCP/IP folder) configuration program.

If the ping was successful, then try running "hostid 196.12.34.56" (according to your IP address) and repeat running "install -d". If this still does not find an IP address, you could have a damaged set of TCP/IP or PowerWeb files, in which case you should re-install TCP/IP and unzip and re-install PowerWeb again.

Error 2: The operating system cannot find a host name on your system.

TCP/IP requires a one-to-many mapping between an IP address and its host names. This mapping is set up either within your HOSTS file or by your domain name server (DNS). We recommend that you set up your HOSTS file regardless of whether you are running DNS, as it enables faster lookup of your server's host name while PowerWeb is running.

The HOSTS file is contained within your TCP/IP etc directory. To discover its location, type "set etc" on an OS/2 command line. If this ETC environment variable is not set, your TCP/IP should be re-installed.

Your HOSTS file is a list of IP addresses (one per line) followed by the equivalent host names. For example, our HOSTS file looks like this:

196.31.1.61 www.compusource.co.za compusource.co.za
127.0.0.1 localhost

1. Run TCPCFG.EXE (the icon labelled "TCP/IP Configuration" in your TCP/IP folder)
2. Select the "HostNames" tab within the notebook and goto page 2.
3. Add or modify your existing entries in the listbox.
4. Be sure to check the checkbox "Look through HOSTS file before going to nameserver"
5. Close the configuration notebook and save your changes.

Error 3: Your host name does not resolve to any IP address.

PowerWeb ensures that your IP address maps to your host name and also that your host name maps back to the original IP address. If the mapping back from the host name to the IP address fails, it means that your HOSTS file is not set up correctly.

Refer to the notes regarding Error 2 above for setting up your HOSTS file.

Error 4: Your host name maps to the IP address xx whereas TCP/IP reports your IP address to be yy

This error message occurs when you have multiple IP addresses defined on your machine, and your HOSTS file is inconsistent. In this case PowerWeb mapped your primary IP address to a specific host name, but when that host name was mapped back to an IP address, a different IP address was returned. This is a serious error and will cause malfunctioning of your server.

Refer to the notes regarding Error 2 above for setting up your HOSTS file.

Warning 5: The operating system is unable to resolve an external host name to an IP address.

This warning message indicates that you are either not online to the Internet or that your domain name server (DNS) is malfunctioning. If you are serving only locally or to your private LAN and not to the Internet you can ignore this warning.

If your server is meant to be online to the Internet, then the most likely cause of this message is that your TCP/IP configuration settings do not specify a valid DNS server IP address, or your service provider's DNS is either not operating or is not setup correctly. The easiest way to test this is to use your Web browser to access other sites on the Internet.

To define your DNS server's IP address for a permanent Internet connection:

1. Run TCPCFG.EXE (the icon labelled "TCP/IP Configuration" in your TCP/IP folder)
2. Select the "HostNames" tab within the notebook and goto page 1.
3. Fill in the "Nameserver addresses" listbox.
4. Close the configuration notebook and save your changes.
5. Shutdown and reboot your machine.

Error 6: A xx Server is already running on socket port yy.

This message indicates that you were previously running a server on the same machine as you are installing PowerWeb. If you shut down that TCP/IP service and wait a while (sometimes as long as 5 minutes), IBM's TCP/IP will release the port and enable PowerWeb to use it. In the case of port 80 (for HTTP), PowerWeb will automatically choose port 8000 instead and install itself on that port, allowing you to run your old server (if any) alongside PowerWeb. You can always change your HTTP port later by choosing "Services" from the main PowerWeb admin page while PowerWeb is running.

Warning 7: Your computer does not have its timezone defined.

PowerWeb needs to know your timezone for your machine's location so that it can send the correct timestamp information to remote clients. Many Web browsers rely on the server's clock and timezone being correctly set so that they can cache images or documents locally, fetching new copies only when the cache is out-of-date.

To define your timezone:

1. Run TCPCFG.EXE (the icon labelled "TCP/IP Configuration" in your TCP/IP folder)
2. Select the "General" tab within the notebook.
3. Fill in the "Timezone" edit field.
4. If you are unsure what setting to use, read the Help - it can be complex, but then the specifications of timezones around the world are complex anyway.
5. Close the configuration notebook and save your changes.
6. Shutdown and reboot your machine.