What is Tcpip? [Windows XP Basics]

Prev: Outline format disappeared
Next: Loads of GREAT SOFTWARE ( 20,000 plus programs DVDS and CDs)

From: William B. Lurie on 17 Mar 2010 19:12

Ken, here's a specific example of how Tcipp has
prevented the system from going into hibernation.

Event Type: Information
Event Source: Tcpip
Event Category: None
Event ID: 4201
Date: 3/17/2010
Time: 5:27:18 PM
User: N/A
Computer: COMPAQ-2006
Description:
The system detected that network adapter
\DEVICE\TCPIP_{D5E50A75-4A1C-4421-A5B4-569C9FE131B8} was connected to
the network, and has initiated normal operation over the network adapter.

This initiation of normal operation over the network
adapted was called by *something*, I'd like to know what,
and as a result the hibernation process, scheduled for
2 hours, was reset after 1 hour. Event Log has a similr
entry (4201) approximately every hour.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 02 00 50 00 ......P.
0008: 00 00 00 00 69 10 00 40 ....i..@
0010: 02 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

William B. Lurie wrote:
> Ken Blake, MVP wrote:
>> On Wed, 17 Mar 2010 10:56:40 -0400, "William B. Lurie"
>> <billurie(a)nospam.net> wrote:
>>
>>> I am one isolated desktop PC, hard- wired by Ethernet to my ISP via
>>> DSL. Am I a network?
>>
>>
>> Two answers to that question:
>>
>> 1. You are part of the network called the internet.
>>
>> 2. You are not part of any local network.
>>
>>
>>> Do I need a network adapter?
>>
>>
>>
>> You don't need more than you have, but you already have one. That's
>> what the ethernet cable from the DSL modem plugs into--either as part
>> of your motherboard or as a separate NIC (network interface card).
>>
>>
> Thanks, Ken. The reason for the specific query goes back
> to the fact that Tcpip error is what is identified in Events
> Monitor as what has been preventing my system from going
> to hibernate if I set hibernate time for greater than 1 hour.
>
> The Tcpip interface somehow gets repeated every hour and
> I asked (and got not response) to the question of how do I
> get that repeated automatic inquiry time lengthened. If it's
> always one hour, it would seem logical that somewhere it is
> *set* as 1 hour, and could be changed......

From: Ken Blake, MVP on 17 Mar 2010 19:22

On Wed, 17 Mar 2010 19:12:42 -0400, "William B. Lurie"
<billurie(a)nospam.net> wrote:

> Ken, here's a specific example of how Tcipp has
> prevented the system from going into hibernation.

Sorry, but I'll bow out of this thread. I know next to nothing about
hibernation.

--
Ken Blake, Microsoft MVP (Windows Desktop Experience) since 2003
Please Reply to the Newsgroup

From: William B. Lurie on 17 Mar 2010 20:07

Ken Blake, MVP wrote:
> On Wed, 17 Mar 2010 19:12:42 -0400, "William B. Lurie"
> <billurie(a)nospam.net> wrote:
>
>> Ken, here's a specific example of how Tcipp has
>> prevented the system from going into hibernation.
>
> Sorry, but I'll bow out of this thread. I know next to nothing about
> hibernation.
>
Okay, Ken. I understand.
But can somebody tell me where and how Tcpip gets initiated,
and whether there is an adjustment of every how often it
does its thing, since it has been established that Tcipp
is an 'event' that prevents hibernation from happening on
schedule.

A search for Tcipp led to a multitude of analysis in depth
and fixes for ills that are associated with it........but I
didn't see an answer to the above question.

From: William B. Lurie on 17 Mar 2010 20:42

Here's the sequence for the Tcpip events that occur every hour
(when the system is otherwise idle and would go to hibernation
after 2 hours).

3/17/2010 6:28:36 PM Tcpip Information None 4201 N/A COMPAQ-2006 The
system detected that network adapter
\DEVICE\TCPIP_{D5E50A75-4A1C-4421-A5B4-569C9FE131B8} was connected to
the network, and has initiated normal operation over the network adapter.
3/17/2010 5:27:18 PM Tcpip Information None 4201 N/A COMPAQ-2006 The
system detected that network adapter
\DEVICE\TCPIP_{D5E50A75-4A1C-4421-A5B4-569C9FE131B8} was connected to
the network, and has initiated normal operation over the network adapter.
3/17/2010 3:24:43 PM Tcpip Information None 4201 N/A COMPAQ-2006 The
system detected that network adapter
\DEVICE\TCPIP_{D5E50A75-4A1C-4421-A5B4-569C9FE131B8} was connected to
the network, and has initiated normal operation over the network adapter.

The system was left idle around 4:30 P.M.
At 5:27 the 'event' occurred, resetting the clock so that it
was headed for hibernation 2 hours later.

Then again, it would have gone to hibernate 2 hours after 5:27,
but instead, along came another 'event' at 6:28, resetting the clock again.

What I'm after is,how can we stretch out those initiations of normal
operation over the neywork? Or find out what is triggering the
initiation of normal operation over the network every hour?

From: William B. Lurie on 17 Mar 2010 22:05

First | Prev | Next | Last
Pages: 1 2 3 4
Prev: Outline format disappeared
Next: Loads of GREAT SOFTWARE ( 20,000 plus programs DVDS and CDs)