WIRELESS network adapter FAILURE on Vista ONLY AFTER SLEEP

1. My network has ALWAYS failed upon RESUME FROM SLEEP using a WIRELESS
connection via a NETGEAR WN121T wireless-N USB 2.0 adapter, but NOT when
using a wired Ethernet connection.
2. It also works perfectly from BOOT via the WN121T wireless connection with
my NETGEAR DG834N draft 802.11n (and another 802.11g) wireless modem/router
on Windows Vista Ultimate, both with and without the SP1 Release Candidate.
3. But upon resumption from SLEEP, the wireless n/w connection has ALWAYS
failed: attempting to re-connect to the network fails, and Device Manager
reports for the WN121T that “Windows has stopped this device because it has
reported problems (code 43)�.
4. The only remedy is to REBOOT.
5. The consequences of this are twofold:
- firstly, Microsoft-recommended sleep mode is consequently irrelevant
as a
reboot is necessary anyway to re-establish the wireless connection,
- secondly, as no wireless connection appears to be maintained during
sleep,
Windows Update, backup and other important maintenance via n/w cannot be
scheduled during sleep.
6. The RELEVANT Vista system settings & status are:
- ReadyBoost: active with 1860MB
- WN121T power setting: “Allow the computer to turn off this device
to save
power� is unchecked (i.e. blank)
- Power plan:
- wireless adapter: “maximum performance�
- allow hybrid sleep: “on�
- hibernate: “never�
- WN121T Drivers: always latest (fails with both Microsoft
& NETGEAR).
7. (NON-RELEVANT factors would appear to include that the motherboard has no
disks directly attached (the 1TB of RAID10 disk storage is provided via an
OEM h/w upgrade to an LSI 8308ELP MegaRAID board), as the failure also
occurred prior to this upgrade – albeit prior to SP1 and with the drivers
then available in July 2007.)
8. It seems clear that this issue is either a GENERAL FAILURE IN MICROSOFT
SLEEP FUNCTIONALITY FOR USB 2.0 WIRELESS NETWORKS, or a SPECIFIC ISSUE IN THE
NETGEAR WN121T DRIVER NOT ACCOMMODATING THE MICROSOFT SLEEP FUNCTIONALITY.
Either way, it would seem a NETGEAR DRIVER v MICROSOFT SLEEP issue.
9. This issue has been repeatedly reported to Microsoft for some 6 months
via Problems & Solutions and more recently via the SP1 Release Candidate
reporting facility, without resolution.
10. CAN YOU HELP?
- Have you experienced ANY wireless adapter failures ONLY AFTER
SLEEP on
VISTA (regardless of adapter)?
- Have you experienced ANY NETGEAR WN121T wireless adapter failures
ONLY AFTER SLEEP on VISTA?
- If so, have you reported them, to whom & with what response?
- Do you know of any remedies?
--
Vultch

"Vulture" wrote:

> 1. My network has ALWAYS failed upon RESUME FROM SLEEP using a WIRELESS
> connection via a NETGEAR WN121T wireless-N USB 2.0 adapter, but NOT when
> using a wired Ethernet connection.
> 2. It also works perfectly from BOOT via the WN121T wireless connection with
> my NETGEAR DG834N draft 802.11n (and another 802.11g) wireless modem/router
> on Windows Vista Ultimate, both with and without the SP1 Release Candidate.
> 3. But upon resumption from SLEEP, the wireless n/w connection has ALWAYS
> failed: attempting to re-connect to the network fails, and Device Manager
> reports for the WN121T that “Windows has stopped this device because it has
> reported problems (code 43)�.
> 4. The only remedy is to REBOOT.
> 5. The consequences of this are twofold:
> - firstly, Microsoft-recommended sleep mode is consequently irrelevant
> as a
> reboot is necessary anyway to re-establish the wireless connection,
> - secondly, as no wireless connection appears to be maintained during
> sleep,
> Windows Update, backup and other important maintenance via n/w cannot be
> scheduled during sleep.
> 6. The RELEVANT Vista system settings & status are:
> - ReadyBoost: active with 1860MB
> - WN121T power setting: “Allow the computer to turn off this device
> to save
> power� is unchecked (i.e. blank)
> - Power plan:
> - wireless adapter: “maximum performance�
> - allow hybrid sleep: “on�
> - hibernate: “never�
> - WN121T Drivers: always latest (fails with both Microsoft
> & NETGEAR).
> 7. (NON-RELEVANT factors would appear to include that the motherboard has no
> disks directly attached (the 1TB of RAID10 disk storage is provided via an
> OEM h/w upgrade to an LSI 8308ELP MegaRAID board), as the failure also
> occurred prior to this upgrade – albeit prior to SP1 and with the drivers
> then available in July 2007.)
> 8. It seems clear that this issue is either a GENERAL FAILURE IN MICROSOFT
> SLEEP FUNCTIONALITY FOR USB 2.0 WIRELESS NETWORKS, or a SPECIFIC ISSUE IN THE
> NETGEAR WN121T DRIVER NOT ACCOMMODATING THE MICROSOFT SLEEP FUNCTIONALITY.
> Either way, it would seem a NETGEAR DRIVER v MICROSOFT SLEEP issue.
> 9. This issue has been repeatedly reported to Microsoft for some 6 months
> via Problems & Solutions and more recently via the SP1 Release Candidate
> reporting facility, without resolution.
> 10. CAN YOU HELP?
> - Have you experienced ANY wireless adapter failures ONLY AFTER
> SLEEP on
> VISTA (regardless of adapter)?
> - Have you experienced ANY NETGEAR WN121T wireless adapter failures
> ONLY AFTER SLEEP on VISTA?
> - If so, have you reported them, to whom & with what response?
> - Do you know of any remedies?
> --
> Vultch

