Hibernation disables network adapter

Running Vista Business edition.

When the system hibernates the Internet connection is dropped which I can
understand, but the network adapter is also disabled. After re-awakening the
system, I cannot connect to the Internet unless I either enable the adapter
or reboot. How can I stop the network adapter being disabled?

TIA
Andrew

If "hibernation" is the state it goes into after sitting idle for awhile and
then you have to sign back on ..... well I second that problem. What a pain!
Never happened with XP Pro. I use an USB wireless ethernet connection.
Sometimes just end up rebooting the damn Computer. That shouldn't be!

"Andrew" wrote:

> Running Vista Business edition.
>
> When the system hibernates the Internet connection is dropped which I can
> understand, but the network adapter is also disabled. After re-awakening the
> system, I cannot connect to the Internet unless I either enable the adapter
> or reboot. How can I stop the network adapter being disabled?
>
> TIA
> Andrew
>

Absolutely spot on - a major pain! And it never happened with my XP Pro
either. Using Cat 5e Ethernet here.

"Ed" <Ed@discussions.microsoft.com> wrote in message
news3A0D683-51E3-416F-91E9-76931A46A1D6@microsoft.com...

> If "hibernation" is the state it goes into after sitting idle for awhile
> and
> then you have to sign back on ..... well I second that problem. What a
> pain!
> Never happened with XP Pro. I use an USB wireless ethernet connection.
> Sometimes just end up rebooting the damn Computer. That shouldn't be!
>
> "Andrew" wrote:
>

Look for a newer driver for your network card. Hibernation and Sleep support
is a function of the driver not Vista. Many manufacturers have basic Vista
drivers for older cards but are not updating them beyond just getting them
working.

--
Kerry Brown
Microsoft MVP - Shell/User
http://www.vistahelp.ca


"Andrew" <noway@forgetit.com> wrote in message
news:3CBCA565-0F49-45F7-A0CB-813A2F86F054@microsoft.com...

> Running Vista Business edition.
>
> When the system hibernates the Internet connection is dropped which I can
> understand, but the network adapter is also disabled. After re-awakening
> the system, I cannot connect to the Internet unless I either enable the
> adapter or reboot. How can I stop the network adapter being disabled?
>
> TIA
> Andrew

