| Event Id | 6 |
| Source | POP3SVC |
| Description | Virtual Server %1: POP3 Server could not read registry key %2. The data is the error. |
| Event Information | This information from some newsgroups may help you: ------------------------------------------------------------------------------ This simple command file just establish a TCP connection to the POP3 server on port 110. When the connection succeeds, the connection is closed normally. The success or failure of the connection is reported in the command window. Very rapidly we saw a number of connection failures and this proves that the mail clients are indeed not the culprits. We changed on the POP3 server the registry key TcpTimedWaitDelay (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters) to the minimum value of 30 seconds. Although this seems to mitigate the problem, it didnt solve the problem completely. Moreover we dont consider this a good solution because you dont have in all scenarios administrative access to and control over the POP3 server. The second workaround was to distribute in some way a custom client LAT file named Locallat.txt and place it into the Microsoft Firewall Client folder on the client computer. The custom client LAT file should contain the IP address of the POP3 server so that any TCP request to that destination would not be handled by the Firewall client. Of course, all internal hosts should then be configured as SecureNAT client too and in the Firewall policy anonymous access should be allowed to the POP3 server. All internal clients were already configured as a SecureNAT client because the internal network was in fact a routed internal network. However, we didnt implement this workaround because distributing a custom client LAT file was too cumbersome as a temporary solution. The last workaround was to change the Firewall client configuration on the ISA server itself. Because all clients were already SecureNAT clients and that the overwhelming majority of the mail clients were Outlook, we could easely disable Outlook in the Firewall client configuration on the ISA server itself. To do that, go to t |
| Reference Links |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.