Many vista user have been experiening promblems with just more than wirless
adapters when resuming from sleep. Microsoft really messed up with the
hibernation part of vista, but they are supposed to fix it with service pack
1. If you dont mind leaving your pc running I would recommend that you turn
of sleep on your computer, that is if it is a desktop, until SP1 comes out. I
to have had problem with USB flash drive, my Motorola wireless adapter, my
printer and so on when resuming from sleep so i just turned it off and life
has been much easier.

Thanks skirwin.
1. I note your observation regarding Microsoft's implementation of
sleep/hibernate on Vista which is well-supported by the number of KB articles
on such topics on their support website. BUT, - don't hold your breath about
all of these problems being fixed in SP1: - I am already running on the SP1
Release Candidate (see my point 2). Although I had already applied all
updates/hotfixes which seemed possibly-relevant, I upgraded to the SP1 RC,
firstly in case I'd missed some, and secondly so that they were all tested as
a coherent whole.
2. Yet the problem persists !
3. As the final SP1 is to be released in some 2-6 weeks, I can only HOPE
that this issue will be resolved in time.
4. Your comment re preventing the computer from sleeping is noted, and I had
already created such a Power plan to facilitate unattended Windows Update,
One-Care Safety Scanner (sleep does not occur until the scan is complete, but
the results and subsequent actions are then unavailable as the wireless
network connection is lost during sleep, thus necessitating a lengthy
re-scan), backups etc.
5. However, leaving a computer running 24 hours/day as a workaround to
losing a wireless network connection during sleep is hardly professional -
especially as Microsoft actively promotes SLEEP with all it's inherent
advantages as it's recommended state in which to leave an unattended computer
at "power-off" !
6. I have been considering purchase of the new MICROSOFT WINDOWS HOME SERVER
which seems an excellent product to satisfy many of my system requirements.
Such purchase is however quite pointless unless this sleep/wireless issue is
first resolved.
7. I have always liked Microsoft products despite the many criticisms from
others over the years, I like Vista, and I welcome the increased stability of
SP1 (RC). As such a fan, I have 2 recommendations for Microsoft:
- Don't further delay the final release of SP1, DO try to include
resolutions to outstanding issues, BUT NOT at the expense of thorough
testing. The increased stability & performance of the SP1 RC is welcome.
- Perhaps more importantly, resolve SLEEP NETWORK issues once and for all -
even if it requires a fundamental re-think, and issue an SP2 resolving such
issues ASAP.
8. FINAL COMMENT TO MICROSOFT:
- SLEEP functionality is fundamental to VISTA.
- NETWORK functionality is fundamental to WINDOWS HOME SERVER.
- Most networked HOME USERS have a WIRELESS network.
- The success of VISTA/HOME SERVER thus depends upon resolving this issue.
- Contemplate the consequences of NOT resolving this issue.
--
Vultch


"skirwin" wrote:

>
>
> "Vulture" wrote:
>
> > 1. My network has ALWAYS failed upon RESUME FROM SLEEP using a WIRELESS
> > connection via a NETGEAR WN121T wireless-N USB 2.0 adapter, but NOT when
> > using a wired Ethernet connection.
> > 2. It also works perfectly from BOOT via the WN121T wireless connection with
> > my NETGEAR DG834N draft 802.11n (and another 802.11g) wireless modem/router
> > on Windows Vista Ultimate, both with and without the SP1 Release Candidate.
> > 3. But upon resumption from SLEEP, the wireless n/w connection has ALWAYS
> > failed: attempting to re-connect to the network fails, and Device Manager
> > reports for the WN121T that “Windows has stopped this device because it has
> > reported problems (code 43)�.
> > 4. The only remedy is to REBOOT.
> > 5. The consequences of this are twofold:
> > - firstly, Microsoft-recommended sleep mode is consequently irrelevant
> > as a
> > reboot is necessary anyway to re-establish the wireless connection,
> > - secondly, as no wireless connection appears to be maintained during
> > sleep,
> > Windows Update, backup and other important maintenance via n/w cannot be
> > scheduled during sleep.
> > 6. The RELEVANT Vista system settings & status are:
> > - ReadyBoost: active with 1860MB
> > - WN121T power setting: “Allow the computer to turn off this device
> > to save
> > power� is unchecked (i.e. blank)
> > - Power plan:
> > - wireless adapter: “maximum performance�
> > - allow hybrid sleep: “on�
> > - hibernate: “never�
> > - WN121T Drivers: always latest (fails with both Microsoft
> > & NETGEAR).
> > 7. (NON-RELEVANT factors would appear to include that the motherboard has no
> > disks directly attached (the 1TB of RAID10 disk storage is provided via an
> > OEM h/w upgrade to an LSI 8308ELP MegaRAID board), as the failure also
> > occurred prior to this upgrade – albeit prior to SP1 and with the drivers
> > then available in July 2007.)
> > 8. It seems clear that this issue is either a GENERAL FAILURE IN MICROSOFT
> > SLEEP FUNCTIONALITY FOR USB 2.0 WIRELESS NETWORKS, or a SPECIFIC ISSUE IN THE
> > NETGEAR WN121T DRIVER NOT ACCOMMODATING THE MICROSOFT SLEEP FUNCTIONALITY.
> > Either way, it would seem a NETGEAR DRIVER v MICROSOFT SLEEP issue.
> > 9. This issue has been repeatedly reported to Microsoft for some 6 months
> > via Problems & Solutions and more recently via the SP1 Release Candidate
> > reporting facility, without resolution.
> > 10. CAN YOU HELP?
> > - Have you experienced ANY wireless adapter failures ONLY AFTER
> > SLEEP on
> > VISTA (regardless of adapter)?
> > - Have you experienced ANY NETGEAR WN121T wireless adapter failures
> > ONLY AFTER SLEEP on VISTA?
> > - If so, have you reported them, to whom & with what response?
> > - Do you know of any remedies?
> > --
> > Vultch
>
> Many vista user have been experiening promblems with just more than wirless
> adapters when resuming from sleep. Microsoft really messed up with the
> hibernation part of vista, but they are supposed to fix it with service pack
> 1. If you dont mind leaving your pc running I would recommend that you turn
> of sleep on your computer, that is if it is a desktop, until SP1 comes out. I
> to have had problem with USB flash drive, my Motorola wireless adapter, my
> printer and so on when resuming from sleep so i just turned it off and life
> has been much easier.

