Network Errors when coming out of hibernation mode

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" wrote in message
...
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]" wrote:
"adamgill" wrote in message

...





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 wrote:
On 30 Oct, 13:10, "Pegasus [MVP]" wrote:





"adamgill" wrote in message

...

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.

On 2 Nov, 09:20, adamgill wrote:
On 30 Oct, 13:47, adamgill wrote:





On 30 Oct, 13:10, "Pegasus [MVP]" wrote:

"adamgill" wrote in message

...

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 he http://support.microsoft.com/kb/840669

"adamgill" wrote in message
...
On 2 Nov, 09:20, adamgill wrote:
On 30 Oct, 13:47, adamgill wrote:





On 30 Oct, 13:10, "Pegasus [MVP]" wrote:

"adamgill" wrote in message

...

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 he http://support.microsoft.com/kb/840669

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

On Nov 4, 11:02*am, "Pegasus [MVP]" wrote:
"adamgill" wrote in message

...





On 2 Nov, 09:20, adamgill wrote:
On 30 Oct, 13:47, adamgill wrote:

On 30 Oct, 13:10, "Pegasus [MVP]" wrote:

"adamgill" wrote in message

...

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 hehttp://support.microsoft.com/kb/840669

Thanks for the feedback. Are you saying that you had not yet applied SP3?- Hide quoted text -

- Show quoted text -

Looks like I spoke too soon. For whatever reason, it begun working
fine for a few days, however, the same issue is now occuring.

I have SP3 by the way.

Here's a snippet from my userenv.log file if anyone has any ideas:

USERENV(2f0.894) 09:05:37:312 ProcessGPOs:
USERENV(2f0.894) 09:05:37:953 ProcessGPOs:
USERENV(2f0.894) 09:05:37:953 ProcessGPOs: Starting computer Group
Policy (Background) processing...
USERENV(2f0.894) 09:05:37:984 ProcessGPOs:
USERENV(2f0.894) 09:05:37:984 ProcessGPOs:
USERENV(2f0.894) 09:05:38:484 EnterCriticalPolicySectionEx: Entering
with timeout 600000 and flags 0x0
USERENV(2f0.894) 09:05:38:750 EnterCriticalPolicySectionEx: Machine
critical section has been claimed. Handle = 0x9b0
USERENV(2f0.894) 09:05:38:750 EnterCriticalPolicySectionEx: Leaving
successfully.
USERENV(2f0.8f8) 09:05:38:812 EnterCriticalPolicySectionEx: Entering
with timeout 600000 and flags 0x0
USERENV(2f0.894) 09:05:39:703 ProcessGPOs: Machine role is 2.
USERENV(2f0.8f8) 09:05:39:953 EnterCriticalPolicySectionEx: User
critical section has been claimed. Handle = 0x940
USERENV(2f0.8f8) 09:05:40:000 EnterCriticalPolicySectionEx: Leaving
successfully.
USERENV(2f0.8f8) 09:05:40:765 ProcessGPOs: Machine role is 2.
USERENV(2f0.8f8) 09:05:41:561 IsSlowLink: Slow link transfer rate is
0. Always download policy.
USERENV(2f0.894) 09:05:42:153 ProcessGPOs: network name is domain
USERENV(2f0.894) 09:05:44:925 MyGetUserName: GetUserNameEx failed
with 1722.
USERENV(2f0.8f8) 09:05:45:034 MyGetUserName: GetUserNameEx failed
with 1722.
USERENV(2f0.8f8) 09:05:45:315 MyGetUserName: Retrying call to
GetUserNameEx in 1/2 second.
USERENV(2f0.8f8) 09:05:46:047 MyGetUserName: GetUserNameEx failed
with 1722.
USERENV(2f0.894) 09:05:45:907 MyGetUserName: GetUserNameEx failed
with 1722.
USERENV(2f0.894) 09:05:46:577 MyGetUserName: Retrying call to
GetUserNameEx in 1/2 second.
USERENV(2f0.894) 09:05:47:200 MyGetUserName: GetUserNameEx failed
with 1722.
USERENV(2f0.894) 09:05:47:371 MyGetUserName: Retrying call to
GetUserNameEx in 1/2 second.
USERENV(2f0.8f8) 09:05:47:278 MyGetUserName: Retrying call to
GetUserNameEx in 1/2 second.
USERENV(2f0.894) 09:05:48:072 MyGetUserName: GetUserNameEx failed
with 1722.
USERENV(2f0.894) 09:05:49:085 ProcessGPOs: MyGetUserName failed with
1722.