WoL running on WS2008 waking up WS2003 server

User avatar
John Gray
PlatinumLounger
Posts: 4768
Joined: 24 Jan 2010, 08:33
Location: A cathedral city in England

WoL running on WS2008 waking up WS2003 server

Post by John Gray »

I have set up a 'spare' Windows Server 2003 backup server and want it to be in Standby most of the time (to save £lots in electricity), but be able to be woken up by a subnet-directed broadcast Wake-on-LAN command issued from a Windows Server 2008 box. (No routers around at present, currently same subnet, but will be on a different subnet later.)

I can get the WS2003 server to wake up using my XP workstation, but the same Wake-on-LAN command issued from the WS2008 server fails miserably.

I suspect that the WS2008 firewall is preventing the magic packet getting to the WS2003 server, but I can't find anywhere to open this up.

The best I've found on Google is an article about opening up a port for SQL Server on WS2008, which includes commands of the form

Code: Select all

netsh firewall set portopening TCP 1433 "SQLServer" 
but I'm stymied as to what text to include for my desired subnet-directed broadcast (I can choose almost any port I want).

Any suggestions about how to proceed, please? Thanks!
John Gray

Snaccident - “the unintentional eating of an entire packet of biscuits".

JoeP
BronzeLounger
Posts: 1584
Joined: 25 Jan 2010, 02:12

Re: WoL running on WS2008 waking up WS2003 server

Post by JoeP »

Joe

User avatar
John Gray
PlatinumLounger
Posts: 4768
Joined: 24 Jan 2010, 08:33
Location: A cathedral city in England

Re: WoL running on WS2008 waking up WS2003 server

Post by John Gray »

Thanks, Joe - I'll plough through these. The PowerShell 'build a magic packet' file is interesting!
John Gray

Snaccident - “the unintentional eating of an entire packet of biscuits".

User avatar
John Gray
PlatinumLounger
Posts: 4768
Joined: 24 Jan 2010, 08:33
Location: A cathedral city in England

Re: WoL running on WS2008 waking up WS2003 server

Post by John Gray »

This is a question for our local NETSH expert (you know who you are!).

After having done
NETSH FIREWALL SET PORTOPENING UDP 7 "WakeOnLAN"
I get from
NETSH FIREWALL SHOW PORTOPENING

Code: Select all

Port configuration for Domain profile:
Port   Protocol  Mode    Traffic direction     Name
-------------------------------------------------------------------
7      UDP       Enable  Inbound               WakeOnLAN

Port configuration for Standard profile:
Port   Protocol  Mode    Traffic direction     Name
but I cannot find any way to make the traffic direction to be OUTBOUND... Any thoughts, please? Thanks!

The subsidiary question is whether I should be hitting the Domain profile or the Standard profile!
John Gray

Snaccident - “the unintentional eating of an entire packet of biscuits".

JoeP
BronzeLounger
Posts: 1584
Joined: 25 Jan 2010, 02:12

Re: WoL running on WS2008 waking up WS2003 server

Post by JoeP »

Unless you have activated the outbound side of the firewall it should not matter. The Windows firewall does not filter outbound connections by default.

Also, see How to use the "netsh advfirewall firewall" context instead of the "netsh firewall" context to control Windows Firewall behavior in Windows Server 2008 and in Windows Vista as "netsh firewall" has been deprecated.

IMO, you should use the domain profile.

Joe
Joe

User avatar
John Gray
PlatinumLounger
Posts: 4768
Joined: 24 Jan 2010, 08:33
Location: A cathedral city in England

Re: WoL running on WS2008 waking up WS2003 server

Post by John Gray »

Thanks Joe - I hadn't come across NETSH ADVFIREWALL FIREWALL on my excursions through "NETSH and parameters /?".

If, as you say, outbound connections are not filtered in WS2008, I am still left with the problem that
  • WOL to a standby'd WS2003 server running from an XP workstation works successfully, but
  • WOL to a standby'd WS2003 server running from a WS2008 Server does nothing...
(all on the same LAN).

Have you any suggestions about where to look next, before I stick WireShark on the WS2008 server?
John Gray

Snaccident - “the unintentional eating of an entire packet of biscuits".

JoeP
BronzeLounger
Posts: 1584
Joined: 25 Jan 2010, 02:12

Re: WoL running on WS2008 waking up WS2003 server

Post by JoeP »

You can use NETSH ADVFIREWALL on the 2008 machine to open an outbound port to test.

Joe
Joe

User avatar
John Gray
PlatinumLounger
Posts: 4768
Joined: 24 Jan 2010, 08:33
Location: A cathedral city in England

Re: WoL running on WS2008 waking up WS2003 server

Post by John Gray »

I tried
NETSH ADVFIREWALL FIREWALL ADD RULE NAME="Allow WOL out" PROTOCOL=UDP DIR=OUT LOCALPORT=9 ACTION=ALLOW
and thought it had worked, but further testing showed it didn't. I then turned the Windows Firewall off on the WS2008 box, and that didn't improve matters either.

I think I am in grrrh mode...
John Gray

Snaccident - “the unintentional eating of an entire packet of biscuits".

JoeP
BronzeLounger
Posts: 1584
Joined: 25 Jan 2010, 02:12

Re: WoL running on WS2008 waking up WS2003 server

Post by JoeP »

Is there some physical issue then? Or is a switch or router in the way?