I did a Google search for

NETGEAR WN121T +vista +sleep

and it turned up lots and lots of pages like
http://www.vidrate.com/product/c009/...B000IT5WY2.htm

"The only issue I have had with it is that if I set my machine on
Sleep mode the Rangemax seems to disconnect so that when I wake the
machine it has issues. The quickest way to get reconnected seems to
be restarting the machine (but since it saves power to shut down
rather than sleep the PC, no big deal)."

so it would appear this is an issue with this adapter.

On Sat, 16 Feb 2008 06:18:00 -0800, Vulture
<> wrote:

>Thanks skirwin.
>1. I note your observation regarding Microsoft's implementation of
>sleep/hibernate on Vista which is well-supported by the number of KB articles
>on such topics on their support website. BUT, - don't hold your breath about
>all of these problems being fixed in SP1: - I am already running on the SP1
>Release Candidate (see my point 2). Although I had already applied all
>updates/hotfixes which seemed possibly-relevant, I upgraded to the SP1 RC,
>firstly in case I'd missed some, and secondly so that they were all tested as
>a coherent whole.
>2. Yet the problem persists !
>3. As the final SP1 is to be released in some 2-6 weeks, I can only HOPE
>that this issue will be resolved in time.
>4. Your comment re preventing the computer from sleeping is noted, and I had
>already created such a Power plan to facilitate unattended Windows Update,
>One-Care Safety Scanner (sleep does not occur until the scan is complete, but
>the results and subsequent actions are then unavailable as the wireless
>network connection is lost during sleep, thus necessitating a lengthy
>re-scan), backups etc.
>5. However, leaving a computer running 24 hours/day as a workaround to
>losing a wireless network connection during sleep is hardly professional -
>especially as Microsoft actively promotes SLEEP with all it's inherent
>advantages as it's recommended state in which to leave an unattended computer
>at "power-off" !
>6. I have been considering purchase of the new MICROSOFT WINDOWS HOME SERVER
>which seems an excellent product to satisfy many of my system requirements.
>Such purchase is however quite pointless unless this sleep/wireless issue is
>first resolved.
>7. I have always liked Microsoft products despite the many criticisms from
>others over the years, I like Vista, and I welcome the increased stability of
>SP1 (RC). As such a fan, I have 2 recommendations for Microsoft:
>- Don't further delay the final release of SP1, DO try to include
>resolutions to outstanding issues, BUT NOT at the expense of thorough
>testing. The increased stability & performance of the SP1 RC is welcome.
>- Perhaps more importantly, resolve SLEEP NETWORK issues once and for all -
>even if it requires a fundamental re-think, and issue an SP2 resolving such
>issues ASAP.
>8. FINAL COMMENT TO MICROSOFT:
>- SLEEP functionality is fundamental to VISTA.
>- NETWORK functionality is fundamental to WINDOWS HOME SERVER.
>- Most networked HOME USERS have a WIRELESS network.
>- The success of VISTA/HOME SERVER thus depends upon resolving this issue.
>- Contemplate the consequences of NOT resolving this issue.
--

Barb Bowman
MS-MVP
http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

When you come out of sleep mode or whatever it is that breaks your wireless
connectivity, go to services (start, run, services.msc) and find "wireless
zero config". Right-click it and then click "restart". See if that works.

JJ

"Barb Bowman" wrote:

