Hey guys. I would like some help setting up remote access for my desktops. Server setup and remote access are not my thing. So, if you guys could help me set this up I would really appreciate this. I need to do the following:

1. setup and use Wake on Lan. Both computers have boot off lan, and for sure one of them has Wake on lan. I can't seem to find BIOS options on either that can tell me if it is on though. 2. I would like help setting up SSH and vsftp from remote locations. The problem I have with this is no-ip. I have no idea on how to set that up. 3. If possible I would like some help with getting Windows able to ssh and transfer files too.

So my systems. My server is an old HP Pavilion 513W. As far as I know this system supports Wake on lan. It is running Arch Linux with the GRsecurity patches.

My Desktop is in my specs. The motherboard is an MSI P4M900M2-L, which definitely supports Wake on Lan but I can't find a BIOS option for it. This system is running Arch Linux with the Mainline Kernel. I am going to read the tutorials on the forums... I would really like help with Wake On Lan and no-ip.com setup.

"Most modern motherboards with an embedded Ethernet controller support WOL without the need for an external cable. Older motherboards must have a WAKEUP-LINK header onboard and connected to the network card via a special 3-pin cable; however, systems supporting the PCI 2.2 standard coupled with a PCI 2.2 compliant network adapter typically do not require a WOL cable as the required standby power is relayed through the PCI bus. Finally, you must have an ATX v2.0 or above compliant power supply. Most systems made after 2004 have all of these hardware requirements."

Thank you gents. Some things to read. I am not sure yet which protocol I wan to use yet.. I definitely want to use ssl for security. I suppose sftp is very much an option. I guess I want to get SSH and wake on lan working first. Quick question for wake on lan, does it only wake the computer from suspension or can it actually TURN IT ON?

For a Windows Client I use MobaXterm to administrate Unix/Linux Environment at work. Has everything you could ever want including copy and past in SSH and even access DE's like GNOME and KDE remotely. Greatest tool ever and free version allows you to have 15 saved sessions. Check it out http://mobaxterm.mobatek.net/. As far as vsftp the IP would be your server IP vsftp service is running. If you have a domain name then your records just reflect name resolution to your server IP. Inside your network go by IP and remotely use DNS. Been busy with new job lately and been hard to find time. Just wanted to pop in here. PM if u need help during the day setting up some services...

Simple answer YES. You can power ON your system and from suspend too using WOL.

From wikipedia:"In the early days of Wake-on-LAN the situation was relatively simple: a machine was connected to power but switched off, and it was arranged that a special packet be sent to switch the machine on.

Since then many options have been added and standards agreed upon. A machine can be in 7 power states from S0 (fully on) through S5 (powered down but plugged in) and disconnected from power (G3, Mechanical Off), with names such as "sleep", "standby", and "hibernate". In some reduced-power modes the system state is stored in RAM and the machine can wake up very quickly; in others the state is saved to disk and the motherboard powered down, taking at least several seconds to awake. The machine can be woken from a reduced-power state by a variety of signals.

The machine's BIOS must be set to allow Wake-on-LAN. To allow wakeup from powered-down state S5, wakeup on PME (Power Management Event) is also required. The Intel adapter allows "Wake on Directed Packet", "Wake on Magic Packet", "Wake on Magic Packet from power off state", and "Wake on Link".[25] Wake on Directed Packet is particularly useful as the machine will automatically come out of standby or hibernation when it is referenced, without the user or application needing to explicitly send a magic packet. Unfortunately in many networks waking on directed packet (any packet with the adapter's MAC address or IP address) or on link is likely to cause wakeup immediately after going to a low-power state. Details for any particular motherboard and network adapter are to be found in the relevant manuals; there is no general method. Knowledge of signals on the network may also be needed to prevent spurious wakening."

I can log into my gateway and boot my desktop, grab what I need and then power it back off remotely. I'm using DHCP with MAC-to-IP mappings so I can look in that file on my gateway system to know the MAC address of the system I wish to wake up. If I didn't have that I could keep a text file.

My next feat is to have non-essential systems power-off (not just halt) on a power outage to extend the battery runtime for the essential systems and then use WOL to power the other systems back on after power is restored and the battery has hit some specific charge level. I think some settings with halt or APM or ACPI are not right on those systems. See OffAndOnAgain. "

As far as SSH is concerned, first off set up a successful demo on local systems and then move up ...to get public access. To access network from outside, port forwarding comes into play. You can even push further by adding another layer of firewall using iptables. Also SElinux and ssh dont work well together.