Overland Storage SnapServer Administrator's Manual page 241

SnapServer GuardianOS 7.2 Administrator's Guide
• This problem may also be caused by a mismatch between the settings on the switch
You Have No Access to the SnapServer via HTTP
When trying to access the SnapServer via HTTP, the Web browser times out. The server can
be accessed using the ping command or Windows Explorer.
• HTTP and HTTPS are both enabled by default on SnapServers. Try typing HTTPS in
the Web address rather than HTTP. If you are able to access the server via HTTPS,
you can re-enable HTTP on the Network > Web page.
• If you cannot access the server via HTTPS, try resetting the server as described on
"Performing System Resets Without Network Access" on page
An Access Denied Message Appears after Configuring Microsoft Domain Security
Customers who have configured local users and local groups with the same name as their
domain users and groups can have security conflicts if they integrate with Microsoft Domain
Security. The SnapServer will authenticate the users as local SnapServer users before
authenticating through the Domain. However, the Domain users/groups may be the ones
that had been granted access to the shares.
Be careful not to add local users or groups that are duplicates of those that are found on the
Windows domain controller.
The SnapServer Does Not Operate Properly on a Network Running Gigabit-Full-Duplex
For Gigabit Ethernet to operate properly, both the switch and the SnapServer's primary
Ethernet port must be set to Auto (autonegotiate). Any other setting will result in
unexpected behavior and reduced performance.
The Network Does Not Have a DHCP Server and the SnapServer IP Address Is Unknown
Install SnapServer Manager (available from the SnapServer
Storage website) onto a client workstation on the same subnet as the SnapServer. You can
then use the utility to discover all SnapServers on that network segment, and to assign
static IP addresses as necessary.
Problems Occur with Domain Controller Authentication
You are receiving the following errors in your error log:
SMB: Domain Controller unavailable
SMB: Username not connected to Domain Controller
This means that either your Domain Controller is down, or the SnapServer is unable to
reach it. Because it cannot communicate with the Domain Controller, it is not able to
authenticate the user. Check to make sure the Domain Controller is online, is consistently
reachable via the network, and that users can authenticate to the Domain Controller.
10400317-003 05/2012
or hub and the settings on the SnapServer Ethernet port. These settings must
match. To resolve the problem, make sure the port settings on the hub or switch
match the settings for the primary port as configured on the Network > TCP/IP page
of the Web Management Interface. Use the autonegotiate setting on both the
switch and the server port.
©2010-12 Overland Storage, Inc.
Networking Issues
D-3.
support page on the Overland
 D-5