> I did a Google search for
>
> NETGEAR WN121T +vista +sleep
>
> and it turned up lots and lots of pages like
> http://www.vidrate.com/product/c009/...B000IT5WY2.htm
>
> "The only issue I have had with it is that if I set my machine on
> Sleep mode the Rangemax seems to disconnect so that when I wake the
> machine it has issues. The quickest way to get reconnected seems to
> be restarting the machine (but since it saves power to shut down
> rather than sleep the PC, no big deal)."
>
> so it would appear this is an issue with this adapter.
>
> On Sat, 16 Feb 2008 06:18:00 -0800, Vulture
> <> wrote:
>
> >Thanks skirwin.
> >1. I note your observation regarding Microsoft's implementation of
> >sleep/hibernate on Vista which is well-supported by the number of KB articles
> >on such topics on their support website. BUT, - don't hold your breath about
> >all of these problems being fixed in SP1: - I am already running on the SP1
> >Release Candidate (see my point 2). Although I had already applied all
> >updates/hotfixes which seemed possibly-relevant, I upgraded to the SP1 RC,
> >firstly in case I'd missed some, and secondly so that they were all tested as
> >a coherent whole.
> >2. Yet the problem persists !
> >3. As the final SP1 is to be released in some 2-6 weeks, I can only HOPE
> >that this issue will be resolved in time.
> >4. Your comment re preventing the computer from sleeping is noted, and I had
> >already created such a Power plan to facilitate unattended Windows Update,
> >One-Care Safety Scanner (sleep does not occur until the scan is complete, but
> >the results and subsequent actions are then unavailable as the wireless
> >network connection is lost during sleep, thus necessitating a lengthy
> >re-scan), backups etc.
> >5. However, leaving a computer running 24 hours/day as a workaround to
> >losing a wireless network connection during sleep is hardly professional -
> >especially as Microsoft actively promotes SLEEP with all it's inherent
> >advantages as it's recommended state in which to leave an unattended computer
> >at "power-off" !
> >6. I have been considering purchase of the new MICROSOFT WINDOWS HOME SERVER
> >which seems an excellent product to satisfy many of my system requirements.
> >Such purchase is however quite pointless unless this sleep/wireless issue is
> >first resolved.
> >7. I have always liked Microsoft products despite the many criticisms from
> >others over the years, I like Vista, and I welcome the increased stability of
> >SP1 (RC). As such a fan, I have 2 recommendations for Microsoft:
> >- Don't further delay the final release of SP1, DO try to include
> >resolutions to outstanding issues, BUT NOT at the expense of thorough
> >testing. The increased stability & performance of the SP1 RC is welcome.
> >- Perhaps more importantly, resolve SLEEP NETWORK issues once and for all -
> >even if it requires a fundamental re-think, and issue an SP2 resolving such
> >issues ASAP.
> >8. FINAL COMMENT TO MICROSOFT:
> >- SLEEP functionality is fundamental to VISTA.
> >- NETWORK functionality is fundamental to WINDOWS HOME SERVER.
> >- Most networked HOME USERS have a WIRELESS network.
> >- The success of VISTA/HOME SERVER thus depends upon resolving this issue.
> >- Contemplate the consequences of NOT resolving this issue.
> --
>
> Barb Bowman
> MS-MVP
> http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
> http://blogs.digitalmediaphile.com/barb/
>

Dear, O dearest Barb, your reply pointed me in the right direction and -
guess what
- the issue appears solved! In order to determine if the problem was a
specific NETGEAR WN121T DRIVER issue or a more general MICROSOFT WIRELESS
NETWORK ADAPTERS issue, I did a google search on "wireless adaptors + vista +
sleep" which yielded
"http://www.vistax64.com/tutorials/63567-power-options-sleep-mode-problems.html".
Entitled "Vistax64.com (Forums)", it goes on to state that the forum is for
both x64 & x86 systems, and although dated 15 May 2007, this is clearly still
a highly-relevant document which covers "Vista Sleep issues" so
comprehensively that I am most surprised it is not present on the Vista KB
under such an index/tag entry. The CRITICAL point re the WN121T (and maybe
other) wireless adapter failures AFTER SLEEP would appear to be the advanced
POWER SAVINGS PLAN options (Control Panel/Power Options/(plan)/Change
Advanced Power Options) WHICH ALSO AFFECT the "soft Power Button (sleep) on
the Start Menu. I use "hybrid sleep" for the obvious advantages, and changed
"hibernate" to be as recommended in this document (instead of "NEVER"). These
are early days, but I anticipate the issue is resolved.
Thanks again, Barb, from Vutch (x86 - but only 64 in the UK!)



"Barb Bowman" wrote:

