NT Server Domain not found error

[sysadmin]

Hi Todd,

We still have the earlier said problem, but the last time it happened was when the NAS box got completely full! now we are monitoring it closely.

Another issue, we are migrating to windows 2003 server and Active Directory in a couple of weeks time, can you please guide us through the process. When the earlier said issue occured we had tried to join the NAS box to another windows 2003 based network, but got a lot of errors, so we would like to have a complete step by step procdure before starting on it.

regards
Ananth.

[To-M]

This procedure is the same, when changing from your PDC environment select ADS with all ADS server information Password and Username. Please make sure DNS, Server Time on both systems are set properly. Also remember ADS uses Kerberos (Please review Microsoft Kerberos documentation) please check all Kerberos in your Windows server and review any ticket or life of tickets, this is located in the GPO of your Windows server (please review your Windows documentation). Also add the NAS computer in you ADS and make sure all your users are trusted. If you are still experiencing any issues please send logs to support@open-e.com

[sysadmin]

Dear Todd,

I'll get back on the joining to ADS Domain..

presently we are getting this message when we try to access the storage management web interface.


Index of /

Name Last modified Size Description

Apache/1.3.26 Ben-SSL/1.48 Server at ancom Port 443

We usually get it back if we restart the system, but is there any way to permanently solve this issue?

regards
Ananth

[To-M]

Can you test with FireFox and let me know if this still comes up with the same message.

[sysadmin]

We get the same error in both the browsers. In fact Firefox is our default browser!

regards
Ananth

[To-M]

Can you send a screen shot and logs to support@open-e.com to review this. Did this just happen recently? After sending logs try to clear them to see if this happens again.

[sysadmin]

I've send the screen shot by mail, this happened recently, we had it before I think, not sure, we access the Nas web interface from several systems is that the problem?