12.07.2015 Views

Symantec™ Security Gateways Reference Guide - Sawmill

Symantec™ Security Gateways Reference Guide - Sawmill

Symantec™ Security Gateways Reference Guide - Sawmill

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Log messagesAlert messages (500-599)257508 - The Symantec Client VPN is not installed correctlyDescription: The client VPN has not been installed appropriately.508 - Unauthorized service stoppedDescription: The vulture routine found an unauthorized user service running and it terminates it gracefully. Eitherignore, if the service was not supposed to be running, or add that service to the vulture.runtime file.509 - The Symantec Enterprise Firewall is not installed correctlyDescription: VPN client was unable to run, as it was not installed appropriately on the security gateway.510 - Could not refresh kernel routing table cacheDescription: The security gateway uses the kernel routing table to find the appropriate router to which to send packets.In this case, the kernel routing table could not be updated.510 - Kernel routing table cache is not loadedDescription: The security gateway uses the kernel routing table to find the appropriate router to which to send packets.In this case, the kernel routing table could not be loaded.513 - Saved trace fileDescription: This message is logged when the SMTP application (smtpd) saves a trace of a smtpd session in a file.514 - Unauthorized HTTP protocol responseDescription: An illegal protocol was sent back to the HTTP proxy. It did not begin correctly, or arrived on an illegal port.514 - Unauthorized HTTP protocol response (headers required by rule)Description: An illegal protocol was sent back to the HTTP proxy. It did not have expected headers in the message.514 - Unauthorized SMTP protocolDescription: SMTP sends this message when a user attempts an illegal SMTP protocol command.515 - User attempted to connect toDescription: The user attempts to connect to the security gateway directly and was denied access.515 - User attempted to connect to portDescription: This message is logged when the security gateway detects an attempt to use its proxies to connect to one ofthe security gateway’s control ports.515 - User attempted to connect to port. Add httpd.allow_proxy_to_port_=1 to theconfig.cf file to allow this (not recommended without investigation)Description: A user attempted to connect to an illegal port. Access was denied.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!