> I did a Google search for
>
> NETGEAR WN121T +vista +sleep
>
> and it turned up lots and lots of pages like
> http://www.vidrate.com/product/c009/...B000IT5WY2.htm
>
> "The only issue I have had with it is that if I set my machine on
> Sleep mode the Rangemax seems to disconnect so that when I wake the
> machine it has issues. The quickest way to get reconnected seems to
> be restarting the machine (but since it saves power to shut down
> rather than sleep the PC, no big deal)."
>
> so it would appear this is an issue with this adapter.
>
> On Sat, 16 Feb 2008 06:18:00 -0800, Vulture
> <> wrote:
>
> >Thanks skirwin.
> >1. I note your observation regarding Microsoft's implementation of
> >sleep/hibernate on Vista which is well-supported by the number of KB articles
> >on such topics on their support website. BUT, - don't hold your breath about
> >all of these problems being fixed in SP1: - I am already running on the SP1
> >Release Candidate (see my point 2). Although I had already applied all
> >updates/hotfixes which seemed possibly-relevant, I upgraded to the SP1 RC,
> >firstly in case I'd missed some, and secondly so that they were all tested as
> >a coherent whole.
> >2. Yet the problem persists !
> >3. As the final SP1 is to be released in some 2-6 weeks, I can only HOPE
> >that this issue will be resolved in time.
> >4. Your comment re preventing the computer from sleeping is noted, and I had
> >already created such a Power plan to facilitate unattended Windows Update,
> >One-Care Safety Scanner (sleep does not occur until the scan is complete, but
> >the results and subsequent actions are then unavailable as the wireless
> >network connection is lost during sleep, thus necessitating a lengthy
> >re-scan), backups etc.
> >5. However, leaving a computer running 24 hours/day as a workaround to
> >losing a wireless network connection during sleep is hardly professional -
> >especially as Microsoft actively promotes SLEEP with all it's inherent
> >advantages as it's recommended state in which to leave an unattended computer
> >at "power-off" !
> >6. I have been considering purchase of the new MICROSOFT WINDOWS HOME SERVER
> >which seems an excellent product to satisfy many of my system requirements.
> >Such purchase is however quite pointless unless this sleep/wireless issue is
> >first resolved.
> >7. I have always liked Microsoft products despite the many criticisms from
> >others over the years, I like Vista, and I welcome the increased stability of
> >SP1 (RC). As such a fan, I have 2 recommendations for Microsoft:
> >- Don't further delay the final release of SP1, DO try to include
> >resolutions to outstanding issues, BUT NOT at the expense of thorough
> >testing. The increased stability & performance of the SP1 RC is welcome.
> >- Perhaps more importantly, resolve SLEEP NETWORK issues once and for all -
> >even if it requires a fundamental re-think, and issue an SP2 resolving such
> >issues ASAP.
> >8. FINAL COMMENT TO MICROSOFT:
> >- SLEEP functionality is fundamental to VISTA.
> >- NETWORK functionality is fundamental to WINDOWS HOME SERVER.
> >- Most networked HOME USERS have a WIRELESS network.
> >- The success of VISTA/HOME SERVER thus depends upon resolving this issue.
> >- Contemplate the consequences of NOT resolving this issue.
> --
>
> Barb Bowman
> MS-MVP
> http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
> http://blogs.digitalmediaphile.com/barb/
>

Thanks Skirwin, Barb & Snacko 4 ur help. I believe the issue has now been
resolved to our mutual advantage, but do respond if u experience further
problems on this issue.

--
Vultch


"Snacko" wrote:

> When you come out of sleep mode or whatever it is that breaks your wireless
> connectivity, go to services (start, run, services.msc) and find "wireless
> zero config". Right-click it and then click "restart". See if that works.
>
> JJ
>
> "Barb Bowman" wrote:
>
> > I did a Google search for
> >
> > NETGEAR WN121T +vista +sleep
> >
> > and it turned up lots and lots of pages like
> > http://www.vidrate.com/product/c009/...B000IT5WY2.htm
> >
> > "The only issue I have had with it is that if I set my machine on
> > Sleep mode the Rangemax seems to disconnect so that when I wake the
> > machine it has issues. The quickest way to get reconnected seems to
> > be restarting the machine (but since it saves power to shut down
> > rather than sleep the PC, no big deal)."
> >
> > so it would appear this is an issue with this adapter.
> >
> > On Sat, 16 Feb 2008 06:18:00 -0800, Vulture
> > <> wrote:
> >
> > >Thanks skirwin.
> > >1. I note your observation regarding Microsoft's implementation of
> > >sleep/hibernate on Vista which is well-supported by the number of KB articles
> > >on such topics on their support website. BUT, - don't hold your breath about
> > >all of these problems being fixed in SP1: - I am already running on the SP1
> > >Release Candidate (see my point 2). Although I had already applied all
> > >updates/hotfixes which seemed possibly-relevant, I upgraded to the SP1 RC,
> > >firstly in case I'd missed some, and secondly so that they were all tested as
> > >a coherent whole.
> > >2. Yet the problem persists !
> > >3. As the final SP1 is to be released in some 2-6 weeks, I can only HOPE
> > >that this issue will be resolved in time.
> > >4. Your comment re preventing the computer from sleeping is noted, and I had
> > >already created such a Power plan to facilitate unattended Windows Update,
> > >One-Care Safety Scanner (sleep does not occur until the scan is complete, but
> > >the results and subsequent actions are then unavailable as the wireless
> > >network connection is lost during sleep, thus necessitating a lengthy
> > >re-scan), backups etc.
> > >5. However, leaving a computer running 24 hours/day as a workaround to
> > >losing a wireless network connection during sleep is hardly professional -
> > >especially as Microsoft actively promotes SLEEP with all it's inherent
> > >advantages as it's recommended state in which to leave an unattended computer
> > >at "power-off" !
> > >6. I have been considering purchase of the new MICROSOFT WINDOWS HOME SERVER
> > >which seems an excellent product to satisfy many of my system requirements.
> > >Such purchase is however quite pointless unless this sleep/wireless issue is
> > >first resolved.
> > >7. I have always liked Microsoft products despite the many criticisms from
> > >others over the years, I like Vista, and I welcome the increased stability of
> > >SP1 (RC). As such a fan, I have 2 recommendations for Microsoft:
> > >- Don't further delay the final release of SP1, DO try to include
> > >resolutions to outstanding issues, BUT NOT at the expense of thorough
> > >testing. The increased stability & performance of the SP1 RC is welcome.
> > >- Perhaps more importantly, resolve SLEEP NETWORK issues once and for all -
> > >even if it requires a fundamental re-think, and issue an SP2 resolving such
> > >issues ASAP.
> > >8. FINAL COMMENT TO MICROSOFT:
> > >- SLEEP functionality is fundamental to VISTA.
> > >- NETWORK functionality is fundamental to WINDOWS HOME SERVER.
> > >- Most networked HOME USERS have a WIRELESS network.
> > >- The success of VISTA/HOME SERVER thus depends upon resolving this issue.
> > >- Contemplate the consequences of NOT resolving this issue.
> > --
> >
> > Barb Bowman
> > MS-MVP
> > http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
> > http://blogs.digitalmediaphile.com/barb/
> >

