Re: Call home ?

From: DanS (t.h.i.s.n.t.h.a.t_at_a.d.e.l.p.h.i.a..n.e.t)
Date: 10/28/04


Date: Thu, 28 Oct 2004 16:40:03 -0500

DanS <t.h.i.s.n.t.h.a.t@a.d.e.l.p.h.i.a..n.e.t> wrote in
news:Xns9590B30B8B5E6idispcom@216.196.97.142:

> Now I have a question. After restarting my computer, for some reason I
> opened up a port monitoring program I have.
>
> There I saw an open socket, on port 80, with a remote IP that resolves
> to a Microsoft address. It was in a TIME_WAIT state, and a PID of 0,
> which in the processes, is System Idle Processes.
>
> I DO NOT use Windows Update, and it is disabled.
>
> This socket is being created by something at startup using
> RulDllAsApp.exe.
>
> Any ideas ?
>
> Thanks,
>
> DanS
>
>
>

rundll32.exe is what it actually is.

DanS



Relevant Pages

  • Call home ?
    ... After restarting my computer, for some reason I ... opened up a port monitoring program I have. ... There I saw an open socket, on port 80, with a remote IP that resolves to a ... the processes, is System Idle Processes. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Call home ?
    ... After restarting my computer, for some reason I ... > opened up a port monitoring program I have. ... > There I saw an open socket, on port 80, with a remote IP that resolves to ... > the processes, is System Idle Processes. ...
    (microsoft.public.windowsxp.security_admin)

Loading