Filter
Top Products
2-46 Sun StorEdge 5310 NAS Troubleshooting Guide • December 2004
Using these two information sources, you can begin to diagnose the problem. The
following are the most common possible problems along with their indicating
symptoms.
Wrong password / insufficient permissions: This is usually indicated by a logon
failure or access denied message in the system log. The user account that is entered
into the StorEdge Domain configuration screen must have the correct password, and
must have the authority to create computer accounts. Typically, a user account that is
a member of the Domain Admins global group is used.
No master browser on the subnet: CIFS/SMB relies on a hierarchical system of
browser servers. Each IP subnet and network segment must have at least one such
server, known as a “master browser” in order for systems on that subnet to locate
network resources. StorEdge does not provide master browser services.
The first indication of this is the log message “No Master Browsers found for
<domain>”. Check the NetBIOS cache for the <1D> or <1B> tag with an IP matching
your subnet. Double check the domain name used against the one in the NetBIOS
tag of the master browser. It may be necessary to move the StorEdge to the same
subnet and segment as a master browser. All Windows server operating systems
provide master browser services by default. Installing StorEdge on the same subnet
as a Domain Controller is the best practice when possible.
If the problem persists after ensuring that StorEdge has a local master browser, check
the solutions below under “Multiple subnets connected to StorEdge”.
Other browsing problems: The log message, “Join domain [local]: locate failed”
indicates that a Domain Controller could not be found. Note that this message also
appears in conjunction with the above “No Master Browser found” message. When
that message is present, the above solutions should be followed first.
Start by looking at the NetBIOS cache. Look for <1B> or <1C> domain controller
tags. If you see any of these, ensure that the domain name matches the one
configured on StorEdge. If you see a <1D> segment master browser, but no <1B> or
<1C> tags, check the NetBIOS cache on the master browser system. This is done
with the “nbtstat –c” at the Windows command prompt. The output is essentially the
same as the StorEdge NetBIOS cache display. If no domain controllers are present in
the master browser’s NetBIOS cache, then there is a network browsing issue that
needs to be addressed.
One possible solution is to add a WINS server. WINS helps to speed Windows
browsing and compensates for browsing problems. WINS can compensate for
browser deficiencies, and should be used whenever possible. In order for WINS to
function properly, the browsers, domain controller and StorEdge must be configured
to use the server for lookups. Another possible solution is to move the StorEdge to
the same subnet as the Domain Controller, though this does not address the larger
browsing problem.
If these solutions have been attempted to no avail, also see the following solution.