Cannot connect to Novell's iManager

*One possibility (from the Novell online knowledgebase:)

Here is the solution:  iManager link not present within the Web Manager. iManager not loaded.
The redirect lines or the include statement for iManager's configuration file is not present.   Check your SYS:APACHE\CONF\ADMINSERV.CONF file for the following statements:

Redirect /iManager/ https://server_ip:2200/eMFrame/iManager.html
Redirect /iManager https://server_ip:2200/eMFrame/iManager.html
Include "SYS:/webapps/eMFrame/WEB-INF/eMFrame-apache.conf"
 
 

Here is the problem or goal:
iManager link not present in the Web Manager.  iManager is not loaded.
 
There is no link for iManager in the Web Manager.
 
 
There is a link to iManager but it brings up "page cannot be found."
 
 

Problem Environment:
Novell NetWare 6.0
 
 
Novell Apache 1.3.26
 
Novell Apache 1.3.27
 
Novell NetWare Web Manager 3.5.3
 
Apache server is running off the primary IP address


*Here's another one:
Here is the solution:  iManage will not come up, thru Web Manager or through direct URL
Check to see if the redirect and include statements are found within the web manager virtual host configuration in the sys:apache\conf\adminserv.conf file.   The commands are as follows:

   Redirect /iManager/ https://10.1.1.1:2200/eMFrame/iManager.html
   Redirect /iManager https://10.1.1.1:2200/eMFrame/iManager.html
   Include "SYS:/webapps/eMFrame/WEB-INF/eMFrame-apache.conf"

Substitute your ip address with the one found in the redirect statements.

Another possibility for imanage / imanager not coming up is that there is no sys:webapps\eMFrame\iManager.html file.   There may be an iManage.html file.      This changed from the original installation of Netware 6 to the introduction of Netware 6 support pack 1.   The product was renamed to iManager.   So, an iManager.html file was created and placed in the directory.   If it is not there, you can create a copy of iManage.html and name it iManager.html.
 
 

Here is the problem or goal:
iManager will not come up either from web manager link or through direct URL to iManage page.
 

Problem Environment:
Netware 6
 
 
Apache engine comes up cleanly and is listening on all applicable ports:  80, 443, 2200, 2211.


* Or -
Here is the solution:  Cannot access iManager after adding a DNS address record
Bypass iManager and use the original DNS/DHCP Management Console for NW6.  (located under PUBLIC\DNSDHCP\Setup.exe, which requires Client32 on the client machine) This utility has proven to work efficiently with the NW6 DNS/DHCP configurations.  At this point you should be able to access the Management Console, correct the bad 'A' record and get past the -635 error you are seeing when using iManager.
 
 

Here is the problem or goal:
Cannot access iManager after adding a DNS address record
 
Secure Portal works (port 8009).  
 
Port 2200 also works, but then fails taking the link to iManager
 
"Login Failure" Error 635, the target server does not have the correct information about the source server"
 
Successfully able to access https://<dnsname>:2200/eMFrame/iManager.html and login the first time as Admin
 

Problem Environment:
Novell NetWare 6
 
Novell iManager
 

Additional Information:
Troubleshooting Steps:

Added an 'A' record for the server's DNS name and logged out.  
Attempting to login again to iManager, now fails with the following error: "Login Failure" Error 635, the target server does not have the correct information about the source server".
Tried accessing iManager via the server's IP address, thinking this was related to a DNS issue.
We ran a DSREPAIR -A (to repair the selected server address) and ran an additional full unattended DSREPAIR, but still could not access iManager.
Unloaded and reloaded NAMED.nlm and Apache and tried bouncing the server.