If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
What is Tcpip?
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? |
Ads |
Thread Tools | |
Display Modes | |
|
|