Sun ONE logo     Previous      Contents      Index      Next     
Sun ONE Web Proxy Server 3.6 SP2 Installation Guide - NT Version

Chapter 3   Troubleshooting Installation


This section describes common installation problems and solutions.

You accidentally denied all access to the Administration forms.
Log in as administrator or with the proxy's user account. In the server root directory, edit the magnus.conf file. See the Administrator's Guide for more information on this file.

You don't remember on what port your administration server is running.
Look in your ns-admin.conf file, which is in the admin-serv\config directory under your iPlanet server directory. In ns-admin.conf, you will find a Port entry that specifies on what port your administration server is located. You can change this value if you want your administration server to run on a different port, but make sure you restart the administration server after you change the value.

Your administration server responds "Unauthorized host" when you try to connect to it.
Open up your administration server to all sites by going into theAdministration section of your NT registry and deleting the lines for Hosts and Addresses (either of these might not be present). Then restart your administration server (go into the Services control panel and stop or start the iPlanet Administration or iPlanet Administration Server service). You will then be able to get back into the administration server, where you can try new settings for your host and address restrictions.

You have forgotten the password to your administration server and you can't log in to your administration pages.
Go into your ns-home directory, and into the admin-serv directory under that. You should find an admpw text file containing a single line of text something like this:


The first part of the line is the name of your administration account (usually just admin), and the second part is your encrypted administration password. Edit this file to remove the encrypted password so that your file looks like this:


Then shut down your administration server, bring it back up again, and log in to your administration server, but don't give any password. The server should let you in, at which point you can go to the appropriate configuration page to set a new administration password.


Because it is so easy to change the administration password this way, you should periodically make certain that your administration password file and your web server's configuration files cannot be edited by anyone, and that only trusted people have access to them. (By default these files cannot be edited by anyone, but you should verify this fact occasionally.)

You don't have access to the proxy.
Log in as root or the proxy's user account. In the server root directory, edit the obj.conf file and remove the following lines:

<Client dns="[wildcardpattern]" ip="[wildcardpattern]">
PathCheck fn=deny-service

[wildcardpattern] is a shell expression that matches your DNS or IP address. You can also edit the wildcard patterns so that your user account information isn't included. To deny service to everyone except a select group, use *~ before the wildcard pattern (for example, *~* denies service to everyone except those from the domain). See the Administrator's Guide, for more information on wildcard patterns.

Clients can't find the proxy server.
First try using the host name. If that doesn't work, use a fully-qualified name (in the form proxy.subdomain.domain). If that doesn't work, use the dotted quad IP address.

The proxy is slow, and transfers take too long.
The proxy computer might need more RAM to handle the load, or, if other applications are on the proxy machine, they might be degrading proxy performance by using most of the computer's memory.

You can also reduce transfer time by configuring the cache refresh setting. See the Administrator's Guide for more information on the cache refresh setting.

When installing my server, I get a message saying not to interrupt while performing the install, but the program doesn't install anything.

Be sure to click on the "Install now" link on the page that says "Do not interrupt." The "Do not interrupt" message refers to the time after the user has clicked install.

When installing my server on my Windows NT machine, I get the following error message:
confhttp: LODCTR returned error code 11

The LODCTR utility is used to set up performance monitoring-related keys in your Windows NT registry. Error 112 means that it ran out of space either on your hard disk or in the registry.

If during installation on a Windows NT machine, you see an error message similar to the one above, make sure that you have plenty of free space on your hard disk; if you do, then Windows NT may have filled up its registry. You can check the registry by going into the System control panel and (on NT 3.51) clicking the "Virtual Memory" button or (on NT 4.0) going to the "Performance" tab and clicking "Change." The window that appears will show you the current and maximum registry sizes. If the current size is near the maximum size, then raise the maximum setting, reboot your machine, and install your iPlanet server again.

If the error continues to appear, remove entries from your Windows NT registry. Run the program "REGEDT32.EXE" (which comes with Windows NT), and delete these two keys and anything below them:



Then close REGEDT32.EXE and start the installation over; it should work normally.

Previous      Contents      Index      Next     
Copyright 2003 Sun Microsystems, Inc. All rights reserved.