thanks for the update

On Mon, 18 Feb 2008 11:03:01 -0800, Vulture
<> wrote:

>Dear, O dearest Barb, your reply pointed me in the right direction and -
>guess what
> - the issue appears solved! In order to determine if the problem was a
>specific NETGEAR WN121T DRIVER issue or a more general MICROSOFT WIRELESS
>NETWORK ADAPTERS issue, I did a google search on "wireless adaptors + vista +
>sleep" which yielded
>"http://www.vistax64.com/tutorials/63567-power-options-sleep-mode-problems.html".
>Entitled "Vistax64.com (Forums)", it goes on to state that the forum is for
>both x64 & x86 systems, and although dated 15 May 2007, this is clearly still
>a highly-relevant document which covers "Vista Sleep issues" so
>comprehensively that I am most surprised it is not present on the Vista KB
>under such an index/tag entry. The CRITICAL point re the WN121T (and maybe
>other) wireless adapter failures AFTER SLEEP would appear to be the advanced
>POWER SAVINGS PLAN options (Control Panel/Power Options/(plan)/Change
>Advanced Power Options) WHICH ALSO AFFECT the "soft Power Button (sleep) on
>the Start Menu. I use "hybrid sleep" for the obvious advantages, and changed
>"hibernate" to be as recommended in this document (instead of "NEVER"). These
>are early days, but I anticipate the issue is resolved.
>Thanks again, Barb, from Vutch (x86 - but only 64 in the UK!)
>
>
>
>"Barb Bowman" wrote:
>
>> I did a Google search for
>>
>> NETGEAR WN121T +vista +sleep
>>
>> and it turned up lots and lots of pages like
>> http://www.vidrate.com/product/c009/...B000IT5WY2.htm
>>
>> "The only issue I have had with it is that if I set my machine on
>> Sleep mode the Rangemax seems to disconnect so that when I wake the
>> machine it has issues. The quickest way to get reconnected seems to
>> be restarting the machine (but since it saves power to shut down
>> rather than sleep the PC, no big deal)."
>>
>> so it would appear this is an issue with this adapter.
>>
>> On Sat, 16 Feb 2008 06:18:00 -0800, Vulture
>> <> wrote:
>>
>> >Thanks skirwin.
>> >1. I note your observation regarding Microsoft's implementation of
>> >sleep/hibernate on Vista which is well-supported by the number of KB articles
>> >on such topics on their support website. BUT, - don't hold your breath about
>> >all of these problems being fixed in SP1: - I am already running on the SP1
>> >Release Candidate (see my point 2). Although I had already applied all
>> >updates/hotfixes which seemed possibly-relevant, I upgraded to the SP1 RC,
>> >firstly in case I'd missed some, and secondly so that they were all tested as
>> >a coherent whole.
>> >2. Yet the problem persists !
>> >3. As the final SP1 is to be released in some 2-6 weeks, I can only HOPE
>> >that this issue will be resolved in time.
>> >4. Your comment re preventing the computer from sleeping is noted, and I had
>> >already created such a Power plan to facilitate unattended Windows Update,
>> >One-Care Safety Scanner (sleep does not occur until the scan is complete, but
>> >the results and subsequent actions are then unavailable as the wireless
>> >network connection is lost during sleep, thus necessitating a lengthy
>> >re-scan), backups etc.
>> >5. However, leaving a computer running 24 hours/day as a workaround to
>> >losing a wireless network connection during sleep is hardly professional -
>> >especially as Microsoft actively promotes SLEEP with all it's inherent
>> >advantages as it's recommended state in which to leave an unattended computer
>> >at "power-off" !
>> >6. I have been considering purchase of the new MICROSOFT WINDOWS HOME SERVER
>> >which seems an excellent product to satisfy many of my system requirements.
>> >Such purchase is however quite pointless unless this sleep/wireless issue is
>> >first resolved.
>> >7. I have always liked Microsoft products despite the many criticisms from
>> >others over the years, I like Vista, and I welcome the increased stability of
>> >SP1 (RC). As such a fan, I have 2 recommendations for Microsoft:
>> >- Don't further delay the final release of SP1, DO try to include
>> >resolutions to outstanding issues, BUT NOT at the expense of thorough
>> >testing. The increased stability & performance of the SP1 RC is welcome.
>> >- Perhaps more importantly, resolve SLEEP NETWORK issues once and for all -
>> >even if it requires a fundamental re-think, and issue an SP2 resolving such
>> >issues ASAP.
>> >8. FINAL COMMENT TO MICROSOFT:
>> >- SLEEP functionality is fundamental to VISTA.
>> >- NETWORK functionality is fundamental to WINDOWS HOME SERVER.
>> >- Most networked HOME USERS have a WIRELESS network.
>> >- The success of VISTA/HOME SERVER thus depends upon resolving this issue.
>> >- Contemplate the consequences of NOT resolving this issue.
>> --
>>
>> Barb Bowman
>> MS-MVP
>> http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
>> http://blogs.digitalmediaphile.com/barb/
>>
--

