Wake On Lan problems

[sefs]

Hi all I'm trying to implement wake on lan.

I've set it up in the bios, and in windows 2000 I have set it to wake on
Magic Packet.

Now it does wake when I send it the magic packet, HOWEVER

1) it also wakes up by its own self even when I have not sent the magic
packet

2) If i open a vnc viewer and type in the address of the machine the vnc
request seems to also wake it up.

My understanding was that it should only wake up when I sent it a Magic
Packet and not to any other network event.

How can I go about setting up WOL so it ONLY wakes up to the magic
packet that i send.

Thanks much for your help.

 

[Galen]

In sefs had this to say:

My reply is at the bottom of your sent message:

Hi all I'm trying to implement wake on lan.

I've set it up in the bios, and in windows 2000 I have set it to wake
on Magic Packet.

Now it does wake when I send it the magic packet, HOWEVER

1) it also wakes up by its own self even when I have not sent the
magic packet

2) If i open a vnc viewer and type in the address of the machine the
vnc request seems to also wake it up.

My understanding was that it should only wake up when I sent it a
Magic Packet and not to any other network event.

How can I go about setting up WOL so it ONLY wakes up to the magic
packet that i send.

Thanks much for your help.

Wake on LAN is buggy like that. Truthfully - that's the answer. It's
insecure and buggy as all heck because it can and just might decide to wake
up when someone sends a happy packet via an inbound telephone call or
something. This isn't what you want to hear but I've seen some great minds
go at it in the trenches with a set of a few dozen PCs that were for a
teleworking crew. The end result is NOT what you want to hear... They left
the PCs on and resorted to another application to usurp desktop control.

Basically they used the enterprise version of RealVNC and the power settings
on the PCs so that they were able to sleep when not in use. Beyond that they
had set it up so that it was a VPN into the network, logon to the server,
and then ended up with the virtual network control to use the PC itself
because it gave them complete control and was less expensive than another
application at that time. The times have likely changed some and my
understanding is that with XP you can do a great deal more with Remote
Desktop but that wasn't a part of 2k nor a part of the few ME boxes in the
sales offices.

So, really, if WOL is the issue then the root of the issue is either power,
noise, improper security on the systems that need only WOL, or the likes...
Instead of looking for a magic packet then look, instead, to alternatives
that require authentication and a decent use of the power settings.

--
Galen - MS MVP - Windows (Shell/User & IE)
http://dts-l.org/
http://kgiii.info/

"At present I am, as you know, fairly busy, but I propose to devote my
declining years to the composition of a textbook which shall focus the
whole art of detection into one volume." - Sherlock Holmes