nas 8000 cant access win 2003 domain

[chrif]

we have a nas 8000 configured on NT domain and now we belt a new win 2003 domain. I'v trayed to join the nas 8000 to the new domain but it do not: error cant join domain XXXX.
any idea ?

software version 1.4.1

[Vincent Fleming]

The NAS8000 has been discontinued for some time now - I believe it's not compatible with the Win2003 domain structure.

However, I think you should be able to join a Win2000 domain - If your win2003 was installed in Native Mode, I think you may be out of luck. Sorry.

You can try re-installing your win2003 domain in the Win2000 compatibility mode (I know, it's unlikely that you'll be able to do this).

Your next choice would be to upgrade the NAS8000 to a newer model.

Good luck,

Vince

[chrif]

hi,

Thaks for the answer.

My win 2003 domain is already in win 2K native mode. And I upgraded this week end to OS 1.6.1 but this did not solv the problem. any idea ?

best regards

[Monty Phillips]

Hi Chrif,

What is the exact model of your NAS8000? Is is a NetServer or a Proliant 580 G2? If it is based on the Netserver, you can't upgrade to the 1.6.x NasOS versions. It sounds like you were able to upgrade to 1.6.1, so you should be OK, but we should be sure.

I would suggest a couple things to check and try with your new DC:

1) Upgrade to 1.6.3. This is the latest NasOS version for the NAS8000 (Proliant 580G2 platform). It can be downloaded from the HP support website: http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?locale=en_US〈=English+%28US%29&pnameOID=79206&prodSeriesId=79204&prodTypeId=12169&basePartNum=COL4682&locBasepartNum=co-16096-1&os=Cross+OS&tech=Operating+System

2) Windows NT domains use WINS servers, but native Windows 2000 domains typically do not use them. Since the NAS8000 requires a WINS server, when installing in a native Windows 2000 domain, make sure there is a WINS server properly setup with the domain controllers in the WINS database.

3) After one or more unsuccessful attempts to join a domain, it is possible the failure is caused by the NAS8000 node(s) already being in the domain controller list. If that happens, remove the NAS8000 nodes(s) from the list and try again to join.

4) Some Windows domains are set to restrict anonymous mode 1 or 2. With such a domain setting, Windows clients cannot connect to any NAS8000 shares. The NAS8000 does not support restrict anonymous mode 2, so when a domain is set to mode 2, it must be set to either mode 0 or 1. With mode 0, nothing more needs to be done. With mode 1, you will need to run an extra command on the NAS8000 to make it work correctly (I can provide that to you if you need it).

- Monty