Symantec™ Security Gateways Reference Guide - Sawmill

176 Log messagesWarning messages (300-399)Warning messages (300-399)Warning messages fall into the range 300-399. These message usually indicate an error condition that thesecurity gateway can recover from, but require attention to prevent further occurrences.300 - Cannot connect to clientDescription: The FTP server has terminated the connection with the FTP proxy, but the proxy is unable to notify theclient.300 - Cannot open socketDescription: The FTP server has terminated the connection with the FTP proxy.301 - A NAT device exists between local and remote gateways, so cannot use transport modeDescription: Transport mode calculates its checksum against a pseudo header that includes both the source anddestination address. Because the NAT device changes the source or destination address, and there is noinner IP header that keeps track of the original source and destination addresses, the checksum fails.Therefore, you cannot use transport mode with an intermediate NAT device.301 - A NAT device is detected between local and remote gateways, so cannot use IPsec AHprotocolDescription: Because AH uses the IP addresses in the packet header to calculate the checksum for encrypted packets,you cannot use the AH protocol with NAT. NAT changes the source address, destination address, or both,which causes the comparison AH checksum to fail.301 - Accept failedDescription: Gwcontrol logs this message if the accept call fails when attempting to accept a connect request from oneof the security gateway services or proxies.301 - Address not in the real address rangeDescription: The NAT component found an illegal address when trying to change the modified address back to itsoriginal address.301 - AH was selected, so hash algorithm cannot be NONEDescription: The Authentication Header (AH) provides authentication to the IP datagram by comparing the IntegrityCheck Value (ICV) on the content that is transmitted and received. Therefore, it does not encrypt or hidethe data.301 - Arguments too largeDescription: An incoming message at the Out of Band Authentication (OOBA) daemon is too large to be processed.301 - ASN packet too large (maximum 64K)Description: The Q931 packet is too large. This is a non-transparent connection, in which the setup protocol data unit(PDU) must be encoded. Connection cannot proceed.