Sun Microsystems 5310 NAS Server User Manual


 
2-48 Sun StorEdge 5310 NAS Troubleshooting Guide December 2004
6. Reboot the StorEdge.
Note that the above changes do not take effect until after the reboot.
This action removes the undesired entries in almost every case. The only case where
the entries may persist is in a multiple server WINS environment using replication.
In this case, consult the provider of the WINS server operating system for removal
instructions.
Anonymous connections restricted by Domain Controller: In this case, the master
browser and domain controller are both located, but the system log shows a number
of RPC errors related to security, along with the name and IP address of the Domain
Controller to which it is attempting to authenticate.
Windows 2000 and later operating systems can be configured to refuse anonymous
connections, otherwise known as null sessions. Typically, this is done for security
reasons. Restricting anonymous connections is not recommended unless all clients
and servers in the domain are running Windows 2000 or newer. StorEdge and other
non-Windows servers require a change to this policy.
This setting is accessed via the registry editor on the Windows domain controller.
Using the Registry Editor, navigate to the key: “HKEY_LOCAL_MACHINE\
SYSTEM\CurrentControlSet\Control\LSA”. Locate the value RestrictAnonymous. If
it is set to “2”, modify it to “0” or “1”. A setting of “0”
The Domain Controller must be rebooted for this change to take effect.
Connected to a DC across a WAN link: In rare cases, it is possible that StorEdge will
join a domain using a distant Domain Controller across a slow link. The symptoms
in this case will vary. You could see timeouts, authentication failures due to a
firewall, or even success with poor performance. The primary indication will be log
messages indicating any of the above problems, and referring to communications
with a Domain Controller on a faraway subnet.
To resolve this issue, first check the NetBIOS cache as directed above to ensure that
the local domain controllers are present. If not, proceed as above to correct any
difficulty locating them. After verifying the presence of one or more nearby Domain
Controllers (<1B> or <1C> NetBIOS tags), proceed as follows to force StorEdge to
use a particular Domain Controller:
1. Connect to the StorEdge via Telnet, and type “admin” at the [menu] prompt and
enter the administrator password.
2. At the CLI, enter “set smb.pdc <IP address>”, replacing <IP address> with the IP
address of one of the above domain controllers. In spite of the variable name, it is
acceptable to use either a PDC <1B>, or a BDC <1C>.
3. After setting the variable, retry the attempt to join the domain. Check the system
log to ensure success.