Error accesing https://ip:2200

[kokaina]

I have a error on my browser when I access my server on

https://ipserver:2200

"The page you are looking for is currently unavailable. The Web site might be experiencing technical difficulties, or you may need to adjust your browser settings"

But

https://ipserver:8009

is working fine.

What is the service that support remote manager?
I don't want to make a restart of server.

 

[Novelli]

Hi 2200 is the Imanager.

Seems to be not running

Andreas

 

[marvhuffaker]

the service that runs port 8009 is completely different than port 2200. if 2200 isn't working, you are probably having apache problems, which could have numerous causes.

Marvin Huffaker, MCNE

http://www.redjuju.com

 

[kokaina]

thank you for your answer.
I will try with a server restart and see what hapens.
And if the problem persist, I will go deep.....to see the problem.

 

[terry712]

just restart apache

this rebooting a netware server is a very strange coccept

 

[Provogeek]

lol terry, but oh so true.


To clarify Marv's post ..

iManager is an Apache web service using the Tomcat web application server for eDirectory intergration.

Normally you will get to this by using the 2200 port. Personally do not use that link since out of the box in 6.5, it doesn't really work (you have to "unlock" it in your http.conf file). Try going to

https://IPADDRESS/nps/iManager

and see if you can login there. Better yet, type in "m apache2" (on NW6.5) or "m apache" (on NW6.0) to see if your apache process is running.

If it is, then type in "java -show" and see if the Tomcat process is running. Should say somthing like cantalina manager (not sure exactly of the text).

To restart the service type in:

java -killall
java -exit

[NW6.0 only]
NVXADMDN.NCF

[NW6.5 only]
ADMSRVDN.NCF
AP2WEBDN.NCF


Then to bring it up type in

[NW6.0]
NVXADMUP.NCF
TOMCAT33.NCF START

[NW6.5]
AP2WEBUP.NCF
ADMSRVUP.NCF
TOMCAT4.NCF
TCADMUP.NCF



Check the console logger and see if the tomcat produces a line that says somthing like "Listening on port 9009". Give ti about 3 to 5 minutes to load (even you have a nice fast 8GHZ server with tons of RAM, give it time to load before you decide it has failed). When you see the 9009 and/or 9008, then you cab be sure the TC process has loaded with out error.

Check in TCPCON to see if ports 80, 443, 2200 are open and listening.


Oh and before I forget, as Marv was saying, port 8009 (and 8008) are a different server, aka .... it ain't apache running remote manager. Remote Manager runs from the portal.nlm as the app server and the HTTPSTK.NLM as the web server.


=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
Brent Schmidt Certified nut case
Senior Network Engineer

http://www.kiscc.com

http://www.bluegunk.com