Remote Manager Woes
Articles and Tips: qna
01 Sep 2002
Q.
I am in the process of building new servers with the NetWare 6 Support Pack 1 from the Novell support site. After the initial build, I can access the default Web page and browse to the Remote Manager link, which takes me the following URL, as it should: https://server.domain:8009/.
If I down the server and press Ctrl-Alt-Del to bring it back up, all is fine. If I go to the server console and execute a RESTART SERVER command, the server reboots and I can access the default page, but port 8009 over HTTPS (secured) now results in a "The page cannot be displayed" screen. Dropping back to port 8008 over HTTP (unsecured) gets me back into the Remote Manager. Downing the server and Ctrl-Alt-Del restarting it does not restore the Remote Manager over secured HTTPS.
I have searched through the available TIDs and the closest one I can find is TID #10058811, which lists required NLMs to suppport SSL. I have verified that all of these NLMs are loaded. Moreover, I can access the server's default page over HTTPS, so I know my certificate is working.
Here is some other information:
Server Hardware: Dell PowerEdge 2650, 1GB RAM, 2.4GHz processor
Apache.NLM Version 1.03 September 17, 2001
JAVA.NLM Version 1.31 January 28, 2002
Dsrepair/Unattended Full Repair results in no errors or warnings
Any and all advice would be greatly appreciated.
Remoting Remotely with Rutherford
A.
Dear Remoting: The information you have provided me indicates this is a timing related problem. It is possible that httpstk and relatives can go wrong with race conditions during loading, and to fix that you can insert a delay between loading nile and httpstk. This should fix your problem.
* Originally published in Novell AppNotes
Disclaimer
The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.