Adaptec 5325301656 Administration Guide - Page 195

The Network Does Not Have a DHCP Server and the Snap Server IP Address Is

Get Adaptec 5325301656 - Snap Server 14000 NAS PDF manuals and user guides
UPC - 753253016563
View all Adaptec 5325301656 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 195 highlights

Networking Issues Snap Server users before authenticating through the Domain. However, the 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. The Snap Server Does Not Operate Properly on a Network Running GigabitFull-Duplex For Gigabit Ethernet to operate properly, both the switch and the Snap Server's primary Ethernet port (Ethernet1) must be set to Auto (autonegotiate). Any other setting will result in unexpected behavior and reduced performance. The Network Does Not Have a DHCP Server and the Snap Server IP Address Is Unknown Install Snap Server Manager from the Snap Server User CD onto a client workstation on the same subnet as the Snap Server. You can then use the utility to discover all Snap Servers on that network segment, and to assign static IP addresses as necessary. Apple Users Cannot Log into the Snap Server as Windows Users To allow Apple users to access a Snap Server, replicate their user names and passwords locally on the Snap Server. An Apple Mac Connection to the Snap Server Is Reset When a Share Is Updated A Mac client connected to a Snap Server share may receive a message stating that the Snap Server will be going down in 5 minutes. This is because the AFP protocol needs to be restarted. To resolve this issue, reconnect to the share. 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 Snap Server 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. Appendix C Troubleshooting Snap Servers 181

  • 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
Appendix C
Troubleshooting Snap Servers
181
Snap Server users before authenticating through the Domain. However, the
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.
The Snap Server Does Not Operate Properly on a Network Running Gigabit-
Full-Duplex
For Gigabit Ethernet to operate properly, both the switch and the Snap Server’s
primary Ethernet port (Ethernet1) must be set to
Auto
(autonegotiate). Any other
setting will result in unexpected behavior and reduced performance.
The Network Does Not Have a DHCP Server and the Snap Server IP Address Is
Unknown
Install Snap Server Manager from the Snap Server User CD onto a client
workstation on the same subnet as the Snap Server. You can then use the utility to
discover all Snap Servers on that network segment, and to assign static IP addresses
as necessary.
Apple Users Cannot Log into the Snap Server as Windows Users
To allow Apple users to access a Snap Server, replicate their user names and
passwords locally on the Snap Server.
An Apple Mac Connection to the Snap Server Is Reset When a Share Is
Updated
A Mac client connected to a Snap Server share may receive a message stating that
the Snap Server will be going down in 5 minutes. This is because the AFP protocol
needs to be restarted. To resolve this issue, reconnect to the share.
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 Snap Server 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.