Forums

[resolved] wake on lan windows 8.1 pc

Michael Taylor, User (Posts: 36)

Jan 16, 2014 9:02:15 pm EST

new version still doesn't work when waking a windows 8.1 pc from wake on lan, it wakes the pc but I cannot connect to it afterwards. I was hoping this new version would resolve this but it doesn't. pretty useless at this point since all my pcs are set to go to sleep after a specified period of time. I end up having to physically go to the pc to login and then I need to restart the host service for remote utilities to work. this happens every time I try to wake on lan the windows 8.1pc
Edited:Michael Taylor - Jan 20, 2014 1:33:49 pm EST

Conrad Sallian, Administrator (Posts: 1163)

Jan 16, 2014 9:37:46 pm EST

Michael,

Does it wake to a fully operational state (i.e. the discs are working and the monitor lights up)?

Also, can the IP address change after wake-up? For example, if the DHCP server is used in the network and the PCs receive IP addresses dynamically.

Conrad Sallian, Administrator (Posts: 1163)

Jan 16, 2014 10:21:44 pm EST

Hi Michael,

A more specific question - is that issue with Windows 8.1 only? Can you wake up and connect to other editions (e.g. 7, Vista, XP)?

Conrad Sallian, Administrator (Posts: 1163)

Jan 16, 2014 11:10:22 pm EST

I've tried to reproduce the issue here on our premises. Here's the configuration:

Desktop computer with Windows 8.1 installed, including recent updates.
Motherboard: Asus P5QSEPlus with "Power on by PCI devices" enabled in Bios Settings.
Network card: integrated, with "Shut down WoL", "Wake on magic packet" and "Allow this device to wake the computer" enabled in the properties.


There is a wired connection to another computer via a router. Both computers are on the same subnet. Wake on LAN goes without a hitch, even from the shut down state. Once the computer is woken up, Remote Utilities can be established right away.

Please, check if Remote Utilities service starts after waking up and if anything prevents the service from operating. Maybe some security settings, permissions or antivirus software activity.

Michael Taylor, User (Posts: 36)

Jan 19, 2014 1:19:19 pm EST

yes the issue is with 8.1 only, this pc used to have windows 7 and worked fine. it have since installed windows 8 and 8.1 (performed fresh installs not upgrade). I can wake up all my other windows 7 pc's without a problem.

when I send wake on lan to 8.1 pc the system wakes, yes monitor and login screen are fully working. the system is on dhcp but the ip doesn't change. I use hostname to connect not ip (name resolution is ok) the service is started after waking up but if I restart the service and then try to connect it works, but I need to restart the service first even though its already started.
unfortunately I decided to go back to windows 7 and reinstall windows 7 on that pc... to be honest if you say you don't have issues and/or cant reproduce this specific issue, I believe you. its probably something with the operating system. there are lots of issues I see with windows 8 and 8.1 not related to remote utilites so its most likely a Microsoft issue or some other OS related issue. I have issues with some drivers, built in video app, homegroup anomalies, skydrive integration etc... windows 8 and 8.1 in my opinion is a POS.

but I do love remote utilites. works great on all my other pc's

thanks

Conrad Sallian, Administrator (Posts: 1163)

Jan 19, 2014 1:55:12 pm EST

Michael Taylor wrote:
yes the issue is with 8.1 only, this pc used to have windows 7 and worked fine. it have since installed windows 8 and 8.1 (performed fresh installs not upgrade). I can wake up all my other windows 7 pc's without a problem.

when I send wake on lan to 8.1 pc the system wakes, yes monitor and login screen are fully working. the system is on dhcp but the ip doesn't change. I use hostname to connect not ip (name resolution is ok) the service is started after waking up but if I restart the service and then try to connect it works, but I need to restart the service first even though its already started.
unfortunately I decided to go back to windows 7 and reinstall windows 7 on that pc... to be honest if you say you don't have issues and/or cant reproduce this specific issue, I believe you. its probably something with the operating system. there are lots of issues I see with windows 8 and 8.1 not related to remote utilites so its most likely a Microsoft issue or some other OS related issue. I have issues with some drivers, built in video app, homegroup anomalies, skydrive integration etc... windows 8 and 8.1 in my opinion is a POS.

but I do love remote utilites. works great on all my other pc's

thanks
Hello Michael,

As a last resort, try to reinstall the Host altogether, the newest version (5.6.0.3). Who knows, maybe that will resolve the issue since I can't imagine what it might be that causes it.

Michael Taylor, User (Posts: 36)

Jan 19, 2014 2:04:39 pm EST

yes it was the latest version, just installed it the other day. but like I said though its probably an OS issue, back to windows 7 for me..... not worth the headaches. maybe windows 9 will be better, at least I hope so.

thanks again..

Robert Persons, User (Posts: 1)

May 23, 2014 1:19:26 pm EDT

I'm using 5.6.06 and am finding the same problem on a couple of Win7 64 bit pcs. It's intermittent. In both cases I had Teamviewer also installed so I could go in with TV and see that the Usoris service was indeed running after waking from sleep, but I still couldn't connect with RU Viewer. I could get in with TV and the remote pcs seemed to be functioning just fine. If I used TV to stop/restart the Usoris service then I could again connect with the RU viewer ... at least until some random next sleep/wake cycle.

I'm wondering if the service needs to periodically refresh itself to wake up whatever dependencies might still be asleep.

Thanks
Edited:Robert Persons - May 25, 2014 3:19:47 pm EDT

Anton Kalugin, User (Posts: 210)

May 26, 2014 12:24:20 pm EDT

Hello, Robert.

Thank you for your message.

I have created a tech support ticket from your message. You will be replied shortly.

* Website time zone: America/New_York (UTC -5)