Cannot connect to Novell's iManager

Posted on 2003-11-14
Last Modified: 2011-08-18
I cannot connect to Novell'siManager.  I can connect to iMonitor at https://<>:8009
I've tried http://<>:2200 like some places on the net suggest, also
According to this: admin_ovw/data/am4s09s.html
I should be able to do this:
... To start iManager in regular mode, open a Web browser and enter either the IP address
or DNS name of the server, followed by /nps/iManager.html.  This does not work either.

Acording to this link: nw65/uddi/data/aj4j2tu.html
I should be able to use this: Tomcat Standalone: http://hostname:8080/nps/iManager.html
For Apache/Tomcat: http://hostname/nps/iManager.html
For Apache/Tomcat with SSL: https://hostname/nps/iManager.html
On NetWare 6.5 for Apache/Tomcat with SSL: https://hostname/nps/iManager.html
On NetWare 6.5 for Apache/Tomcat without SSL: http://hostname/nps/iManager.html

where hostname is the server name or IP address of the server where the UDDI service is running.

None of these work.   Which file do I examine, or how else do I find which port iManager is listening to?  TCPCON/protocol information/tcp/tcp connections lists the ports, but not what is listening on them.  

NDSIMON.nlm is indeed running, and I can connect to iMonitor with https://<ipaddress>:8009 just to recap.

More info:  I've upgraded to edir 8.71 on the server with the Master Replica, I've install iManager 2.01 and installed the Novell JVM 1.4.1 which was required by Tomcat.

Found some stuff here (finally after 12 hours of searching).  I'll keep you all up to date.

Question by:sgdought
  • 7
  • 4
  • 2
LVL 35

Expert Comment

ID: 9749112
Firstly, I would recommend that you ask in the CS TA to have this question moved to the NetWare subtopic area.  There are ppl there that are true Novell Experts that don't always show up in the Networking TA.

As to your problem.  Do you have a link to iManager from iMonitor?  Does it also give you an error?
LVL 35

Expert Comment

ID: 9749130
Also, have you tried reinstalling iManager?

The TID talks about iManager 1.2 and 1.51 and not 2.01, but it may still apply.

Author Comment

ID: 9749783
I did not see a Netware area.  Anyway, at this point I can get to to first iManager screen. I used an apache\conf\adminserv.conf from the UMich to see what ports I need to fix.  It was listening on 52443 instead of ssl 443.  Also redirects need to be pointed to port 2200.    Now I get prompted for a password, but it does not accept it.  I can use the login function to login to iMonitor, but the iManager login just prompts me 3 times, then goes to a page that says Authentication required.
That's where I stand at the moment.  
LVL 35

Expert Comment

ID: 9749830
This question is posted in the Networking topic area.  Among the subtopics in the networking topic area is Netware.  That's where all the NetWare wizards in EE do their wizardry.

When you put your login ID in, are you using the full context?  i.e. .admin.myorg?  or .me.myou.myorg?

Author Comment

ID: 9749937
Ok. I went to https://<IP Address>:2200/eMFrame/Simple.html and go a login screen complete with context.  I could login from this screen.  So I tried logging in from https://<IP Address>:2200 and got the windows authentication screen  I used just admin NOT admin.FullContext  and it worked.  Seems that the apache config files are ALREADY point to the correct context for admin, so I didnt needed to use anything but the name without the context.  Thanks anyway folks.
I will say iManager install and troubleshooting SUCKS as their is no documentation.
LVL 35

Expert Comment

ID: 9750085
There is documentation.  Don't get too frustrated too quickly. The Novell support knowledgebase is superior to any other software provider's knowledgebase I have used, including the mess that Microsoft has for a knowledgebase.  They have more online, web-accessible documentation available than any other software provider I have encountered in my 20-plus years in IT.
How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails


Author Comment

ID: 9750147
When I tried logging in from https://<IP Address>:2200 and got the windows authentication screen, the screen came up Netware Web Manager, with
NetWare® Enterprise Web Servers  

Novell® eDirectory™  

NetWare® Remote Manager  

eDirectory™ iManager    

On the left hand side.  You will notice that my test server White-srv1 is not listed under iManager

When I go to the URL https://<IP Address>:2200/eMFrame/Simple.html I get the following screen:
Version 1.0

   You are currently logged in as user admin.WHITE.CRIME.TOKYO.ACME
   in the Novell Directory Services tree acme-tree

Now I know I installed version 2.01 and that is what shows up in nwconfig\products\currently installed products.  So I wonder why iManage does not show up in Web Manager?  

Obviously this is a complex product that uses Apache and Tomcat4  which I will have to learn more about.

   Please select a task on the left.
LVL 35

Accepted Solution

ShineOn earned 100 total points
ID: 9750230
*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/
   Redirect /iManager
   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.
LVL 35

Expert Comment

ID: 9750424
I noticed that you were trying "simple.html" and getting a message regarding iManage 1.0.  

Have you tried accessing it directly using "imanager.html" instead of "simple.html" ???
LVL 10

Expert Comment

ID: 9752383
have you tried updating iManager to it's latest version?  I'm running iManager 1.21 myself - all is well here...


Author Comment

ID: 9752759
100 points to the man, ShineON.  There was indeed a file named iManage.html, NOT imanager.   I just copied it over to iManager.html and the URLs worked.  It still does not show up in Web Manager, but I can now get to it.  I looked for hours at the Novell website and managed to miss the TID that mentioned the name change.

Thank You.
LVL 35

Expert Comment

ID: 9752834
Check your redirect and include statements in ADMINSERV.CONF also - it may be missing the redirects for iManager, which would cause the link not to show in Web Manager.
LVL 10

Expert Comment

ID: 9768400
Did you shut down Java prior to upgrading iManager?  It's a must.

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Suggested Solutions

Title # Comments Views Activity
NDS object move 10 906
Netware 6.5 on VMWare with VMTools 5 1,890
Groupwise IMAP 2 1,135
log in log 7 546
This article explains how to prepare an HTML email signature template file containing dynamic placeholders for users' Azure AD data. Furthermore, it explains how to use this file to remotely set up a department-wide email signature policy in Office …
In  today’s increasingly digital world, managed service providers (MSPs) fight for their customers’ attention, looking for ways to make them stay and purchase more services. One way to encourage that behavior is to develop a dependable brand of prod…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.
This video shows how to remove a single email address from the Outlook 2010 Auto Suggestion memory. NOTE: For Outlook 2016 and 2013 perform the exact same steps. Open a new email: Click the New email button in Outlook. Start typing the address: …

706 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now