User manual
Table Of Contents
- Web Technologies Administration
- Contents
- Web Technologies Overview
- Managing Web Technologies
- Managing Websites
- Using Server Admin to Manage Websites
- Changing the Access Port for a Website
- Improving Performance of Static Websites (PerformanceCache)
- Enabling Access and Error Logs for a Website
- Setting Up Directory Listing for a Website
- Connecting to Your Website
- Enabling WebDAV on Websites
- Enabling a Common Gateway Interface (CGI) Script
- Enabling Server Side Includes (SSI)
- Viewing Website Settings
- Setting Server Responses to MIME Types and ContentHandlers
- Enabling SSL
- Enabling PHP
- User Content on Websites
- WebMail
- Secure Sockets Layer (SSL)
- Working With Open-Source Applications
- Installing and Viewing WebModules
- Solving Problems
- Where to Find More Information
- Glossary
- Index
8
65
8 Solving Problems
If you experience a problem with web service or one of
its components, check the tips and strategies in this
chapter.
From time to time you may encounter a problem when setting up or managing web
services. Some of the situations that may cause a problem for administering web
service or for client connections are outlined here.
Users Can’t Connect to a Website on Your Server
Try these strategies to uncover the problem:
• Make sure that web service is turned on and the site is enabled.
• Check the Web Service Overview window to verify that the server is running.
• Check the Apache access and error logs. (If you are not sure what the messages
mean, you’ll find explanations on the Apache website at www.apache.org.)
• Make sure users are entering the correct URL to connect to the web server.
• Make sure that the correct folder is selected as the default web folder. Make sure that
the correct HTML file is selected as the default document page.
• If your website is restricted to specific users, make sure those users have access
privileges to your website.
• Verify that users’ computers are configured correctly for TCP/IP. If the TCP/IP settings
appear correct, use a “pinging” utility that allows you to check network connections.
• Verify that the problem is not a DNS problem. Try to connect with the IP address of
the server instead of its DNS name.
• Make sure your DNS server’s entry for the website’s IP address and domain name
are correct.
LL2350.book Page 65 Friday, August 22, 2003 2:32 PM