Apple M8347LL/A User Guide - Page 189

Symptom/Cure Tables: System Problems After Startup - 57, Possible Fix

Page 189 highlights

Troubleshooting Symptom/Cure Tables: System Problems After Startup - 57 This table should help you troubleshoot and fix a modem that is recognized and able to dial out, but is having trouble connecting. The table is divided into different sections, each with its own symptom and cure(s). Find your symptom and then follow the instructions under the "Possible Fix" column to resolve the problem. Note: It is a good idea to check the Activity Log (accessible via the Remote Access menu) to see if there is an explanation for the failed connection attempt. Possible Cause Possible Fix The phone number is wrong. You don't have access to the server. Pauses in dialing are required. Verify the phone number of the server you're trying to call. Dial the number using a regular telephone and listen for the "whistle" of a modem. Make sure you're calling the type of server for which you've set up Remote Access. If you don't have access to the server, you may get an Authentication Failed message. Make sure you are a registered user on the server or that the server is set up for guest access. If trying to connect as a registered user, verify that you've entered your name and password correctly. Some servers require passwords that are case-sensitive, meaning capitalization matters. You may need to create pauses while the number is being dialed. Insert a comma between parts of the number where a pause might be needed. Inserting a comma lengthens the pause. For example, the following entries cause Remote Access to dial "9" to get an outside line and then pause before dialing the rest of the number: 9, 555-1234

  • 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
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263

Troubleshooting
Symptom/Cure Tables: System Problems After Startup - 57
The phone number is
wrong.
Verify the phone number of the server you
re trying to
call. Dial the number using a regular telephone and listen
for the
whistle
of a modem. Make sure you
re calling
the type of server for which you
ve set up Remote
Access.
You don
t have access to
the server.
If you don
t have access to the server, you may get an
Authentication Failed message. Make sure you are a
registered user on the server or that the server is set up
for guest access. If trying to connect as a registered
user, verify that you
ve entered your name and password
correctly. Some servers require passwords that are
case-sensitive, meaning capitalization matters.
Pauses in dialing are
required.
You may need to create pauses while the number is
being dialed. Insert a comma between parts of the
number where a pause might be needed. Inserting a
comma lengthens the pause. For example, the following
entries cause Remote Access to dial
9
to get an
outside line and then pause before dialing the rest of the
number:
9, 555-1234
This table should help you troubleshoot and fix a modem that is recognized and able to
dial out, but is having trouble connecting. The table is divided into different sections,
each with its own symptom and cure(s). Find your symptom and then follow the
instructions under the
Possible Fix
column to resolve the problem.
Note
: It is a
good idea to check the Activity Log (accessible via the Remote Access menu) to see if
there is an explanation for the failed connection attempt.
Possible Cause
Possible Fix