EasyManua.ls Logo

Overland Storage SnapServer - Miscellaneous Issues

Overland Storage SnapServer
326 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
10400589-001 ©2008-14 Overland Storage, Inc. 293
SnapServer / GuardianOS 7.6 Administrators Guide D - Troubleshooting
A SnapServer is 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 running the SSM utility.
Use the server name method if you are installing just 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 following the IP address before the share. This
returns an Access Denied message. The correct syntax should be the following (added slash
shown in red):
mount 192.168.32.124:/SHARE1 /mnt
NOTE: The share name is case-sensitive.
You Cannot Log in as Root to 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 has joined the Active Directory domain properly but you cannot see the
domain users when you set share permissions from the Web Management Interface.
Make sure the Windows client (PC) you are trying to set permissions from is assigned a valid
DNS server. You can check your Windows client using the
ipconfig command from a
command prompt.
Miscellaneous Issues
These are some miscellaneous issues you may encounter when using your SnapServer.

Table of Contents

Other manuals for Overland Storage SnapServer

Related product manuals