Filter
Top Products
Chapter 2 NAS Head 2-49
Assuming that the difficulty connecting to the Domain Controller is temporary, and
related to network load, it should not be necessary to save this variable with the
savevars command. Doing so will limit the ability of StorEdge to find an alternate
Domain Controller in the case that this one fails.
Cannot connect or authenticate to Windows 2003 Domain
Controller.
By default Windows 2003 is configured to require signed digital communications
from clients. This is also known as SMB packet signing. StorEdge does not support
packet signing. Therefore, Windows 2003 must be configured to negotiate packet
signing rather than assuming that it is present.
1. To configure this, you must access the Local Security Policy Editor on the
Windows 2003 Server.
2. Next, navigate to Security Settings/Local Policies/Security Options.
3. Scroll down to “Microsoft network server: Digitally sign network
communications (always)”
4. Double click the entry and click the “Disabled” button.
5. Click “OK”.
Changing this setting does not restrict the Windows 2003 server from using packet
signing with those clients that support it.
Lost Connection with Windows Domain.
In some conditions, it is possible for StorEdge to lose connection to the Domain
Controller. In this case, Windows users will be denied access to the StorEdge, and
they will be prompted for a password.
Possible reasons for this include modification of administrative user password,
network problems or failure of PDC.
The solution to each of these is the same. It is necessary to re-enter the user and
password information in the domain setup screen. This is done as follows:
1. Access the StorEdge via Telnet.
2. Press enter at the [menu] prompt and enter the administrator password.
3. Press the spacebar until “CIFS/SMB Configuration” is displayed under
“Extensions” at the lower right.
4. Select the letter corresponding to “CIFS/SMB Configuration”.