Overland Storage SnapServer Administrator's Manual page 242

SnapServer GuardianOS 7.2 Administrator's Guide
You Start Your SnapServer but Cannot See It on the Network
Ensure that the Ethernet cable is connected securely to both the network port and the
server's primary Ethernet port. Also, check to see that the Link light on the front of the
SnapServer is lit (solid green). If the Link light is off, this is normally caused by a mismatch
between the switch/hub and the Ethernet port on the SnapServer. To resolve this problem,
verify that all settings (if using multiple Ethernet ports) on the switch/hub match the setting
on the server. When the server is shipped from the factory, both ports are set to
autonegotiate. Therefore, the switch/hub must be set to autonegotiate to initially connect to
the server.
SnapServers are configured by default to acquire an IP address from a DHCP server. If no
DHCP server is found on the network, the SnapServer defaults to an IP address in the range
of 169.254.xxx.xxx and is labeled ZeroConf in SSM. While you may not be able to see the
server on your network, you can discover the SnapServer using either the default server
name or the SSM utility (available at our external download site:
http://www.overlandstorage.com/SSM). Use the server name method if you are installing one
SnapServer on the network. Use SSM if you are installing two or more SnapServers, or if
your network does not have IP-to-name resolution services.
You Try to Mount to a Share on Your SnapServer from Your Linux Workstation and You
Receive an RPC Timeout Message
Check the firewall configuration to your Linux workstation. Be sure you have not blocked
the ability to receive TCP or User Datagram Protocol (UDP) communications. If problems
persist, contact Overland Storage Technical Support.
You Receive an Access Denied Message When Attempting to Mount a Share on Your
SnapServer from a Linux Workstation
If you are logged in as root on your workstation and NFS is enabled on your SnapServer, this
message can be misleading, causing you to look for security issues, when in fact it could be a
command syntax issue. For example, the common Linux mount command:
mount 192.168.32.124:SHARE1 /mnt
is missing a forward slash (/) in the command, which will return an Access Denied message.
The correct syntax should be the following:
mount 192.168.32.124:/SHARE1 /mnt
NOTE: The share name is case-sensitive.
You Cannot Log in as Root to the SnapServer
GuardianOS allows you to log in as root over SMB. If this operation has failed or you have
trouble logging in, be sure that you have enabled root login in the Network > Windows/SMB
page. Also note that the root account password is tied to the admin account password. If you
cannot log in as root, change the password for the admin account on the Network >
Windows/SMB page. Use the admin password to log in as root.
You Are Unable to See Your Domain Users When Trying to Set Up Windows Security
Permissions on File Folders
The SnapServer (GuardianOS) has joined the Active Directory domain properly, and you can
see the domain users when you set Share permissions from the browser-based Web
Management Interface.
10400317-003 05/2012
©2010-12 Overland Storage, Inc.
Networking Issues
 D-6