Wake On LAN doesn't work

[Lord Nicoll]

Hey folks, is there any router settings that need to be adjusted to use wake on LAN? I tried to use this feature but it doesn't seem to wanna work, I used a programme pictured under to send the magic packet but it didn't work. I enabled it in the BIOS of the machine and made sure it was set up, but it doesn't work, so I'm thinking maybe router issues?

[DnFx91]

have you enabled the feature on the adapter settings ?

 

[Lord Nicoll]

1 minute ago, DnFx91 said:

have you enabled the feature on the adapter settings ?

 

From within the OS? Yes, although while it runs windows now, Linux or VMware ESXI 6 will be installed on it later. I tried the other NIC too and it didn't work as well. 

[DnFx91]

i've managed to get WOL working on my LAN before but i always used an android app to send the packet from my phone, give that a try to see if your PC is the problem or your LAN

[Lord Nicoll]

4 minutes ago, DnFx91 said:

i've managed to get WOL working on my LAN before but i always used an android app to send the packet from my phone, give that a try to see if your PC is the problem or your LAN

I tried the Wake On LAN app for Android no luck, it didn't turn on

 

[DnFx91]

1 minute ago, Lord Nicoll said:

I tried the Wake On LAN app for Android no luck, it didn't turn on

 

did you check the setting for allowing magic packet from wireless source ?

 

[Lord Nicoll]

Just now, DnFx91 said:

did you check the setting for allowing magic packet from wireless source ?

 

The options from within the device I tried to turn on are difference, WOL is enabled soley through the BIOS, the OS only has power saving controls, not direct control over it, I should have perhaps pointed the machine I wanna wake on lan is a HP server, so it isn't 100% the same.

[DnFx91]

not sure man, if all BIOS settings and OS settings are correct then it should just work. 

 

im guessing you tried every option under that "send options" dropdown on the magic packet program you are using ?

[Lord Nicoll]

Just now, DnFx91 said:

not sure man, if all BIOS settings and OS settings are correct then it should just work. 

 

im guessing you tried every option under that "send options" dropdown on the magic packet program you are using ?

yep, I'll have a look through the router again and see if there's a setting I missed, and I guess I'll have to read the manual to see the wake on lan settings, I might need the password and some people programme, would be my luck

 

[Blake]

3 hours ago, Lord Nicoll said:

Hey folks, is there any router settings that need to be adjusted to use wake on LAN? I tried to use this feature but it doesn't seem to wanna work, I used a programme pictured under to send the magic packet but it didn't work. I enabled it in the BIOS of the machine and made sure it was set up, but it doesn't work, so I'm thinking maybe router issues?

1. You need to enable it on the NIC card not just in the bios.

2. Typically it'll only work on the local subnet (or VLAN).

3. Role your own, you'l learn alot more about the process:

function Wake-Computer
{
    [CmdletBinding(DefaultParameterSetName='Username', 
                  SupportsShouldProcess=$true, 
                  PositionalBinding=$false,
                  HelpUri = 'http://www.microsoft.com/',
                  ConfirmImpact='Medium')]
    [Alias()]

    Param(
                #Username
        [Parameter(Mandatory=$true, 
                   ValueFromPipeline=$true,
                   ValueFromPipelineByPropertyName=$true, 
                   Position=0,
                   ParameterSetName='MacAddress')]
        [ValidateNotNull()]
        [ValidateNotNullOrEmpty()]
        [String[]] 
        $Mac,

        #ComputerName
        [Parameter(Mandatory=$true, 
                   ValueFromPipeline=$true,
                   ValueFromPipelineByPropertyName=$true, 
                   Position=0,
                   ParameterSetName='ComputerName')]
        [ValidateNotNull()]
        [ValidateNotNullOrEmpty()]
        [String[]] 
        $ComputerName
    )

    BEGIN{
        Write-Verbose "Start BEGIN Block"

        Write-Verbose "End BEGIN Block"
    }

    PROCESS{
        Write-Verbose "Start PROCESS Block"
        #add regex clause to make sure variable looks like a mac, and conforms to mac syntax - 1-9+A-F
        if ($Mac -ne $null) {
            #Assume Mac provided.
            $MacAddress = $Mac
        } else {
            #Assume No Mac Provided. Will need to get Mac Address list from offline source / ARP request first etc etc.
            #Clear DNS Cache? look at performance hit.
            #Resolve DNS
            #$IPAddress = Resolve-DNSName -Name $ComputerName
            #$neighbor = Get-NetNeighbor -IP Address $IPAddress
            #Return Mac Address.
            #$macaddress = $Neighbour.LinkLayerAddress
        }

        foreach ($Row in $MacAddress) {
            $Mac = $Row.macaddress
            $MacByteArray = $Mac -split "[:-]" | ForEach-Object { [Byte] "0x$_"}
            [Byte[]] $MagicPacket = (,0xFF * 6) + ($MacByteArray  * 16)
            $UdpClient = New-Object System.Net.Sockets.UdpClient
            $UdpClient.Connect(([System.Net.IPAddress]::Broadcast),7)
            $UdpClient.Send($MagicPacket,$MagicPacket.Length)
            $UdpClient.Close()
            Start-Sleep -Seconds 10
        }

        Write-Verbose "End PROCESS Block"
    }

    END{
        Write-Verbose "Start END Block"

        Write-Verbose "End END Block"
    }
}

 

