Re: Why is Win Explorer accessing the Net?
From: Alan P (alan_at_(nojunkplease)alancode.net)
Date: 01/12/04
- Next message: Rob Slade, doting grandpa of Ryan and Trevor: "REVIEW: "The Manager's Handbook for Corporate Security", Gerald L. Kovacich/Edward P. Halibozek"
- Previous message: Alan P: "Re: key logger question"
- Maybe in reply to: Black Baptist: "Re: Why is Win Explorer accessing the Net?"
- Next in thread: NeoSadist: "Re: Why is Win Explorer accessing the Net?"
- Reply: NeoSadist: "Re: Why is Win Explorer accessing the Net?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 12 Jan 2004 16:03:48 +0000 (UTC)
//> Explorer is not the OS. It is just a shell/user interface. For
> example, you can run cmd.exe as your shell just fine. You can even
> kill explorer using task manager and all the other programs continue
> just fine.
Then network neighbourhood wouldn't work :-|
<chris@nospam.com> wrote in message
news:4gmnuvcfejhbpd3ba9fvp9lmsk988dgc3m@4ax.com...
> On Thu, 25 Dec 2003 12:17:44 GMT, Lars M. Hansen
> <badnews@hansenonline.net> wrote:
>
> >On Thu, 25 Dec 2003 10:13:55 +0200, Lassi Hippeläinen spoketh
> >
> >>chris@nospam.com wrote:
> >>
> >>> Isn't it a bit odd that Explorer is the process reported doing the
> >>> discovery? Doesn't this discovery occur when tcpip or the ppp comes
> >>> up which may happen before explorer is running?
> >>
> >>It is Microsoft policy that Explorer cannot be separated from the
> >>operating system. They claimed that in court, so they must live by it...
> >>
> >
> >You are confusing "Explorer" with "Internet Explorer". Explorer _is_ the
> >OS, thus it is making the router discovery requests.
>
> Explorer is not the OS. It is just a shell/user interface. For
> example, you can run cmd.exe as your shell just fine. You can even
> kill explorer using task manager and all the other programs continue
> just fine.
>
> Explorer talks to the network by making calls to the underlying
> network subsystem, but it should not be doing the actual router
> discovery. My guess is that the software firewall is trying to
> identify what program was talking to the network when the router
> discovery occured.
>
>
> -Chris
- Next message: Rob Slade, doting grandpa of Ryan and Trevor: "REVIEW: "The Manager's Handbook for Corporate Security", Gerald L. Kovacich/Edward P. Halibozek"
- Previous message: Alan P: "Re: key logger question"
- Maybe in reply to: Black Baptist: "Re: Why is Win Explorer accessing the Net?"
- Next in thread: NeoSadist: "Re: Why is Win Explorer accessing the Net?"
- Reply: NeoSadist: "Re: Why is Win Explorer accessing the Net?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|