Joe
Joe

User avatar
John Gray
PlatinumLounger
Posts: 4768
Joined: 24 Jan 2010, 08:33
Location: A cathedral city in England

Re: WoL running on WS2008 waking up WS2003 server

Post by John Gray »

Each of the three devices, WS2008, WS2003 and XP Pro is connected to a Netgear 24-port switch. I can't see anything in Device Manager -> Broadcom Ethernet card on the WS2008 box that would have anything to do with outgoing UDP...
John Gray

Snaccident - “the unintentional eating of an entire packet of biscuits".

JoeP
BronzeLounger
Posts: 1584
Joined: 25 Jan 2010, 02:12

Re: WoL running on WS2008 waking up WS2003 server

Post by JoeP »

Can you use any of the Sysinternals tools to "touch" the target machine from the WS2008 box?

Joe
Joe

User avatar
John Gray
PlatinumLounger
Posts: 4768
Joined: 24 Jan 2010, 08:33
Location: A cathedral city in England

Re: WoL running on WS2008 waking up WS2003 server

Post by John Gray »

I've been PINGing the WS2003 box from WS2008, and WireShark running on the WS2003 box shows all sorts of Stuff coming in from the WS2008 box - but no WOL packets. I shall return to this with some SysInternals utilities when next in, on Monday. thanks for your help!
John Gray

Snaccident - “the unintentional eating of an entire packet of biscuits".

User avatar
John Gray
PlatinumLounger
Posts: 4768
Joined: 24 Jan 2010, 08:33
Location: A cathedral city in England

Re: WoL running on WS2008 waking up WS2003 server

Post by John Gray »

The only unexpected thing I've come across is that my 64-bit WS2008 doesn't gives the expected results from running the Wake-on-LAN command whereas my 32-bit WS2008 works perfectly! (Whether the 64-bit-ness is relevant, I don't know.) Nothing in System or Application Event Logs, not surprisingly.

Does 'something' need to be enabled on the server to allow WOL to run correctly, perhaps? It seems a fairly low-level thing to block. I'm fairly baffled...
John Gray

Snaccident - “the unintentional eating of an entire packet of biscuits".

User avatar
HansV
Administrator
Posts: 69458
Joined: 16 Jan 2010, 00:14
Status: Microsoft MVP
Location: Wageningen, The Netherlands

Re: WoL running on WS2008 waking up WS2003 server

Post by HansV »

How does "fairly baffled" work? :scratch:
Regards,
Hans

JoeP
BronzeLounger
Posts: 1584
Joined: 25 Jan 2010, 02:12

Re: WoL running on WS2008 waking up WS2003 server

Post by JoeP »

Maybe it is the software you are using to send the packet. Here's something that is supposed to work in a 64-bit environment - Wake On Lan Ex 2.

Also, you can download .NET code from Depicus Wake On Lan over the Internet.

Joe
Joe

User avatar
John Gray
PlatinumLounger
Posts: 4768
Joined: 24 Jan 2010, 08:33
Location: A cathedral city in England

Re: WoL running on WS2008 waking up WS2003 server

Post by John Gray »

Thanks again, Joe. I have tried three different DOS WOL commands, running as Administrator, all of which work fine everywhere except on this wretched 64-bit server (including the 32-bit WS2008 box). The Wake on LAN EX2 has a rather annoying GUI, and I haven't had enough time to sort it out yet. .NET code would be Greek to me, but for the fact that I would do better at Greek! One's programming days, bar BATch files, are long gone...

I may try and put a new NDIS 6.x NIC driver on these Broadcom NetXtreme II 1 Gigabit cards, but doing this sort of thing on a server fills me with deep trepidation...
Last edited by John Gray on 14 Sep 2010, 17:38, edited 1 time in total.
John Gray

Snaccident - “the unintentional eating of an entire packet of biscuits".

User avatar
John Gray
PlatinumLounger
Posts: 4768
Joined: 24 Jan 2010, 08:33
Location: A cathedral city in England

Re: WoL running on WS2008 waking up WS2003 server

Post by John Gray »

HansV wrote:How does "fairly baffled" work? :scratch:
Perhaps I should have said "unfairly baffled"?

Translation: "I am baffled to a slightly lesser extent than 'totally baffled'"
John Gray

Snaccident - “the unintentional eating of an entire packet of biscuits".

JoeP
BronzeLounger
Posts: 1584
Joined: 25 Jan 2010, 02:12

Re: WoL running on WS2008 waking up WS2003 server

Post by JoeP »

have you checked to see if your NIC drivers are up-to-date. See Broadcom.com - NetXtreme II 1 Gigabit Drivers.

Joe
Joe

User avatar
John Gray
PlatinumLounger
Posts: 4768
Joined: 24 Jan 2010, 08:33
Location: A cathedral city in England

Re: WoL running on WS2008 waking up WS2003 server

Post by John Gray »

See two posts above! I tried this morning but the software I got from the Broadcom site said "The setup files are not compatible with the current installed software package", so I am researching those shown on the Dell website. Nothing straightforwardly obvious, though, and a choice between two.

I tried at home sending WOL packets from a Windows 7 64-bit box, and that worked fine. So somehow it must be down to the NICs, the drivers, the teaming, the iSCSI support... etc!
John Gray

Snaccident - “the unintentional eating of an entire packet of biscuits".