WOL

Discussion in 'Windows Small Business Server' started by Skc, May 19, 2005.

  1. Skc

    Skc Guest

    We have a Dell PowerEdge 2800 with x2 gigabit NICs with PXE enabled. I
    believe PXE is to do with WOL - (wake on LAN)?

    If the server is swithed off can I wake the machine up? I have downloaded
    various free WOL programs and it is not working!

    Help!
     
    Skc, May 19, 2005
    #1
    1. Advertisements

  2. PXE is what lets workstations boot from the server rather than from the
    local OS. It's separate from wake on lan.

    A lot of people have reported trouble getting WOL to work on Dell products -
    I've got a fair amount of time wasted in trying to get it to work on a
    Dimension 8400. In any case, since servers are generally left running 24x7,
    and since Dell is already known for less than stellar WOL support, I doubt
    you'll get WOL to power up a Dell server. You could check their support
    forums, but if your experience is anything like mine, you'll find a lot of
    questions but few answers.
     
    Dave Nickason [SBS MVP], May 19, 2005
    #2
    1. Advertisements

  3. Skc

    aus Guest

    Dell machines generally need to have thair NIC settings changed to
    enable the standard Magic Packet WOL programs to work (many seem to miss
    this and think Dell has some problem).

    In Windows / Device Manager / Network card properties / Advanced

    find 'Wake on Settings' at the bottom of the list and select 'Wake on
    Magic Packet' (the default is 'OS Controlled').

    Post back if this works - or not.
     
    aus, May 21, 2005
    #3
  4. aus - thanks for your input. I'd love to get this working, so any help you
    can provide will be greatly appreciated. I have a situation where traveling
    users connect laptops to the LAN over VPN, then want to access their
    desktops but they're powered down. For now, I'm trying to get it working on
    my new Dimension 8400 with broadcom gigabit NIC.

    I enabled WOL in the bios. I verified the setting you describe, and enabled
    the "allow this device to bring the computer out of standby" setting. No
    go.

    While in standby, the PC responds to pings, and I can even access it
    remotely with Computer Management. But I tried 2 WOL magic packet programs,
    and can't get the PC to come out of standby.

    What I really want is to wake it from a full power-down state, but I can't
    even get standby to work.
     
    Dave Nickason [SBS MVP], May 23, 2005
    #4
  5. Skc

    aus Guest

    Hi,

    I do the same for a client of mine - they turn their own PCs on from
    home. The way I do it is have a slave PC (Win 2000 as it happens) always
    on somewhere on the network. They connect in via a VPN, run VNC to that
    PC and hit the batch file for their own PC (just a call to the WOL exe
    with the appropriate MAC address) - that shoots off a Magic Packet to
    their PCs.

    They have a mixture of Compaq and Dell. The Dells didnt work to start
    with - until I tried the NIC setting and used a new WOL program. These
    little programs are not all the same I have found - the one I use for
    the Dells is some obscure one:

    See: http://www.annoyances.org/exec/forum/win2000/t1004416137

    The download is at the sourceforge link (wol 0.5.1) about half way down
    - I think there is a newer version around (0.7?) but I use this one at
    the moment untill I find a NIC it can't handle.

    Try this one on a basic PC first so you know its up and running then try
    the server. If the server fails try a couple of the other options in the
    NIC settings re. WOL then post back.
     
    aus, May 24, 2005
    #5
  6. If we ever meet, the beer's on me. I'm not exactly sure what got this
    working, but it works. I used the program you suggested, but now the other
    ones I tried work as well. And it will bring the PC up from a full
    shutdown, which is great. I did verify the bios settings, and WOL and Allow
    this device to wake up enabled in the NIC properties.

    Thanks!
     
    Dave Nickason [SBS MVP], May 24, 2005
    #6
  7. Skc

    aus Guest

    Im glad that worked - I remember playing with it for a while. You may be
    able to help me. The reason I used a slave PC on the office network to
    switch on other client PCs was because the Magic Packet request doesnt
    traverse my VPN link. Im using the Safenet VPN client software (an old
    version admittedly) to a Netscreen firewall and it refused to work no
    matter what.

    I'd be interested if you can connect via your VPN and magic packet a PC
    directly as this may answer weather WOL unicasts can cross a VPN link
    in general (as I had expected them originaly to) or not.
     
    aus, May 25, 2005
    #7
  8. I'll try to check it tonight, but if not I'm out of town until Tuesday and
    I'll do it when I get back. I'm currently using regular Windows VPN to RRAS
    with ISA 2000.


     
    Dave Nickason [SBS MVP], May 25, 2005
    #8
  9. OK aus - I tried it and got the same result you did. The WOL works on the
    LAN but not over VPN. Also, I used a WOL program that can get the MAC
    address from the IP. That too works locally but not over VPN.

    Got to be something to do with routing, don't you think? Ping over VPN
    doesn't work either, so that might be a clue in tracking it down. I'm going
    to ask some of the other MVPs and do a little research on this - if I figure
    out a solution, I'll let you know.

    I'm in the same boat - I need it to work over VPN to be useful.


     
    Dave Nickason [SBS MVP], Jun 1, 2005
    #9
  10. Skc

    Matt S Guest

    Just a thought...

    My experience with VPN software is that it's set up to transport IP packets,
    not Ethernet frames. If this WOL software is sending an Ethernet frame to a
    client's MAC address for the wake-up, it's not using IP, which means the
    magic packet won't be routed over an IP network like a VPN. It would only
    work on the same Ethernet LAN as the target machine. Essentially, your
    remote computer doesn't know that the target Ethernet MAC address is on the
    other side of the VPN tunnel.

    Someone please check my work...

     
    Matt S, Jun 1, 2005
    #10
  11. Skc

    aus Guest

    WOL packets go over UDP (same layer as TCP - i.e the transport layer)
    and are therfore routeable - which is nice!


    Dave - the PING failing is because its being blocked at some point on
    your setup. You should be able to PING any internal IP. I have no
    trouble with any service in or out over VPN - from POP3 to Remote
    desktop - PING isnt special (dont tell it).

    However the WOL may fail on actually getting out of the PC in the first
    place - which is were I think the issue is. I'd have to get some
    monitoring up to check for sure. Maybe the subnet mask needs to be all
    255's to send as a broadcast - its something I have seen (i.e. Not the
    subnet of the remote network). Can't remember if I tried that.

    Now I did see someone running WOL over the Internet direct to his lan
    (no VPN) - which is fine but a bit too open to naughtyness for me - i.e.
    anyone could poke a WOL to your LAN, and though not really a security
    issue I'd rather not have that!




     
    aus, Jun 2, 2005
    #11
  12. If I get a chance, I'm going to try some different WOL programs. I just
    tried the one I could grab easiest, but I do think it'll send the magic
    packet with just an IP and subnet, and I tried that in addition to the MAC
    address.

    I don't know what would be blocking ping or WOL unless it's the DSL router.
    Ping to my SBS works from the LAN but not from home, same as WOL. My home
    PC is a plain XP Pro SP2 box with the SP2 firewall, no router or anything
    other than the DSL modem.

    Inbound ping to the SBS is blocked by both ISA and Sonicwall, but the VPN
    would be bypassing both of those. I'm thinking Mark is on track about
    routing, and you're right about the magic packet not leaving the home PC.
    I'll play further when I get some time and let you know if I come up with
    anything.


     
    Dave Nickason [SBS MVP], Jun 2, 2005
    #12
  13. Skc

    aus Guest

    If your VPN is up and established PC-to-SBS then the DSL router or
    hardware firewall will not be interfering with any data across it as its
    all encapsulated between the VPN endpoints.

    Are you PINGing the SBS (LAN side) with the IP adress? I think RRAS does
    disable PINGs to the external SBS NIC in this instance - you need to
    check what RRAS is doing as it does do some filtering as I remember when
    its setup for VPN access.


    I think Matt was saying WOL isnt routable over an IP network and only
    works on a local LAN, which isn't true. You can send a routed Internet
    WOL right now and it will work fine with no VPN (needs some router
    setup). It was the WOL over VPN that was the issue.


    OK I just tried and got it to work ok - from remote PC to LAN PC via VPN
    - hoorah. Not sure what was different to last time I tried last year. I
    used the Matcode WOL program:

    http://www.depicus.com/wake-on-lan/wake-on-lan-cmd.aspx


    Give that one a go and see if you have any joy. I was running this to a
    Compaq PC - didnt try any of the Dells yet, butIm sure they'd be ok.



     
    aus, Jun 2, 2005
    #13
  14. I'm not sure of the name of the WOL program I tried from home, but it was
    one that definitely works on the LAN - no difference whatsoever between the
    two situations, except that one was LAN and one VPN. I'll try the Matcode
    program when I get a chance.

    You're probably right about RRAS blocking ping - I tried to ping the SBS by
    IP and it failed. I didn't pursue it further.


     
    Dave Nickason [SBS MVP], Jun 2, 2005
    #14
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.