HomeDoor 2.0 User's Guide

Troubleshooting

 

This chapter covers some common questions about problems with HomeDoor.

 

Troubleshooting: Browser-Independent Redirection

As a general troubleshooting hint, many problems with browser-independent redirection are due to incorrect configuration of domain names. To rule out DNS problems, try accessing your virtual servers using hard-coded addresses (URLs of the form http://10.0.0.1). If hard-coded addresses work correctly, the problem is with domain name configuration. Consult with your network administrator.


When accessed through a browser, the home page for the entire Web server is being displayed, not the home page for the particular virtual server desired.


The "location" of the home pages managed by HomeDoor, as displayed in the browser, begins with the "real" server's domain name, not the home page's.


I implemented the above workaround, but the "location" field is still incorrect in some cases.


No page is displayed at all when a virtual server is accessed.


An error message on the Web browser indicates that the desired file could not be found.


A home page can be accessed from your local network, but is not accessible through the Internet.


After moving the HomeDoor extension to another Mac, home pages no longer come up.


When accessing a virtual server, the browser goes into a "redirection loop," continuously looking up and then trying to contact the same host.


The HomeDoor extension will not load at start up, displaying a red "X" through the HomeDoor icon.


No HomeDoor icon is displayed at start up.


Only the first few addresses configured into HomeDoor seem to work correctly.


TCP/IP services do not seem to work on the Macintosh on which the HomeDoor extension is running.


TCP/IP services do not work on another device on the network whose IP address is within HomeDoor's range.


HomeDoor Admin claims HomeDoor is not in the extensions folder.


HomeDoor's status could not be set to "Active" in HomeDoor Admin's Redirection Preferences dialog.


HomeDoor's logging could not be set to "On" in HomeDoor Admin's Redirection Preferences dialog.


The HomeDoor log file cannot be read by another application.


A change made with HomeDoor Admin has not taken effect


 

Troubleshooting: Host Field Mapping

Some accesses to the "real" server through new browsers don't work


Some accesses to the "real" server through old browsers don't work


A virtual Web server is not working at all


No virtual Web servers are working, even though I configured the plug-in with HomeDoor Admin.


Another plug-in that used to work has stopped working.


A change made with HomeDoor Admin has not taken effect


Back to Table of Contents
Back to Admin Reference
Forward to Appendixes