Networking Issues - Overland Storage SnapServer Administrator's Manual

SnapServer 7.0 Administrator's Guide
NOTE: To install GuardianOS, you must obtain the appropriate GuardianOS image file. This file is

Networking Issues

These are some of the networking issues you may encounter when using your SnapServer.
The Server Cannot Be Accessed over the Network
Inaccessibility may be caused by a number of reasons. To resolve this issue, use one of the
following methods:
• Verify that you have the correct IP address of the server, and try to connect again.
• Verify that the LED for the primary Ethernet port is lit. (This light indicates network
connectivity.) If the light is not lit, perform the following:
• The most likely cause is the physical connection. Check for a loose or damaged
• This problem may also be caused by a mismatch between the settings on the
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.
10400317-001 10/2011
available for download by entitled users from the SnapServer support site:
http://docs.overlandstorage.com/SnapServer
cable, or poor connections in the port connector.
switch 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 >
page of the Administrator Tool. Use the autonegotiate setting on both the
TCP/IP
switch and the server port.
©2010-11 Overland Storage, Inc.
C – Troubleshooting SnapServers
C-3.
C-4