Adaptec 5325301638 - Snap Server 4500 NAS, Administrator'S Manual

Page: 111 / 148

Networking Issues
Chapter 10 Troubleshooting Snap Servers 97
mismatch between the switch/hub and the Ethernet port on the Snap Server. To
resolve this problem, verify that both settings (if using both of the server's 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.
The NT Event Viewer Reports Forced Master Browser Election When Snap
Servers Are Online
Snap Servers have the ability to act as a master browser on a Microsoft network.
This may cause a message to appear in an NT server's event log about a forced
master browser election.
Snap Servers should lose elections to Windows domain controllers (NT/2K/2K3),
but win against standalone Windows servers (NT/2K/2K3) and workstations (all
versions); however, users often prefer to prevent this election entirely.
The master browser option is enabled by default on Snap Servers to allow them to
appear more rapidly in a peer-to-peer Windows environment. In some
environments that include NT server systems, this may cause the NT server to show
warnings about having to force a master browser election in the event log. You can
prevent these warning messages by disabling the Master Browser option on the
Networking > Windows
screen.
You Try to Mount to a Share on Your Snap Server 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 UDP communications. If problems persist,
contact Snap Appliance Technical Support.
You Receive an Access Denied Message When Attempting to Mount a Share
on Your Snap Server from A Linux Workstation.
If you are logged in as root on your workstation and NFS is enabled on your Snap
Server, 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
Tip
The share name is case sensitive.