So with this information (works with XP, doesn't with Vista) why would anyone
want to digress to vista? I'm not ranting I'm sympathizing...it's
frustrating to see finger-pointing instead of real solutions when your the
company support specialist and your head is on the chopping block.

"Kerry Brown" wrote:

> Look for a newer driver for your network card. Hibernation and Sleep support
> is a function of the driver not Vista. Many manufacturers have basic Vista
> drivers for older cards but are not updating them beyond just getting them
> working.
>
> --
> Kerry Brown
> Microsoft MVP - Shell/User
> http://www.vistahelp.ca
>
>
> "Andrew" <noway@forgetit.com> wrote in message
> news:3CBCA565-0F49-45F7-A0CB-813A2F86F054@microsoft.com...

>

I sympathize but that's the way it is whenever a new version of Windows
comes out. Older hardware often doesn't get the support the users of the
older hardware think it should. I like Vista and use it as my main OS. I've
been using Vista exclusively since last October. Before that I did a lot of
testing with the beta versions. All this was just so I could learn the ins
and outs before I deployed it to customers. The only XP I have installed is
in VM's. That said I haven't upgraded any of my business customers yet. When
XP SP2 came out did you immediately upgrade? Are you immediately upgrading
all your Server 2003 servers with SP2? It's a pain but that's life with
Microsoft. Whenever a new version of Windows (or even a major service pack)
is released it breaks older hardware drivers. If the hardware manufacturer
won't fix it you may be better sticking with XP or updating the hardware.
Note that there is still a lot of old hardware in the supply chain that some
OEMs have installed Vista on that isn't 100% compatible. This is
particularly prevalent with notebooks.

What is the NIC in question?

--
Kerry Brown
Microsoft MVP - Shell/User
http://www.vistahelp.ca


"MarshMan" <MarshMan@discussions.microsoft.com> wrote in message
news:897B9FA2-27E6-4C7B-B57F-AB53A8B11CBE@microsoft.com...

> So with this information (works with XP, doesn't with Vista) why would
> anyone
> want to digress to vista? I'm not ranting I'm sympathizing...it's
> frustrating to see finger-pointing instead of real solutions when your the
> company support specialist and your head is on the chopping block.
>
> "Kerry Brown" wrote:
>

Who said it was an older driver? Not I. Did the Vista compatibility tool (or
whatever the thing is called) report any incompatibilities before I
installed it? No it didn't.

The NIC is an "Intel PRO/1000 PM Network Connection" and is built into the 8
month old Intel Motherboard. The driver is provided by guess who ...
Microsoft.



"Kerry Brown" <kerry@kdbNOSPAMsys-tems.c*a*m> wrote in message
news:E04D9AE0-4200-49CB-8761-439E05F61E29@microsoft.com...

>I sympathize but that's the way it is whenever a new version of Windows
>comes out. Older hardware often doesn't get the support the users of the
>older hardware think it should. I like Vista and use it as my main OS. I've
>been using Vista exclusively since last October. Before that I did a lot of
>testing with the beta versions. All this was just so I could learn the ins
>and outs before I deployed it to customers. The only XP I have installed is
>in VM's. That said I haven't upgraded any of my business customers yet.
>When XP SP2 came out did you immediately upgrade? Are you immediately
>upgrading all your Server 2003 servers with SP2? It's a pain but that's
>life with Microsoft. Whenever a new version of Windows (or even a major
>service pack) is released it breaks older hardware drivers. If the hardware
>manufacturer won't fix it you may be better sticking with XP or updating
>the hardware. Note that there is still a lot of old hardware in the supply
>chain that some OEMs have installed Vista on that isn't 100% compatible.
>This is particularly prevalent with notebooks.
>
> What is the NIC in question?
>
> --
> Kerry Brown
> Microsoft MVP - Shell/User
> http://www.vistahelp.ca
>
>
> "MarshMan" <MarshMan@discussions.microsoft.com> wrote in message
> news:897B9FA2-27E6-4C7B-B57F-AB53A8B11CBE@microsoft.com...

>

Microsoft doesn't supply drivers. Manufacturers write drivers then submit
them to Microsoft. Go to Intel's web site and get the newest driver for you
motherboard. FWIW many people are having problems with Intel NICs.

--
Kerry Brown
Microsoft MVP - Shell/User
http://www.vistahelp.ca


"Andrew" <noway@forgetit.com> wrote in message
news:C50BDC6E-F5B9-4466-99D8-7596146BA1FA@microsoft.com...

> Who said it was an older driver? Not I. Did the Vista compatibility tool
> (or whatever the thing is called) report any incompatibilities before I
> installed it? No it didn't.
>
> The NIC is an "Intel PRO/1000 PM Network Connection" and is built into the
> 8 month old Intel Motherboard. The driver is provided by guess who ...
> Microsoft.
>
>
>
> "Kerry Brown" <kerry@kdbNOSPAMsys-tems.c*a*m> wrote in message
> news:E04D9AE0-4200-49CB-8761-439E05F61E29@microsoft.com...

>

You should also update the chipset driver from the Intel site and see if
there are any BIOS updates. All of these can affect sleep/hibernation. There
is also a Performance and Reliability update for Vista that will be released
later this month which fixes some problems when resuming from sleep.

--
Kerry Brown
Microsoft MVP - Shell/User
http://www.vistahelp.ca


"Andrew" <noway@forgetit.com> wrote in message
news:C50BDC6E-F5B9-4466-99D8-7596146BA1FA@microsoft.com...

> Who said it was an older driver? Not I. Did the Vista compatibility tool
> (or whatever the thing is called) report any incompatibilities before I
> installed it? No it didn't.
>
> The NIC is an "Intel PRO/1000 PM Network Connection" and is built into the
> 8 month old Intel Motherboard. The driver is provided by guess who ...
> Microsoft.
>
>
>
> "Kerry Brown" <kerry@kdbNOSPAMsys-tems.c*a*m> wrote in message
> news:E04D9AE0-4200-49CB-8761-439E05F61E29@microsoft.com...

>

If Microsoft doesn't supply drivers then why does the device manager tell me
the driver is supplied by Microsoft?

This is total BS. I bought a high-end system with Vista in mind, the
compatibility tool told me it was fine, and it isn't fine. Please don't
insult me by telling me that's my fault.

"Kerry Brown" <kerry@kdbNOSPAMsys-tems.c*a*m> wrote in message
newsDF83942-33F7-4A4F-808D-A0C46BD23CA5@microsoft.com...

> Microsoft doesn't supply drivers. Manufacturers write drivers then submit
> them to Microsoft. Go to Intel's web site and get the newest driver for
> you motherboard. FWIW many people are having problems with Intel NICs.
>
> --
> Kerry Brown
> Microsoft MVP - Shell/User
> http://www.vistahelp.ca
>
>
> "Andrew" <noway@forgetit.com> wrote in message
> news:C50BDC6E-F5B9-4466-99D8-7596146BA1FA@microsoft.com...

>