Win XP Computer [on Network] Restarts after Shutdown

Hi,
We have two computers set up on a home network.
The first (main) computer is a Dell 4700 running Windows XP, SP2 Pro.
The second computer is an IBM NetVista 2292 21U running Windows XP, SP2 Home Edition.
In Control Panel, Power Options, we have both computers set up as follows:
Schemes Tab
Always On
Never
Never
Never
Advanced Tab
Options
Unchecked
Unchecked
Power Buttons
Shutdown
(On Windows XP Home Only) Ask Me What To Do
Hibernate Tab
Hibernate
Unchecked
UPS Tab
Currently Stopped

When we shutdown the IBM (Windows XP Home) computer it will restart by itself after a short period of time. We have to shut the power off to the computer to keep it shutdown.
We also noted that the small green light on the CD-RW drive remains on after we shutdown the computer. There is no disk in this drive when we shut the computer down.

We do not have this problem with the Dell computer.
We did not have this problem with the IBM computer when it was our only computer.

Any suggestions for keeping the IBM computer shutdown without shutting off it’s power?

Thanks.

 

Hi Pete,
Thanks for the information.
I noticed a lot of the problems deal with rebooting instead of shutting down.

The IBM computer will shutdown.

I checked all the settings in Control Panel, Power Options again today on the IBM computer and then shut it down about noontime today.

I just checked it a few minutes ago and it was still shut down. That's almost 6-1/2 hours so far, so it appears that I don't have a shutdown/reboot problem.
Something else must be causing it to restart. The small green light on the CD-RW drive still remains on.

I'll check some of the other items in this article.

 

Hi, jslow.

I have a hunch your Dell may also have been turned off during that time (or at least you weren't actively using the Dell during that time).

If this is the case, then perhaps your IBM computer's BIOS is configured to allow another computer on the LAN (Local Area Network) to power-up the IBM. Since your Dell is the main computer and the IBM is a workstation, the IBM might just be "obeying" your Dell and allowing the Dell to turn the IBM on.

DISCLAIMER: I'm not especially experienced with networking though so I might be off base. I have only tinkered a bit with networking. This idea seems reasonable to me anyway.

Anyway, my BIOS (Award BIOS rev. 1008) has the following option in the Power > Power Up Control section of my Award BIOS (according to my Asus motherboard manual):

I have never enabled this option in my BIOS but it seems like a reasonable possibility for your IBM and should be a fairly easy check. Your IBM's BIOS may not have exactly the same section titles or descriptions as my BIOS (Award) but I expect there is something similar.

If you find out that the remote power up is enabled in your IBM's BIOS, then instead of disabling that in the IBM's BIOS, you might consider looking in your Dell's Windows XP OS network configuration to see if you can tell the Dell to leave the IBM alone. If there is a way to do that, I think the XP Pro network experts would be able to get you to those network configuration options pretty quickly.

 

Hi Mailman,
Thanks for the reply.

I think your comments may apply to my problem.

I shut the Dell computer down last night and then, after reading your post this morning, I checked the IBM computer and, sure enough, it was on.

I checked network connections on the Dell computer and I couldn't find any way to change anything that makes sense.

I'm going to post on the Microsoft Newsgroup to see if anyone can offer suggestions.

Thanks again.

 

Hi jslow,

I'm moving this thread to the Networking section and see if the Networking people can up with an answer.

Also going to add to your thread title.

Regards - Charles

 

Hi Mailman & Charles,
Thanks again for your replies.

I have tried the following on my Dell computer:
Went to; Control Panel, Administrative Tools, Computer Management, Device Manager, Network Adapters, Intel Pro/100VE Network Connection Properties,
Advance Tab.
Then under Property "Wake on Settings ", I changed the Value to "Disabled ".

So far, this seems to have eliminated the problem. I have shut down the Dell computer a number of times (With the IBM computer shut down) and the IBM computer has not started up unattended.

If any problems re occur, I'll post back.

Thanks

 

Hi jslow, good news and thanks for the post back.

Regards - Charles

 

Hi, jslow. I'm glad to hear your issue might be resolved!

However, based on your replies, I'm not certain you understood me correctly so i will clarify.

It seems (before you made your recent Dell network configuration changes) while you had both computers off, then the IBM would not power up on its own. This was my hunch.


Also it seems, beginning with both machines off, if you turned on the Dell, that would in turn "Wake up" (power up, perhaps) the IBM.

Also, perhaps if you turned off your IBM but left the Dell on (and perhaps even used the Dell), then the Dell would periodically cause the IBM to turn on as the Dell refreshed its own network inventory.

Anyway, I'm glad Charles moved this to the networking forum. We can probably get more definitive information than mine here.

Good luck!

 

Hi Mailman,

The problem was that the IBM computer would restart unattended.

It appears that we now have it narrowed down to: The IBM computer apparently starts itself when the Dell computer shuts down.
We have no problem starting or shutting down either computer.
It's just that the IBM computer starts by itself when unattended. We would notice it was running when we walked by it and you could hear it.

The changes that I posted previously did not correct the problem.

I am currently trying another suggestion and, if it works, I'l post the details here.

 

Hi,
Here is an update on my problem.

I disabled all items in the Power, Automatic Power On, section of the BIOS
and this stopped the IBM computer from starting unattended.

Thanks for your replies.

 

Hi, jslow.

That's GREAT news! I'm glad your issue is solved. Way to be persistent!

So the BIOS setting appears to be the solution after all.

Thanks for posting back and letting us know what worked. Maybe somone else searching these forums with a similar problem will find this thread helpful.