Adaptec 5325301656 Administration Guide - Page 194

Networking Issues, You Have No Access to the Snap Server via HTTP

Page 194 highlights

Networking Issues • Resets the Administrator password to the default (admin) • Resets the web server to allow http Networking Issues These are some of the networking issues you may encounter when using your Snap Server. 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, perform the following in order: • The most likely cause is the physical connection. Check for a loose or damaged cable, or poor connections in the port connector. • 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. • 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 screen. • If you cannot access the server via HTTPS, try resetting the server as described on "Resetting the Snap Server to Factory Defaults" on page 178. 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 180 Snap Server Administrator Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224

Networking Issues
180
Snap Server Administrator Guide
Resets the Administrator password to the default (
admin
)
Resets the web server to allow http
Networking Issues
These are some of the networking issues you may encounter when using your Snap
Server.
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, perform the following in order:
The most likely cause is the physical connection. Check for a loose or damaged
cable, or poor connections in the port connector.
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.
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
screen.
If you cannot access the server via HTTPS, try resetting the server as described on
“Resetting the Snap Server to Factory Defaults” on page 178.
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