Overland Storage SnapServer Administrator's Manual page 228

SnapServer 7.0 Administrator's Guide
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.
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
10400317-001 10/2011
©2010-11 Overland Storage, Inc.
C – Troubleshooting SnapServers
support page on the Overland
C-5