Barb Bowman
MS-MVP
http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

Sorry Barb et all. I was quite wrong - I had forgotten to disconnect my
Ethernet cable. Please disreguard my comments re solution on my previous
posting - the "hibernate" setting even prevented working operation of the
WN121T from BOOT. My apologies. Back to the investigative drawing board.
--
Vultch


"Barb Bowman" wrote:

> thanks for the update
>
> On Mon, 18 Feb 2008 11:03:01 -0800, Vulture
> <> wrote:
>
> >Dear, O dearest Barb, your reply pointed me in the right direction and -
> >guess what
> > - the issue appears solved! In order to determine if the problem was a
> >specific NETGEAR WN121T DRIVER issue or a more general MICROSOFT WIRELESS
> >NETWORK ADAPTERS issue, I did a google search on "wireless adaptors + vista +
> >sleep" which yielded
> >"http://www.vistax64.com/tutorials/63567-power-options-sleep-mode-problems.html".
> >Entitled "Vistax64.com (Forums)", it goes on to state that the forum is for
> >both x64 & x86 systems, and although dated 15 May 2007, this is clearly still
> >a highly-relevant document which covers "Vista Sleep issues" so
> >comprehensively that I am most surprised it is not present on the Vista KB
> >under such an index/tag entry. The CRITICAL point re the WN121T (and maybe
> >other) wireless adapter failures AFTER SLEEP would appear to be the advanced
> >POWER SAVINGS PLAN options (Control Panel/Power Options/(plan)/Change
> >Advanced Power Options) WHICH ALSO AFFECT the "soft Power Button (sleep) on
> >the Start Menu. I use "hybrid sleep" for the obvious advantages, and changed
> >"hibernate" to be as recommended in this document (instead of "NEVER"). These
> >are early days, but I anticipate the issue is resolved.
> >Thanks again, Barb, from Vutch (x86 - but only 64 in the UK!)
> >
> >
> >
> >"Barb Bowman" wrote:
> >
> >> I did a Google search for
> >>
> >> NETGEAR WN121T +vista +sleep
> >>
> >> and it turned up lots and lots of pages like
> >> http://www.vidrate.com/product/c009/...B000IT5WY2.htm
> >>
> >> "The only issue I have had with it is that if I set my machine on
> >> Sleep mode the Rangemax seems to disconnect so that when I wake the
> >> machine it has issues. The quickest way to get reconnected seems to
> >> be restarting the machine (but since it saves power to shut down
> >> rather than sleep the PC, no big deal)."
> >>
> >> so it would appear this is an issue with this adapter.
> >>
> >> On Sat, 16 Feb 2008 06:18:00 -0800, Vulture
> >> <> wrote:
> >>
> >> >Thanks skirwin.
> >> >1. I note your observation regarding Microsoft's implementation of
> >> >sleep/hibernate on Vista which is well-supported by the number of KB articles
> >> >on such topics on their support website. BUT, - don't hold your breath about
> >> >all of these problems being fixed in SP1: - I am already running on the SP1
> >> >Release Candidate (see my point 2). Although I had already applied all
> >> >updates/hotfixes which seemed possibly-relevant, I upgraded to the SP1 RC,
> >> >firstly in case I'd missed some, and secondly so that they were all tested as
> >> >a coherent whole.
> >> >2. Yet the problem persists !
> >> >3. As the final SP1 is to be released in some 2-6 weeks, I can only HOPE
> >> >that this issue will be resolved in time.
> >> >4. Your comment re preventing the computer from sleeping is noted, and I had
> >> >already created such a Power plan to facilitate unattended Windows Update,
> >> >One-Care Safety Scanner (sleep does not occur until the scan is complete, but
> >> >the results and subsequent actions are then unavailable as the wireless
> >> >network connection is lost during sleep, thus necessitating a lengthy
> >> >re-scan), backups etc.
> >> >5. However, leaving a computer running 24 hours/day as a workaround to
> >> >losing a wireless network connection during sleep is hardly professional -
> >> >especially as Microsoft actively promotes SLEEP with all it's inherent
> >> >advantages as it's recommended state in which to leave an unattended computer
> >> >at "power-off" !
> >> >6. I have been considering purchase of the new MICROSOFT WINDOWS HOME SERVER
> >> >which seems an excellent product to satisfy many of my system requirements.
> >> >Such purchase is however quite pointless unless this sleep/wireless issue is
> >> >first resolved.
> >> >7. I have always liked Microsoft products despite the many criticisms from
> >> >others over the years, I like Vista, and I welcome the increased stability of
> >> >SP1 (RC). As such a fan, I have 2 recommendations for Microsoft:
> >> >- Don't further delay the final release of SP1, DO try to include
> >> >resolutions to outstanding issues, BUT NOT at the expense of thorough
> >> >testing. The increased stability & performance of the SP1 RC is welcome.
> >> >- Perhaps more importantly, resolve SLEEP NETWORK issues once and for all -
> >> >even if it requires a fundamental re-think, and issue an SP2 resolving such
> >> >issues ASAP.
> >> >8. FINAL COMMENT TO MICROSOFT:
> >> >- SLEEP functionality is fundamental to VISTA.
> >> >- NETWORK functionality is fundamental to WINDOWS HOME SERVER.
> >> >- Most networked HOME USERS have a WIRELESS network.
> >> >- The success of VISTA/HOME SERVER thus depends upon resolving this issue.
> >> >- Contemplate the consequences of NOT resolving this issue.
> >> --
> >>
> >> Barb Bowman
> >> MS-MVP
> >> http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
> >> http://blogs.digitalmediaphile.com/barb/
> >>
> --
>
> Barb Bowman
> MS-MVP
> http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
> http://blogs.digitalmediaphile.com/barb/
>

