Symantecâ¢ Security Gateways Reference Guide - Sawmill

More documents

Recommendations

Info

232 Log messagesError messages (400-499)401 - Cannot contact driverDescription: Eagle service is unable to contact the driver.401 - Cannot create request queueDescription: This is a HTTP protocol error, and it indicates a security gateway resource problem that is cleared byrestarting the proxy.401 - Cannot create server socket listDescription: This is a HTTP protocol error and it indicates a security gateway resource problem that is cleared byrestarting the proxy.401 - Cannot create threadDescription: A proxy was unable to create an additional thread for processing connections.401 - Cannot create thread (out of memory)Description: A process was unable to create an additional thread for processing connections. If the process continues, itwill do so at a degraded level.401 - Cannot determine source IP address. Source IP will not be blacklistedDescription: The security gateway detected a condition which causes the source address to be blacklisted. As the sourceaddress is not specified, it is not blacklisted.401 - Cannot determine type of interfaceDescription: This indicates a severe Sun Solaris DLPI installation or network configuration error.401 - Cannot determine type of interface or cannot find interface nameDescription: This indicates a severe Sun Solaris DLPI installation or network configuration error.401 - Cannot disable userDescription: (Microsoft Windows only) Vulture daemon is unable to save an illegal account.401 - Cannot executeDescription: A component was unable to run a user script. The log message identifies the component. Execute the scriptfrom the command line to check its validity.401 - Cannot find entry for message IDDescription: The FTP daemon attempts to load the string resources, that it requires, to create the FTP greeting, but wasunable to complete. FTP will terminate. Confirm that the ResourceDictionary.xml is in the sg\lang\endirectory.401 - Cannot find file tar fileDescription: This message indicates an internal software error. Please contact Technical Support by phone or online athttp://www.symantec.com/techsupp/ to report this.
Log messagesError messages (400-499)233401 - Cannot find kill file descriptor for daemonDescription: Gwcontrol attempted to kill a connection but the connection information was invalid.401 - Cannot generate a key schedule from the session keyDescription: A secure remote login (SRL) client was unable to connect to the security gateway’s SRL daemon because itcould not generate a key schedule from the session key.401 - Cannot get blacklist protocol numberDescription: The notify daemon was unable to communicate with the remote blacklist daemon because of an invalidprotocol. The IP address is not blacklisted.401 - Cannot get interface listDescription: Blacklist daemon attempts to get the interface list to track the intruder, but fails.401 - Cannot get IP address of blacklist firewallDescription: Unable to get the IP address of the blacklist daemon that runs on another security gateway. The list ofblacklisted hosts are not sent.401 - Cannot get process listDescription: Vulture daemon is unable to acquire a list of legitimate processes that are functioning.401 - Cannot get socket for connectionDescription: Unable to allocate a socket for the connection between the security gateway services and gwcontrol.401 - Cannot get system nameDescription: (Microsoft Windows only) Unable to get the name of the security gateway, which is required by MicrosoftInternet Information Server.401 - Cannot initialize rule cacheDescription: The component was unable to load the security gateway rules as it does not have sufficient memory.401 - Cannot initialize rule caches, so performance may be degradedDescription: The HTTP daemon was unable to read the rules into its cache. The HTTP daemon will continue to apply therules, but will have to read the rule file repeatedly.401 - Cannot kill processDescription: The process cannot be killed.401 - Cannot lookup attached devicesDescription: There were either no interfaces configured, or an error occurred while building a list of interfaces.
Page 1 and 2:
Symantec Security GatewaysReference
Page 3:
Licensing and registrationContactin
Page 6 and 7:
6 ContentsMail server record ......
Page 8 and 9:
8 ContentsChapter 9Chapter 10Append
Page 10 and 11:
10 Contents
Page 12 and 13:
12 Introducing Symantec security ga
Page 14 and 15:
14 Introducing Symantec security ga
Page 16 and 17:
16 Network security overviewSecurit
Page 18 and 19:
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
24 Network security overviewManagem
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
32 Security gateway fundamentalsRou
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
38 Security gateway fundamentalsDom
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
44 Understanding accessNetwork prot
Page 46 and 47:
46 Understanding accessNetwork prot
Page 48 and 49:
48 Understanding accessProxiesProxi
Page 50 and 51:
50 Understanding accessProxiesExamp
Page 52 and 53:
52 Understanding accessProxiesThe D
Page 54 and 55:
54 Understanding accessProxiesThe H
Page 56 and 57:
56 Understanding accessProxiesThe N
Page 58 and 59:
58 Understanding accessProxiesThe S
Page 60 and 61:
60 Understanding accessProxiesTable
Page 62 and 63:
62 Understanding accessService grou
Page 64 and 65:
64 Understanding accessRulesTable 4
Page 66 and 67:
66 Understanding accessRulesWhen a
Page 68 and 69:
68 Controlling service accessFilter
Page 70 and 71:
70 Controlling service accessFilter
Page 72 and 73:
72 Controlling service accessConten
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
78 Controlling user accessAuthentic
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
86 Controlling user accessTime Peri
Page 88 and 89:
88 Understanding VPN tunnelsTunnels
Page 90 and 91:
90 Understanding VPN tunnelsTunnels
Page 92 and 93:
92 Understanding VPN tunnelsIPsec s
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
100 Understanding VPN tunnelsGlobal
Page 102 and 103:
102 Monitoring security gateway tra
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
114 Preventing attacksAntivirus (ap
Page 116 and 117:
116 Preventing attacksIntrusion det
Page 118 and 119:
118 Preventing attacksLogical netwo
Page 120 and 121:
120 Preventing attacksAddress trans
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
126 Preventing attacksAnti-spam mea
Page 128 and 129:
128 Ensuring availabilitySymantec
Page 130 and 131:
130 Ensuring availabilityStateful f
Page 132 and 133:
132 Ensuring availabilityCluster ad
Page 134 and 135:
134 Log messagesInformational messa
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
158 Log messagesNotice messages (20
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
176 Log messagesWarning messages (3
Page 178 and 179:
Page 180 and 181:
Page 182 and 183: 182 Log messagesWarning messages (3
Page 230 and 231: 230 Log messagesError messages (400
Page 256 and 257: 256 Log messagesAlert messages (500
Page 258 and 259: 258 Log messagesAlert messages (500
Page 260 and 261: 260 Log messagesCritical messages (
Page 270 and 271: 270 Log messagesEmergency messages
Page 272 and 273: 272 Log messagesEmergency messages
Page 274 and 275: 274 IDS eventsAbout IDS/IPS events
Page 282 and 283:
282 IDS eventsAbout IDS/IPS events
Page 284 and 285:
Page 286 and 287:
Page 288 and 289:
Page 290 and 291:
Page 292 and 293:
Page 294 and 295:
Page 296 and 297:
296 IDS eventsDenial-of-ServiceTabl
Page 298 and 299:
298 IDS eventsDenial-of-ServiceResp
Page 300 and 301:
300 IDS eventsDenial-of-ServiceMalf
Page 302 and 303:
302 IDS eventsIntrusion attemptsUnk
Page 304 and 305:
304 IDS eventsIntrusion attemptsCod
Page 306 and 307:
306 IDS eventsIntrusion attemptsDNS
Page 308 and 309:
308 IDS eventsIntrusion attemptsAff
Page 310 and 311:
Page 312 and 313:
312 IDS eventsIntrusion attemptsFTP
Page 314 and 315:
314 IDS eventsIntrusion attemptsHTT
Page 316 and 317:
Page 318 and 319:
Page 320 and 321:
320 IDS eventsIntrusion attemptsIMA
Page 322 and 323:
322 IDS eventsIntrusion attemptsIRC
Page 324 and 325:
324 IDS eventsIntrusion attemptsIRC
Page 326 and 327:
Page 328 and 329:
328 IDS eventsIntrusion attemptsNim
Page 330 and 331:
330 IDS eventsIntrusion attemptsNim
Page 332 and 333:
332 IDS eventsIntrusion attemptsOSP
Page 334 and 335:
334 IDS eventsIntrusion attemptsRlo
Page 336 and 337:
Page 338 and 339:
Page 340 and 341:
Page 342 and 343:
342 IDS eventsIntrusion attemptsSta
Page 344 and 345:
Page 346 and 347:
Page 348 and 349:
Page 350 and 351:
Page 352 and 353:
352 IDS eventsIntrusion attemptsWAR
Page 354 and 355:
354 IDS eventsProbesSensor Record F
Page 356 and 357:
356 IDS eventsProbesAffected:No spe
Page 358 and 359:
358 IDS eventsSignaturesSMTP Probin
Page 360 and 361:
360 IDS eventsSignaturesHTTP IIS IS
Page 362 and 363:
362 IDS eventsSignaturesAffected: A
Page 364 and 365:
364 IDS eventsSuspicious activitySu
Page 366 and 367:
366 IDS eventsSuspicious activityBG
Page 368 and 369:
368 IDS eventsSuspicious activityBG
Page 370 and 371:
370 IDS eventsSuspicious activityDN
Page 372 and 373:
372 IDS eventsSuspicious activityFT
Page 374 and 375:
374 IDS eventsSuspicious activityAf
Page 376 and 377:
Page 378 and 379:
378 IDS eventsSuspicious activityHT
Page 380 and 381:
Page 382 and 383:
Page 384 and 385:
Page 386 and 387:
Page 388 and 389:
Page 390 and 391:
Page 392 and 393:
392 IDS eventsSuspicious activityId
Page 394 and 395:
394 IDS eventsSuspicious activityIM
Page 396 and 397:
Page 398 and 399:
Page 400 and 401:
Page 402 and 403:
Page 404 and 405:
404 IDS eventsSuspicious activityMa
Page 406 and 407:
Page 408 and 409:
Page 410 and 411:
Page 412 and 413:
Page 414 and 415:
Page 416 and 417:
Page 418 and 419:
Page 420 and 421:
Page 422 and 423:
Page 424 and 425:
Page 426 and 427:
Page 428 and 429:
Page 430 and 431:
Page 432 and 433:
Page 434 and 435:
Page 436 and 437:
Page 438 and 439:
Page 440 and 441:
Page 442 and 443:
442 IDS eventsSuspicious activityNN
Page 444 and 445:
444 IDS eventsSuspicious activityOS
Page 446 and 447:
446 IDS eventsSuspicious activityOS
Page 448 and 449:
448 IDS eventsSuspicious activityPO
Page 450 and 451:
450 IDS eventsSuspicious activityRl
Page 452 and 453:
452 IDS eventsSuspicious activityRP
Page 454 and 455:
454 IDS eventsSuspicious activityRe
Page 456 and 457:
Page 458 and 459:
458 IDS eventsSuspicious activitySM
Page 460 and 461:
460 IDS eventsSuspicious activitySN
Page 462 and 463:
462 IDS eventsSuspicious activitySO
Page 464 and 465:
Page 466 and 467:
Page 468 and 469:
Page 470 and 471:
Page 472 and 473:
Page 474 and 475:
Page 476 and 477:
Page 478 and 479:
Page 480 and 481:
Page 482 and 483:
Page 484 and 485:
Page 486 and 487:
Page 488 and 489:
Page 490 and 491:
Page 492 and 493:
Page 494 and 495:
Page 496 and 497:
Page 498 and 499:
Page 500 and 501:
Page 502 and 503:
Page 504 and 505:
Page 506 and 507:
Page 508 and 509:
508 IDS eventsSuspicious activity
Page 510 and 511:
510 IndexIP address spoofing 21Man-
Page 512 and 513:
512 IndexHH.323alias report 105prox
Page 514 and 515:
514 IndexRTSP 57service parameters
Page 516:
516 Index
show all

Symantecâ¢ Security Gateways Reference Guide - Sawmill

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?

Symantecâ¢ Security Gateways Reference Guide - Sawmill