Networking Issues
Chapter 10 Troubleshooting Snap Servers
95
Networking Issues
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, do the following in the order
indicated:
a
The most likely cause is the physical connection. Check for a loose or damaged
cable, or poor connections in the port connector.
b
This problem may also be caused by a mismatch between the settings on the
switch or hub and the settings on the Snap Server 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 >
TCP/IP
screen of the Administrator Tool. Use the autonegotiate setting on both
the switch and the server port.
You Have No Access to the Snap Server via HTTP
When trying to access the Snap Server via HTTP the Web browser times out. The
server can be accessed using the ping command or Windows Explorer.
a
HTTP and HTTPS are both enabled by default on Snap Servers. 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 View
screen.
b
If you cannot access the server via HTTPS, try resetting the server as described
on “Using Maintenance Modes to Perform System Resets” on page 93.
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 Snap Server will authenticate the users as local
Snap Server users before authenticating through the NT Domain. However, the NT
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.
Summary of Contents for 5325301638 - Snap Server 4500 NAS
Page 2: ......
Page 10: ...x Snap Server Administrator Guide ...
Page 14: ...xiv Snap Server Administrator Guide ...
Page 42: ...NIS Domain 28 Snap Server Administrator Guide ...
Page 68: ...Setting File and Folder Permissions Windows 54 Snap Server Administrator Guide ...
Page 96: ...Log View 82 Snap Server Administrator Guide ...
Page 116: ...Phone Home Support 102 Snap Server Administrator Guide ...