Hi,

We're trying to implement new power saving techniques. One of these is
having all PC's in our network shut down overnight. However, users
have a tendancy to leave unsaved documents open, so it seemed
hibernation mode was our saviour.

But, we're encountering major problems. When the PC's are brought out
of hibernation mode after a few hours (issue doesn't seem to occur if
PC's are left in hibernation for less than this), a number of errors
appear in the application log in event viewer relating to networking
issues (event ID 1054/15). These include problems relating to group
policy processing and contacting active directory. It seems the PC is
waking up before the NIC or something, but I can't figure out what's
going on. Things tried so far:

- Enabling 'portfast' on switch ports
- Upgrading NIC drivers
- Assigning a static IP address
- Disabling Windows XP fast logon
- Disabling the NIC setting 'allow the computer to turn off this
device to save power' in device manager
- Dropping NIC speed from 1gbps to 100mbps

None of this has made a difference and I'm completely out of ideas. I
can't believe I'm the only person experiencing this problem. Has
anyone else any suggestions?

Thanks.

"adamgill" <adamgilldo@hotmail.com> wrote in message
news:6c3a2c45-a525-49e6-93ea-fca4ab80f62a@k4g2000yqb.googlegroups.com...

Quote:

Hi, We're trying to implement new power saving techniques. One of these is having all PC's in our network shut down overnight. However, users have a tendancy to leave unsaved documents open, so it seemed hibernation mode was our saviour. But, we're encountering major problems. When the PC's are brought out of hibernation mode after a few hours (issue doesn't seem to occur if PC's are left in hibernation for less than this), a number of errors appear in the application log in event viewer relating to networking issues (event ID 1054/15). These include problems relating to group policy processing and contacting active directory. It seems the PC is waking up before the NIC or something, but I can't figure out what's going on. Things tried so far: - Enabling 'portfast' on switch ports - Upgrading NIC drivers - Assigning a static IP address - Disabling Windows XP fast logon - Disabling the NIC setting 'allow the computer to turn off this device to save power' in device manager - Dropping NIC speed from 1gbps to 100mbps None of this has made a difference and I'm completely out of ideas. I can't believe I'm the only person experiencing this problem. Has anyone else any suggestions? Thanks.

Did you try disabling the NIC prior to hibernating, then re-enabling when
coming back?

On 30 Oct, 13:10, "Pegasus [MVP]" <n...@microsoft.com> wrote:

Quote:

"adamgill" <adamgil...@hotmail.com> wrote in message news:6c3a2c45-a525-49e6-93ea-fca4ab80f62a@k4g2000yqb.googlegroups.com... Hi, We're trying to implement new power saving techniques. One of these is having all PC's in our network shut down overnight. However, users have a tendancy to leave unsaved documents open, so it seemed hibernation mode was our saviour. But, we're encountering major problems. When the PC's are brought out of hibernation mode after a few hours (issue doesn't seem to occur if PC's are left in hibernation for less than this), a number of errors appear in the application log in event viewer relating to networking issues (event ID 1054/15). These include problems relating to group policy processing and contacting active directory. It seems the PC is waking up before the NIC or something, but I can't figure out what's going on. Things tried so far: - Enabling 'portfast' on switch ports - Upgrading NIC drivers - Assigning a static IP address - Disabling Windows XP fast logon - Disabling the NIC setting 'allow the computer to turn off this device to save power' in device manager - Dropping NIC speed from 1gbps to 100mbps None of this has made a difference and I'm completely out of ideas. I can't believe I'm the only person experiencing this problem. Has anyone else any suggestions? Thanks. Did you try disabling the NIC prior to hibernating, then re-enabling when coming back?- Hide quoted text - - Show quoted text -

I haven't tried that yet, I assumed since the issue seemed to be that
Active Directory could not be contacted and group policies could not
run, it was because the NIC wasn't functioning at start up, so in
theory, I should get the same problems disabling the NIC. Will give it
a go tonight though and see what happens, thanks.

On 30 Oct, 13:47, adamgill <adamgil...@hotmail.com> wrote:

Quote:

On 30 Oct, 13:10, "Pegasus [MVP]" <n...@microsoft.com> wrote: "adamgill" <adamgil...@hotmail.com> wrote in message news:6c3a2c45-a525-49e6-93ea-fca4ab80f62a@k4g2000yqb.googlegroups.com... Hi, We're trying to implement new power saving techniques. One of these is having all PC's in our network shut down overnight. However, users have a tendancy to leave unsaved documents open, so it seemed hibernation mode was our saviour. But, we're encountering major problems. When the PC's are brought out of hibernation mode after a few hours (issue doesn't seem to occur if PC's are left in hibernation for less than this), a number of errors appear in the application log in event viewer relating to networking issues (event ID 1054/15). These include problems relating to group policy processing and contacting active directory. It seems the PC is waking up before the NIC or something, but I can't figure out what's going on. Things tried so far: - Enabling 'portfast' on switch ports - Upgrading NIC drivers - Assigning a static IP address - Disabling Windows XP fast logon - Disabling the NIC setting 'allow the computer to turn off this device to save power' in device manager - Dropping NIC speed from 1gbps to 100mbps None of this has made a difference and I'm completely out of ideas. I can't believe I'm the only person experiencing this problem. Has anyone else any suggestions? Thanks. Did you try disabling the NIC prior to hibernating, then re-enabling when coming back?- Hide quoted text - - Show quoted text - I haven't tried that yet, I assumed since the issue seemed to be that Active Directory could not be contacted and group policies could not run, it was because the NIC wasn't functioning at start up, so in theory, I should get the same problems disabling the NIC. Will give it a go tonight though and see what happens, thanks.- Hide quoted text - - Show quoted text -

Unfortunately this didn't make a difference and the same errors still
popped up in event log. Anyone else have any suggestions?

Thanks.

"adamgill" <adamgilldo@hotmail.com> wrote in message
news:805836c5-1991-45d7-98ac-a62d9c99f2ec@l13g2000yqb.googlegroups.com...

Quote:

On 2 Nov, 09:20, adamgill <adamgil...@hotmail.com> wrote: On 30 Oct, 13:47, adamgill <adamgil...@hotmail.com> wrote: On 30 Oct, 13:10, "Pegasus [MVP]" <n...@microsoft.com> wrote: "adamgill" <adamgil...@hotmail.com> wrote in message news:6c3a2c45-a525-49e6-93ea-fca4ab80f62a@k4g2000yqb.googlegroups.com... Hi, We're trying to implement new power saving techniques. One of these is having all PC's in our network shut down overnight. However, users have a tendancy to leave unsaved documents open, so it seemed hibernation mode was our saviour. But, we're encountering major problems. When the PC's are brought out of hibernation mode after a few hours (issue doesn't seem to occur if PC's are left in hibernation for less than this), a number of errors appear in the application log in event viewer relating to networking issues (event ID 1054/15). These include problems relating to group policy processing and contacting active directory. It seems the PC is waking up before the NIC or something, but I can't figure out what's going on. Things tried so far: - Enabling 'portfast' on switch ports - Upgrading NIC drivers - Assigning a static IP address - Disabling Windows XP fast logon - Disabling the NIC setting 'allow the computer to turn off this device to save power' in device manager - Dropping NIC speed from 1gbps to 100mbps None of this has made a difference and I'm completely out of ideas. I can't believe I'm the only person experiencing this problem. Has anyone else any suggestions? Thanks. Did you try disabling the NIC prior to hibernating, then re-enabling when coming back?- Hide quoted text - - Show quoted text - I haven't tried that yet, I assumed since the issue seemed to be that Active Directory could not be contacted and group policies could not run, it was because the NIC wasn't functioning at start up, so in theory, I should get the same problems disabling the NIC. Will give it a go tonight though and see what happens, thanks.- Hide quoted text - - Show quoted text - Unfortunately this didn't make a difference and the same errors still popped up in event log. Anyone else have any suggestions? Thanks.- Hide quoted text - - Show quoted text - For anyone interested, issue was resolved by adding the registry key stated in the article here: http://support.microsoft.com/kb/840669

Thanks for the feedback. Are you saying that you had not yet applied SP3?

On 2 Nov, 09:20, adamgill <adamgil...@hotmail.com> wrote:

Quote:

On 30 Oct, 13:47, adamgill <adamgil...@hotmail.com> wrote: On 30 Oct, 13:10, "Pegasus [MVP]" <n...@microsoft.com> wrote: "adamgill" <adamgil...@hotmail.com> wrote in message news:6c3a2c45-a525-49e6-93ea-fca4ab80f62a@k4g2000yqb.googlegroups.com... Hi, We're trying to implement new power saving techniques. One of these is having all PC's in our network shut down overnight. However, users have a tendancy to leave unsaved documents open, so it seemed hibernation mode was our saviour. But, we're encountering major problems. When the PC's are brought out of hibernation mode after a few hours (issue doesn't seem to occur if PC's are left in hibernation for less than this), a number of errors appear in the application log in event viewer relating to networking issues (event ID 1054/15). These include problems relating to group policy processing and contacting active directory. It seems the PC is waking up before the NIC or something, but I can't figure out what's going on. Things tried so far: - Enabling 'portfast' on switch ports - Upgrading NIC drivers - Assigning a static IP address - Disabling Windows XP fast logon - Disabling the NIC setting 'allow the computer to turn off this device to save power' in device manager - Dropping NIC speed from 1gbps to 100mbps None of this has made a difference and I'm completely out of ideas. I can't believe I'm the only person experiencing this problem. Has anyone else any suggestions? Thanks. Did you try disabling the NIC prior to hibernating, then re-enabling when coming back?- Hide quoted text - - Show quoted text - I haven't tried that yet, I assumed since the issue seemed to be that Active Directory could not be contacted and group policies could not run, it was because the NIC wasn't functioning at start up, so in theory, I should get the same problems disabling the NIC. Will give it a go tonight though and see what happens, thanks.- Hide quoted text - - Show quoted text - Unfortunately this didn't make a difference and the same errors still popped up in event log. Anyone else have any suggestions? Thanks.- Hide quoted text - - Show quoted text -

For anyone interested, issue was resolved by adding the registry key
stated in the article here: http://support.microsoft.com/kb/840669