G
Gregg
Hello!
I have four systems running XP Professional. I am trying to get ACPI S3
Suspend to Ram to work with Wake on LAN on a 2.0GHz P4 and Intel D845EBG2
motherboard and on two Intel D815EEA2 PIII (1.0GHz and 866MHz) motherboards.
I have another machine on which it works perfectly: an AMD Athlon 2200+ on a
SOYO KT400 DragonLite board with Realtek 8139 NIC. All computers are hooked
to a Netgear FVS318 firewall/router with a built-in 8-port 10/100 switch.
The Intel boards all have their NICs set to wake the system from standby (an
Intel Pro/100 VE Network Connection NIC). The Soyo board has an onboard
Realtek 8139 NIC. I tried a D-Link DFE530TX+ NIC, which is recognized by XP
as a Realtek 8139, but that also pops right back from Standby, even if I
load the D-Link XP driver. I have the latest BIOS flash, NIC, and video
drivers for all systems.
The Intel boards will not stay in standby if Wake on Lan is used. If the NIC
is not set to wake the system, S3 works perfectly. They will go into
standby, but come out immediately if Wake on LAN is used on the Intel
Pro/100 VE NIC, even if all other computers are off. If I disconnect the
network cable, turn off the router, or disable the Local Area Connection in
the OS, it will go into standby and stay there until I hit a key or move the
mouse. Sometimes after rebooting on the D845EBG2 P4, it will go into Standby
and it will stay there (one time only) until a LAN event wakes it (ping or
pcAnywhere). After the first time it works correctly, it fails on every
subsequent attempt to enter Standby until I reboot again...the monitor goes
off for a second, then comes back on. Again, disabling the NIC,
disconnecting it, turning off the router, etc, all let it go into Standby
and stay there.
If I use Intel ProSet to change some parameters, the system will only go
into Standby and stay there if I disable the "Wake on directed packet"
setting. This is good in that it at least goes into and stays in Standby,
but useless for me, since I want pcAnywhere (or a ping from the router
itself) to wake it up.
I have changed ports on the router, made sure nothing is forwarded from the
router to the machines' IP address, changed the IP address, and probably a
few other things I cannot even remember. I need to have these things in
standby and wake up from the NIC when I access them remotely.
The BIOS is set for S3 and a fresh install after setting S3 in the BIOS
makes no difference. I used F5 during setup to force an ACPI install of the
OS.
Any ideas?
OS is XP Professional (also tried Server 2003)
512MB RAM
Pentium 4 2.0GHz on Intel D845EBG2 board and ATI Rage 128 AGP 4x video
OR
Pentium III 1GHz and 866MHz on D815EEA2 boards with only Intel onboard video
and NIC, all PCI slots empty
Intel onboard Pro/100 VE NIC (also tried D-Link DFE530TX+, same result)
WD 40GB hard drive
52X CDROM
3.5" Floppy
Thank you for helping!
Gregg
I have four systems running XP Professional. I am trying to get ACPI S3
Suspend to Ram to work with Wake on LAN on a 2.0GHz P4 and Intel D845EBG2
motherboard and on two Intel D815EEA2 PIII (1.0GHz and 866MHz) motherboards.
I have another machine on which it works perfectly: an AMD Athlon 2200+ on a
SOYO KT400 DragonLite board with Realtek 8139 NIC. All computers are hooked
to a Netgear FVS318 firewall/router with a built-in 8-port 10/100 switch.
The Intel boards all have their NICs set to wake the system from standby (an
Intel Pro/100 VE Network Connection NIC). The Soyo board has an onboard
Realtek 8139 NIC. I tried a D-Link DFE530TX+ NIC, which is recognized by XP
as a Realtek 8139, but that also pops right back from Standby, even if I
load the D-Link XP driver. I have the latest BIOS flash, NIC, and video
drivers for all systems.
The Intel boards will not stay in standby if Wake on Lan is used. If the NIC
is not set to wake the system, S3 works perfectly. They will go into
standby, but come out immediately if Wake on LAN is used on the Intel
Pro/100 VE NIC, even if all other computers are off. If I disconnect the
network cable, turn off the router, or disable the Local Area Connection in
the OS, it will go into standby and stay there until I hit a key or move the
mouse. Sometimes after rebooting on the D845EBG2 P4, it will go into Standby
and it will stay there (one time only) until a LAN event wakes it (ping or
pcAnywhere). After the first time it works correctly, it fails on every
subsequent attempt to enter Standby until I reboot again...the monitor goes
off for a second, then comes back on. Again, disabling the NIC,
disconnecting it, turning off the router, etc, all let it go into Standby
and stay there.
If I use Intel ProSet to change some parameters, the system will only go
into Standby and stay there if I disable the "Wake on directed packet"
setting. This is good in that it at least goes into and stays in Standby,
but useless for me, since I want pcAnywhere (or a ping from the router
itself) to wake it up.
I have changed ports on the router, made sure nothing is forwarded from the
router to the machines' IP address, changed the IP address, and probably a
few other things I cannot even remember. I need to have these things in
standby and wake up from the NIC when I access them remotely.
The BIOS is set for S3 and a fresh install after setting S3 in the BIOS
makes no difference. I used F5 during setup to force an ACPI install of the
OS.
Any ideas?
OS is XP Professional (also tried Server 2003)
512MB RAM
Pentium 4 2.0GHz on Intel D845EBG2 board and ATI Rage 128 AGP 4x video
OR
Pentium III 1GHz and 866MHz on D815EEA2 boards with only Intel onboard video
and NIC, all PCI slots empty
Intel onboard Pro/100 VE NIC (also tried D-Link DFE530TX+, same result)
WD 40GB hard drive
52X CDROM
3.5" Floppy
Thank you for helping!
Gregg