How to use Wake-on-LAN (WOL) By NeoServer on the iOS

Author : Neo Huang
LAST UPDATED: 2024-10-07 19:44:10 TAG : NeoServer

Index

NeoServer

NeoServer offers a comprehensive management solution for your servers, NAS (Network Attached Storage), and Linux-based routers across iPhone, iPad, and Mac platforms.

How to Use Wake-on-LAN (WOL) by NeoServer on iOS

Wake-on-LAN (WOL) is a powerful network standard that allows you to remotely wake up computers from a low power state or shutdown condition. This technology can be particularly useful in managing home networks or for IT professionals managing corporate networks. If you are an iOS user, you can leverage an app like NeoServer to implement WOL easily. Here's a step-by-step guide on how to set up and use Wake-on-LAN with NeoServer on an iOS device.

Step 1: Ensure Hardware Compatibility

Before you begin, make sure that the computer you want to wake up supports Wake-on-LAN functionality. This is generally found in the BIOS or UEFI settings of the computer. You may need to enable WOL in the power management settings. Additionally, ensure that the network card supports WOL and is properly configured.

Step 2: Download and Install NeoServer

Download the NeoServer app from the Apple App Store. This app is designed to facilitate easy network management tasks like Wake-on-LAN from your iOS device. Install the app following the standard iOS app installation process.

Step 3: Configure Your Computer’s BIOS

Access your computer’s BIOS settings by pressing a specific key during the boot process (often Del, F2, or Esc). Navigate to the power management section and enable the Wake-on-LAN feature. This step is crucial as it allows the network card to power up the computer remotely.

Step 4: Set Up Static IP or Dynamic DNS

To ensure that you can always reach your computer, assign a static IP address or use a Dynamic DNS service. This is important because if your computer's IP address changes (common with DHCP), you might not be able to send the WOL signal effectively.

Step 5: Configure NeoServer

Open the NeoServer app on your iOS device. You will need to configure the app with details about your computer, such as its IP address, MAC address.

Step 6: Connect to Your Network

Ensure that your iOS device is connected to the same local network as your computer. WOL typically works over a local area network. However, with proper configuration and port forwarding, it can also be implemented over the internet.

Step 7: Send a Wake Signal

With everything set up, you can now wake your computer using NeoServer. Select your configured computer in the app and tap the “Wake” button. The app will send a "magic packet" to your computer, which should power it up from sleep or shutdown state.

Step 8: Troubleshooting

If your computer does not wake up, check if all settings (BIOS, NeoServer app, network configurations) are correct. Ensure that the firewall settings on your computer are not blocking the WOL packets. Additionally, some routers may block WOL packets, so verify your router's settings as well.

Conclusion

Using Wake-on-LAN with NeoServer on an iOS device is a convenient way to remotely manage your computer’s power state. It's particularly useful for remote troubleshooting and managing off-site systems without having to physically be there. With the correct setup, you can enjoy the seamless operation and enhanced control over your networked devices.

This guide covers the essential steps to get you started with WOL using NeoServer on iOS, ensuring you can remotely wake your devices efficiently and securely.

Features

Multi Device

Support across multiple platforms: iPhone, iPad, Mac.

iCloud Sync

iCloud Sync ensures all your configuration information is securely stored in iCloud, facilitating seamless synchronization across your multiple devices.

Security

Security, featuring support for password and biometric (FaceID, TouchID) unlocking mechanisms.

A wealth of features.

providing support for SSH terminal, script execution, containers management, and metrics monitoring with zero server-side configuration required.

Screenshots