Stardock Forums
I use a wake on lan tool outside of multiplicity that works fine, but for some reason I cant get it working inside of multiplicity. It gives me the option to use WOL for my other two pc's but they just never wake up. I'm doing the WOL from the main pc that's sharing its keyboard and mouse.
Anyone have ideas on this?
I do have 1 more question. Is "always Use the IP address xxxxx" the preferred method if you have static internal IP's assigned?
It's a preference - of no other consequence.
Sean Drohan
Stardock Support Manager
Very glad to hear it...
I must say, your determination to find the cause was valiant, to say the least. A testament to your will and intellect is well documented in this thread.
If you ever need a QA job... 😉
Sean Drohan
Stardock Support Manager
ha! NOBODY would want that. Software would never make it out the door. My ocd falls into the realm of perfectionism to a fault. It causes me much agony and lost free time fixing inconsequential things. We all have our "issues" i suppose lol.
Anyhow, dont let me own the front page of the multiplicity forums any longer 
Again i do sincerely appreciate taking my cynical attitude in stride and helping me in the ways you could along the way. Here and in other threads.
Looking forward to whats to come in the future since im on my way to owning about half your stuff now 
ooooooiiii im back.
So this rears its ugly head again.
I use torguard VPN. Like most VPNs it intentionally increases its interface metric to ensure traffic goes over the VPN as to prevent leaks.
No harm no foul. Until of course, I try to use multiplicity to wake on lan. Once again, everything can wake the other pc's on the lan fine EXCEPT multiplicity.
I went through a bunch of troubleshooting with the torguard support and it boiled down to it being a problem with this software. What is it doing differently than basically everything else? I can ping other pc's, i can seamless to other pc's, I can wake other pcs from any app even the most rudimentary EXCEPT this when ANY other adapter has the same or higher metric than my ethernet adapter.
Can we not force this to stop trying to send from whatever has the highest metric and/or ignore virtual adapters? it should be sending the broadcast via the physical adapter same as everything else uses?
The only fix for this is now is on your end this time. Nothing they or I can do. I can change the interface metric and get it working again, but id have to do it EVERY time i used the vpn as each time you disconnect and re-connect it re pumps up its interface metric for the aforementioned reasons.
As it sits, im just dealing with it for now. Ive been only using my vpn situationally but was considering using it full time. Cant really do that now. Just wanted to bring it to your attention. It shouldnt be trying to send via virtual adapters, its the only software ive tried and i have at least a half a dozen i can use real-time right now and list that work fine under the circumstances that this wont.
Everything else has been rock solid with it ever since though. Love it, and would love to see this fixed. its cumbersome and honestly (please dont take offense) it feels amateur (the bug. the software is incredibly comprehensive). If i was a developer and I took pride in my work (i wish i was, man did i pick the wrong career path) and I saw that everyone elses software not only worked, but did things a certain way - id probably assume there was a reason for that and follow suit.
Of course, being wholly ignorant of the goings on under the hood - there could be a legitimate reason for the deviation.
Still im the case study proof that it presents issues, and have examples of several reproducible circumstances in which it does so.
If you have any questions, will obviously be around. Dont hate me for being critical, you get paid to fix bugs right Contrary as it may seem, i truly do love the software, hence wanting to see it improve. (unless its EoL then squash my dreams)
Worst part is it has become evident that the behavior surrounding this wake on lan debacle had forced me to disable automatic metric handling for just about every adapter and jostle things about when that was a hacky workaround for what appears to be a deviation from the norm or bug on your side.
In a perfect world with the app receiving a small update to address the incorrect selection of network adapter to broadcast from, i could set them all back to automatic and let windows put things back as they should be. No idea though, never had to mess with it before.
I also have the same problem. I also have Virtualbox and reorganize my network adpaters but still does not work. I don't have a VPN on the PC i'm trying to wake. I tried MANY apps and they all wake up my pc. Only Multiplicity is unable to wake it up. I'd like this functionnality to work.
well i'd like to think you figured it out by now, but if not - try flushing the arp cache. i only found this old thread because i just updated to a fresh windows install (11) and wouldnt ya know, this is back. except without virtualbox this time.
ive already ascertained it is vmware's virtual adapters but even with the proper interface metric it will still not wake anything.
that being said, im about to flush the cache myself and hopefully thats the ticket.
think i got it sorted. been so darn long i couldnt remember the specifics
so setting the interface metric in and of itself isnt good enough because apparently it negotiates on the fly. you need to go into the adapter and go to properties > ipv4 > advanced > and uncheck automatic metric.
I did it for both ipv4 and ipv6, unsure if both are necessary but since i have both enabled i might as well start at the top so to speak.
anyhow, hope thats helpful
sheesh. still not it. seems windows 11 wants to see the virtual adapters as and keep them as a public network. this results in creation of public firewall rules (as they somehow get priority at startup irrespective of the metric set) and Troubleshooting blocked inbound network traffic on Windows Vista or later after installing a VMware product (1004813)
is already applied in the registry yet seems to not take effect. could be a win11 networking issue, surprised face.
and more seemingly related info.
windows - Why private VMware network recognized as unidentified (public) network? - Super User
trying to find a way around it but at current outside of disabling the vlan adapters or restarting them after each reboot of the pc, wake on lan via multiplicity is once again down.
at this point my inquiry becomes why does this effect multiplicity and no other wake on lan applications. its querying its adapter priority from a non-ideal place evidently.
Welcome Guest! Please take the time to register with us.