svchost.exe is listening on port 135 for an internal TCP connection to support the Remote Procedure Call service. An external request comes in to connect to svchost from an outside source, and is blocked (correctly)-I think the way D+ states it is a bit misleading. And according to your other message it is directed at some other IP. Still don’t know why dialup sends stuff that is not addressed for you or whether it is a threat-probably all the dialup experts are somewhere else. You can make a rule to block and not log it if you just want the popups and logging to go away.
Earlier message at https://forums.comodo.com/empty-t22107.0.html;topicseen showed that it was a RPC connection request from one L3com server to another L3com server that somehow got routed to his address by his ISP. Lacking a dialup expert, and since things appear to be working, seems like a good thing to block. Only caution before was not to try to turn off the RPC service to stop the listening or the computer will stop working. See http://www.blackviper.com/WinXP/Services/Remote_Procedure_Call_(RPC).htm , for example.
Level 3 is a MAJOR internet infrastructure provider.
(I’ve read a number of articles about them in the financial press).
According to their web site:
The company operates one of the largest communications and Internet backbones in the world.