I've tested the  foreach loop (the part that actually does the WOL), and have confirmed it works intel NICs (don't have any non-intel nics is a system that actually sleeps...)

 

4. It most likely wont work through a router as they split up the broad cast domains, and as you see above, it does a broadcast to send the packet. Try connecting through a switch and let us know.

[Lord Nicoll]

1 minute ago, Blake said:

1. You need to enable it on the NIC card not just in the bios.

2. Typically it'll only work on the local subnet (or VLAN).

3. Role your own, you'l learn alot more about the process:

function Wake-Computer
{
    [CmdletBinding(DefaultParameterSetName='Username', 
                  SupportsShouldProcess=$true, 
                  PositionalBinding=$false,
                  HelpUri = 'http://www.microsoft.com/',
                  ConfirmImpact='Medium')]
    [Alias()]

    Param(
                #Username
        [Parameter(Mandatory=$true, 
                   ValueFromPipeline=$true,
                   ValueFromPipelineByPropertyName=$true, 
                   Position=0,
                   ParameterSetName='MacAddress')]
        [ValidateNotNull()]
        [ValidateNotNullOrEmpty()]
        [String[]] 
        $Mac,

        #ComputerName
        [Parameter(Mandatory=$true, 
                   ValueFromPipeline=$true,
                   ValueFromPipelineByPropertyName=$true, 
                   Position=0,
                   ParameterSetName='ComputerName')]
        [ValidateNotNull()]
        [ValidateNotNullOrEmpty()]
        [String[]] 
        $ComputerName
    )

    BEGIN{
        Write-Verbose "Start BEGIN Block"

        Write-Verbose "End BEGIN Block"
    }

    PROCESS{
        Write-Verbose "Start PROCESS Block"
        #add regex clause to make sure variable looks like a mac, and conforms to mac syntax - 1-9+A-F
        if ($Mac -ne $null) {
            #Assume Mac provided.
            $MacAddress = $Mac
        } else {
            #Assume No Mac Provided. Will need to get Mac Address list from offline source / ARP request first etc etc.
            #Clear DNS Cache? look at performance hit.
            #Resolve DNS
            #$IPAddress = Resolve-DNSName -Name $ComputerName
            #$neighbor = Get-NetNeighbor -IP Address $IPAddress
            #Return Mac Address.
            #$macaddress = $Neighbour.LinkLayerAddress
        }

        foreach ($Row in $MacAddress) {
            $Mac = $Row.macaddress
            $MacByteArray = $Mac -split "[:-]" | ForEach-Object { [Byte] "0x$_"}
            [Byte[]] $MagicPacket = (,0xFF * 6) + ($MacByteArray  * 16)
            $UdpClient = New-Object System.Net.Sockets.UdpClient
            $UdpClient.Connect(([System.Net.IPAddress]::Broadcast),7)
            $UdpClient.Send($MagicPacket,$MagicPacket.Length)
            $UdpClient.Close()
            Start-Sleep -Seconds 10
        }

        Write-Verbose "End PROCESS Block"
    }

    END{
        Write-Verbose "Start END Block"

        Write-Verbose "End END Block"
    }
}

 

I've tested the  foreach loop (the part that actually does the WOL), and have confirmed it works intel NICs (don't have any non-intel nics is a system that actually sleeps...)

 

4. It most likely wont work through a router as they split up the broad cast domains, and as you see above, it does a broadcast to send the packet. Try connecting through a switch and let us know.

I hate coding, I don't go near it, so that's a flat line. From windows enterprise edition I couldn't find any NIC settings in advanced, but the options where there in Power Management. The device is too far away to connect directly, and I don't have a spare RJ45 port on my main PC, so I couldn't. 

[Blake]

1 hour ago, Lord Nicoll said:

The device is too far away to connect directly, and I don't have a spare RJ45 port on my main PC, so I couldn't. 

Well it looks like the router is the issue here. I've had nothing but good stuff from solarwinds, give their free app a go: http://www.solarwinds.com/free-tools/wake-on-lan

 

You could also attempt to configure your router to act as a switch or configure a VLAN so they are in the same broadcast domain.

[Lord Nicoll]

1 hour ago, Blake said:

Well it looks like the router is the issue here. I've had nothing but good stuff from solarwinds, give their free app a go: http://www.solarwinds.com/free-tools/wake-on-lan

 

You could also attempt to configure your router to act as a switch or configure a VLAN so they are in the same broadcast domain.

to the best of my knowledge they are on the same broadcast domain, but there are so many settings in the router I usually just stick to the DMZ, any idea which of these that would be under?

[Blake]

19 hours ago, Lord Nicoll said:

to the best of my knowledge they are on the same broadcast domain, but there are so many settings in the router I usually just stick to the DMZ, any idea which of these that would be under?

To be honest? I can't see anything there that looks to turn your router ports into switching ports. To confirm this (just as a troubleshooting step, not necessarily a permanent solution) Connect a switch between all the devices, and then have just the single Ethernet cable going to the router. The switch should broadcast out all ports, which should be dropped by all devices on the broadcast domain except the target system. If this still isn't doing WOL, fire up wireshark on both the source and target systems anc confirm the packet that is leaving the source is correctly formed and the same with the target device, confirm the packets are arriving correctly.

 

This should help isolate the issue between the application or the network.