1. Thanks, Barb, for pointing me to expert groups which led to the following
Vista Team blog; though old (Vista beta), it comprehensively explains
wireless adapter/router connectivity re sleep
http://windowsvistablog.com/blogs/wi...ty-issues.aspx
2. I consequently set my WN121T wireless adapter power saving to "allow
computer to turn device off" & "Do not allow device to wake computer", and
Power Plan network from "max performance" to "max power saving".
3. These settings were ok to give wireless connection from boot as usual.
4. After resume from sleep, work was restored (hybrid sleep) & network (n/w)
icon in notification area ok (green). But almost immediately, audible “device
connect/disconnect� warnings, and the n/w icon turned to fail (red cross).
5. Event Viewer (admin) reported DHCP client failure 1003 (DHCP client
unable to renew n/w adapter address from DHCP server – semaphore timeout).
6. Though not solved, this does appear to isolate the problem as a general
Vista wireless n/w issue rather than a specific NETGEAR WN121T issue, and I
have consequently also posted this under “network & Sharing�.
7. This has been reported to the VISTA SP1 RC team through the beta
reporting facility.

--
Vultch


"Vulture" wrote:

> 1. My network has ALWAYS failed upon RESUME FROM SLEEP using a WIRELESS
> connection via a NETGEAR WN121T wireless-N USB 2.0 adapter, but NOT when
> using a wired Ethernet connection.
> 2. It also works perfectly from BOOT via the WN121T wireless connection with
> my NETGEAR DG834N draft 802.11n (and another 802.11g) wireless modem/router
> on Windows Vista Ultimate, both with and without the SP1 Release Candidate.
> 3. But upon resumption from SLEEP, the wireless n/w connection has ALWAYS
> failed: attempting to re-connect to the network fails, and Device Manager
> reports for the WN121T that “Windows has stopped this device because it has
> reported problems (code 43)�.
> 4. The only remedy is to REBOOT.
> 5. The consequences of this are twofold:
> - firstly, Microsoft-recommended sleep mode is consequently irrelevant
> as a
> reboot is necessary anyway to re-establish the wireless connection,
> - secondly, as no wireless connection appears to be maintained during
> sleep,
> Windows Update, backup and other important maintenance via n/w cannot be
> scheduled during sleep.
> 6. The RELEVANT Vista system settings & status are:
> - ReadyBoost: active with 1860MB
> - WN121T power setting: “Allow the computer to turn off this device
> to save
> power� is unchecked (i.e. blank)
> - Power plan:
> - wireless adapter: “maximum performance�
> - allow hybrid sleep: “on�
> - hibernate: “never�
> - WN121T Drivers: always latest (fails with both Microsoft
> & NETGEAR).
> 7. (NON-RELEVANT factors would appear to include that the motherboard has no
> disks directly attached (the 1TB of RAID10 disk storage is provided via an
> OEM h/w upgrade to an LSI 8308ELP MegaRAID board), as the failure also
> occurred prior to this upgrade – albeit prior to SP1 and with the drivers
> then available in July 2007.)
> 8. It seems clear that this issue is either a GENERAL FAILURE IN MICROSOFT
> SLEEP FUNCTIONALITY FOR USB 2.0 WIRELESS NETWORKS, or a SPECIFIC ISSUE IN THE
> NETGEAR WN121T DRIVER NOT ACCOMMODATING THE MICROSOFT SLEEP FUNCTIONALITY.
> Either way, it would seem a NETGEAR DRIVER v MICROSOFT SLEEP issue.
> 9. This issue has been repeatedly reported to Microsoft for some 6 months
> via Problems & Solutions and more recently via the SP1 Release Candidate
> reporting facility, without resolution.
> 10. CAN YOU HELP?
> - Have you experienced ANY wireless adapter failures ONLY AFTER
> SLEEP on
> VISTA (regardless of adapter)?
> - Have you experienced ANY NETGEAR WN121T wireless adapter failures
> ONLY AFTER SLEEP on VISTA?
> - If so, have you reported them, to whom & with what response?
> - Do you know of any remedies?
> --
> Vultch