Home » Questions » Computers [ Ask a new question ]

Windows 7 come out of sleep when I open remote desktop

Windows 7 come out of sleep when I open remote desktop

Is there any way to have a Windows 7 machine come out of sleep automatically when I try and connect to it with Remote Desktop?

Asked by: Guest | Views: 335
Total answers/comments: 3
Guest [Entry]

"You'll need to send a magic packet (For Wake ON LAN) through your router. Difficult because router's don't forward these by default, but there are workarounds as found here:

In order to wake up a computer from
the Internet you need a Broadband
connection with a Router connected to
the Modem that keeps your connection
alive (you need a Router even if you
have Static IP).

Waking Up the computer from remote is
done by sending the magic packet
through the Internet using your
Internet IP address, and the MAC
number of the computer that you intend
to Wake Up.

If you do not know your IP address:

Link to: How I find my Computer/Server
Internet address from remote location.

You have to prepare the system for
Wake Up Over the Internet.

Open a Port thought the Router, and
the Software Firewall (use high port
number so it will not conflict with
any other port, 5850 is a good
example).

Assign the port to the internal IP of
the computer that you want to WOL (you
can use the port only for one
computer).

Get this Utility it let you define a
port for WOL.

Link to: Wake on LAN for Windows
Graphical User Interface (WOL GUI)

Take with you a copy of the WOL GUI,
and write down the MAC number. In the
remote location start WOL GUI and type
in your MAC number, Type in the
Internet address (Internet IP) type in
the port number that you left Open.
Click on Wake me Up and it should
work.

The utility:

The magic packet GUI utility is freeware.

You can also use a hotkey to wake it along with the command line version of Wake On LAN:

The Syntax:

C:\path\to\wolcmd.exe [Mac address] [IP address] [Subnet mask] [port number]

Making things easier:

Download AutoHotkey
Use this script:

!w::Run, C:\wolcmd.exe 009027a324fe 195.188.159.20 255.255.255.0 8900

Alt + w will wake the remote computer

modify the script accordingly so the path points to the wolcmd.exe executable and the MAC, IP, and subnet are correct."
Guest [Entry]

"Remote Desktop does not have any built-in remote wake-up capability.

You may be able to configure your network card to wake up on any packet. However, this will probably not work like you intended - as it won't discriminate between your remote desktop connection attempt and someone just scanning your network or a latent packet from a service you were using.

For now, you will probably have to settle with a two-step process: 1) wake the computer with one application, 2) Connect via remote desktop."
Guest [Entry]

"There are different type reasons related to the appearing error message.

Not enough memory

Close your other programs, and then try connecting again. If the problem continues, restart your computer, and then try connecting again. If you still can't connect, contact your network administrator or technical support. (For more information, see Preventing low memory problems.)

Network failure

Make sure that your network connection is working e.g. by accessing some local or global domain or if the Ethernet cable is plugged into your network adapter or wireless switch is turned on.

The remote computer cannot be found

Verify that Remote Desktop is enabled. Check if the remote computer is running (neither in sleep nor hibernation mode). Verify the computer name or its IP address and make sure you typed it correctly.

Connecting a home computer to a computer on a corporate domain requires an intermediate step to ensure that the computers can communicate e.g. to establish a virtual private network (VPN) connection to the corporate network.

Or another application might be using the same port as RDP.

For further examples than my most common cases or for details about each of them see:

http://windows.microsoft.com/en-us/windows-vista/troubleshoot-remote-desktop-problems or
http://support.microsoft.com/kb/2477133"