Lights Out Konflikt mit VirtualBox 2.2.0 ?

Probleme oder Fragen zum Lights-Out Add-In unter WHSv1 werden hier beantwortet
Antworten
franz_post
Foren-Einsteiger
Beiträge: 5
Registriert: 26. Apr 2009, 20:39

Lights Out Konflikt mit VirtualBox 2.2.0 ?

Beitrag von franz_post »

Hallo,
über Monate ist Lights Out auf meinem Vista-64 PC problemlos gelaufen und hat meinen WHS klaglos zu jeder Zeit wie gewollt geweckt. Seit einiger Zeit funktioniert das nicht mehr und anhand des Log-Files habe ich den Verdacht, dass das im Zusammenhang mit VirtualBox V2.2.0 steht (könnte auch mit dem Installations-Zeitpunkt von VirtualBox zusammenpassen): anscheinend sendet Lights Out den WOL Request über das von VirtualBox eingerichtete virtuelle Network Interface (IP-Adresse 169.254.27.129) anstatt über meinen echten LAN-Adapter.
Kann man Lights Out irgendwie steuern, über welches Interface er den WOL Request schickt ??? Oder muss ich VirtualBox entfernen???

Danke & Gruss, Franz

2009-04-26 02:16:36.1490 LightsOutClientService [5] Power event: ResumeAutomatic
2009-04-26 02:16:36.2070 LightsOutClientService [7] --- NetworkAvailabilityChanged ---
2009-04-26 02:16:36.2080 LightsOutClientService [7] Network is now available!
2009-04-26 02:16:36.2080 LightsOutClientService [7] PrepareWakeUp
2009-04-26 02:16:36.3070 LightsOutClientService [4] WOL suspended
2009-04-26 02:16:36.5000 LightsOutClientService [5] PrepareWakeUp
2009-04-26 02:16:37.6650 LightsOutClientService [4] sendWakeUp: NetworkAvailable=True, Interval=5
2009-04-26 02:16:37.8880 LightsOutClientService [4] WakeUp
2009-04-26 02:16:38.5000 LightsOutClientService [7] --- Network address has changed! ---
2009-04-26 02:16:39.4210 LightsOutClientService [7] VirtualBox Host-Only Network: IP Address 169.254.27.129
2009-04-26 02:16:39.4210 LightsOutClientService [7] LAN-Verbindung: IP Address 192.168.0.10
2009-04-26 02:16:39.7260 LightsOutClientService [4] Sent WOL packet to server with MAC = 00-1D-60-67-EE-E1
2009-04-26 02:16:39.7260 LightsOutClientService [4] >> Server is alive
2009-04-26 02:16:39.9870 LightsOutClientService [7] PrepareWakeUp
2009-04-26 02:16:40.8110 LightsOutClientService [4] sendWakeUp: NetworkAvailable=True, Interval=5
2009-04-26 02:16:40.8110 LightsOutClientService [4] WakeUp
2009-04-26 02:16:41.0250 LightsOutClientService [4] Sent WOL packet to server with MAC = 00-1D-60-67-EE-E1
2009-04-26 02:16:41.0280 LightsOutClientService [4] >> Server is alive
2009-04-26 04:31:08.0656 LightsOutClientService [6] Power event: Suspend
2009-04-26 04:31:08.0968 LightsOutClientService [6] --------
2009-04-26 04:31:17.0376 LightsOutClientService [7] --- NetworkAvailabilityChanged ---
2009-04-26 04:31:17.0376 LightsOutClientService [7] Network is no longer available!
2009-04-26 10:06:44.0416 LightsOutClientService [7] --- NetworkAvailabilityChanged ---
2009-04-26 10:06:44.0766 LightsOutClientService [7] Network is now available!
2009-04-26 10:06:44.0766 LightsOutClientService [7] PrepareWakeUp
2009-04-26 10:06:44.9606 LightsOutClientService [6] Power event: ResumeAutomatic
2009-04-26 10:06:45.4156 LightsOutClientService [10] Power event: ResumeSuspend
2009-04-26 10:06:46.3986 LightsOutClientService [4] WOL suspended
2009-04-26 10:06:46.4286 LightsOutClientService [6] PrepareWakeUp
2009-04-26 10:06:46.4546 LightsOutClientService [8] --- Network address has changed! ---
2009-04-26 10:06:47.1196 LightsOutClientService [8] VirtualBox Host-Only Network: IP Address 169.254.27.129
2009-04-26 10:06:47.1196 LightsOutClientService [8] LAN-Verbindung: IP Address 192.168.0.10
2009-04-26 10:06:47.8506 LightsOutClientService [4] sendWakeUp: NetworkAvailable=True, Interval=5
2009-04-26 10:06:47.8506 LightsOutClientService [4] WakeUp
2009-04-26 10:06:48.0856 LightsOutClientService [8] PrepareWakeUp
2009-04-26 10:06:48.5326 LightsOutClientService [4] Sent WOL packet to server with MAC = 00-1D-60-67-EE-E1
2009-04-26 10:06:48.8506 LightsOutClientService [9] --- Network address has changed! ---
2009-04-26 10:06:49.0976 LightsOutClientService [9] VirtualBox Host-Only Network: IP Address 169.254.27.129
2009-04-26 10:06:49.2046 LightsOutClientService [9] LAN-Verbindung: IP Address 192.168.0.10
2009-04-26 10:06:49.4906 LightsOutClientService [9] PrepareWakeUp
2009-04-26 10:06:49.7286 LightsOutClientService [7] --- Network address has changed! ---
2009-04-26 10:06:49.8256 LightsOutClientService [7] VirtualBox Host-Only Network: IP Address 169.254.27.129
2009-04-26 10:06:49.8256 LightsOutClientService [7] LAN-Verbindung: IP Address 192.168.0.10
2009-04-26 10:06:49.9866 LightsOutClientService [7] PrepareWakeUp
2009-04-26 10:06:51.6466 LightsOutClientService [4] >> Server is down
2009-04-26 10:06:51.6466 LightsOutClientService [4] PrepareWakeUp
2009-04-26 10:06:52.8596 LightsOutClientService [4] sendWakeUp: NetworkAvailable=True, Interval=10
2009-04-26 10:06:52.8596 LightsOutClientService [4] WakeUp
2009-04-26 10:06:53.2206 LightsOutClientService [4] Sent WOL packet to server with MAC = 00-1D-60-67-EE-E1
2009-04-26 10:06:56.3356 LightsOutClientService [4] >> Server is down
2009-04-26 10:06:56.3356 LightsOutClientService [4] PrepareWakeUp
2009-04-26 10:07:07.4336 LightsOutClientService [4] sendWakeUp: NetworkAvailable=True, Interval=20
2009-04-26 10:07:07.4336 LightsOutClientService [4] WakeUp
2009-04-26 10:07:07.5736 LightsOutClientService [4] Sent WOL packet to server with MAC = 00-1D-60-67-EE-E1
2009-04-26 10:07:10.6856 LightsOutClientService [4] >> Server is down
2009-04-26 10:07:10.6856 LightsOutClientService [4] PrepareWakeUp
2009-04-26 10:07:31.7786 LightsOutClientService [4] sendWakeUp: NetworkAvailable=True, Interval=40
2009-04-26 10:07:31.7786 LightsOutClientService [4] WakeUp
2009-04-26 10:07:31.9076 LightsOutClientService [4] Sent WOL packet to server with MAC = 00-1D-60-67-EE-E1
2009-04-26 10:07:35.0216 LightsOutClientService [4] >> Server is down
2009-04-26 10:07:35.0216 LightsOutClientService [4] PrepareWakeUp
2009-04-26 10:08:16.1196 LightsOutClientService [4] sendWakeUp: NetworkAvailable=True, Interval=80
2009-04-26 10:08:16.1196 LightsOutClientService [4] WakeUp
2009-04-26 10:08:16.3076 LightsOutClientService [4] Sent WOL packet to server with MAC = 00-1D-60-67-EE-E1
2009-04-26 10:08:19.4196 LightsOutClientService [4] >> Server is down
2009-04-26 10:08:19.4196 LightsOutClientService [4] PrepareWakeUp
2009-04-26 10:09:40.4826 LightsOutClientService [4] sendWakeUp: NetworkAvailable=True, Interval=160
2009-04-26 10:09:40.4826 LightsOutClientService [4] WakeUp
2009-04-26 10:09:40.6056 LightsOutClientService [4] Sent WOL packet to server with MAC = 00-1D-60-67-EE-E1
2009-04-26 10:09:43.7166 LightsOutClientService [4] >> Server is down
2009-04-26 10:09:43.7166 LightsOutClientService [4] PrepareWakeUp
2009-04-26 10:12:24.7986 LightsOutClientService [4] sendWakeUp: NetworkAvailable=True, Interval=320
2009-04-26 10:12:24.7986 LightsOutClientService [4] WakeUp
2009-04-26 10:12:24.9516 LightsOutClientService [4] Sent WOL packet to server with MAC = 00-1D-60-67-EE-E1
2009-04-26 10:12:28.0636 LightsOutClientService [4] >> Server is down
2009-04-26 10:12:28.0636 LightsOutClientService [4] PrepareWakeUp
2009-04-26 10:17:49.2066 LightsOutClientService [4] sendWakeUp: NetworkAvailable=True, Interval=640
2009-04-26 10:17:49.2066 LightsOutClientService [4] WakeUp
2009-04-26 10:17:49.5056 LightsOutClientService [4] Sent WOL packet to server with MAC = 00-1D-60-67-EE-E1
2009-04-26 10:17:49.5176 LightsOutClientService [4] >> Server is alive
2009-04-26 13:45:15.0102 LightsOutClientService [6] Power event: Suspend
2009-04-26 13:45:15.0102 LightsOutClientService [6] --------
2009-04-26 13:45:28.8366 LightsOutClientService [7] --- NetworkAvailabilityChanged ---
2009-04-26 13:45:28.8536 LightsOutClientService [7] Network is no longer available!
2009-04-26 17:42:46.1700 LightsOutClientService [6] Power event: ResumeAutomatic
2009-04-26 17:42:46.4980 LightsOutClientService [7] --- NetworkAvailabilityChanged ---
2009-04-26 17:42:46.5540 LightsOutClientService [7] Network is now available!
2009-04-26 17:42:46.5540 LightsOutClientService [7] PrepareWakeUp
2009-04-26 17:42:46.6690 LightsOutClientService [5] Power event: ResumeSuspend
2009-04-26 17:42:49.2730 LightsOutClientService [4] WOL suspended
2009-04-26 17:42:49.2730 LightsOutClientService [6] PrepareWakeUp
2009-04-26 17:42:49.2920 LightsOutClientService [9] --- Network address has changed! ---
2009-04-26 17:42:49.6020 LightsOutClientService [9] VirtualBox Host-Only Network: IP Address 169.254.27.129
2009-04-26 17:42:49.6070 LightsOutClientService [9] LAN-Verbindung: IP Address 192.168.0.10
2009-04-26 17:42:50.3450 LightsOutClientService [9] PrepareWakeUp
2009-04-26 17:42:50.4120 LightsOutClientService [4] sendWakeUp: NetworkAvailable=True, Interval=5
2009-04-26 17:42:50.4120 LightsOutClientService [4] WakeUp
2009-04-26 17:42:50.5440 LightsOutClientService [8] --- Network address has changed! ---
2009-04-26 17:42:50.6940 LightsOutClientService [8] VirtualBox Host-Only Network: IP Address 169.254.27.129
2009-04-26 17:42:50.6940 LightsOutClientService [8] LAN-Verbindung: IP Address 192.168.0.10
2009-04-26 17:42:50.8710 LightsOutClientService [8] PrepareWakeUp
2009-04-26 17:42:51.6520 LightsOutClientService [4] Sent WOL packet to server with MAC = 00-1D-60-67-EE-E1
2009-04-26 17:42:54.7640 LightsOutClientService [4] >> Server is down
2009-04-26 17:42:54.7640 LightsOutClientService [4] PrepareWakeUp
2009-04-26 17:42:55.8280 LightsOutClientService [4] sendWakeUp: NetworkAvailable=True, Interval=10
2009-04-26 17:42:55.8280 LightsOutClientService [4] WakeUp
2009-04-26 17:42:55.9550 LightsOutClientService [4] Sent WOL packet to server with MAC = 00-1D-60-67-EE-E1
2009-04-26 17:42:59.0890 LightsOutClientService [4] >> Server is down
2009-04-26 17:42:59.0890 LightsOutClientService [4] PrepareWakeUp
2009-04-26 17:43:10.1530 LightsOutClientService [4] sendWakeUp: NetworkAvailable=True, Interval=20
2009-04-26 17:43:10.1530 LightsOutClientService [4] WakeUp
2009-04-26 17:43:10.2840 LightsOutClientService [4] Sent WOL packet to server with MAC = 00-1D-60-67-EE-E1
2009-04-26 17:43:13.3960 LightsOutClientService [4] >> Server is down
2009-04-26 17:43:13.3960 LightsOutClientService [4] PrepareWakeUp
2009-04-26 17:43:34.4860 LightsOutClientService [4] sendWakeUp: NetworkAvailable=True, Interval=40
2009-04-26 17:43:34.4860 LightsOutClientService [4] WakeUp
2009-04-26 17:43:34.6360 LightsOutClientService [4] Sent WOL packet to server with MAC = 00-1D-60-67-EE-E1
2009-04-26 17:43:37.7480 LightsOutClientService [4] >> Server is down
2009-04-26 17:43:37.7480 LightsOutClientService [4] PrepareWakeUp
2009-04-26 17:44:18.8260 LightsOutClientService [4] sendWakeUp: NetworkAvailable=True, Interval=80
2009-04-26 17:44:18.8260 LightsOutClientService [4] WakeUp
2009-04-26 17:44:18.9680 LightsOutClientService [4] Sent WOL packet to server with MAC = 00-1D-60-67-EE-E1
2009-04-26 17:44:22.0950 LightsOutClientService [4] >> Server is down
2009-04-26 17:44:22.1130 LightsOutClientService [4] PrepareWakeUp
2009-04-26 17:45:43.2080 LightsOutClientService [4] sendWakeUp: NetworkAvailable=True, Interval=160
2009-04-26 17:45:43.2080 LightsOutClientService [4] WakeUp
2009-04-26 17:45:43.3540 LightsOutClientService [4] Sent WOL packet to server with MAC = 00-1D-60-67-EE-E1
2009-04-26 17:45:46.4660 LightsOutClientService [4] >> Server is down
2009-04-26 17:45:46.4660 LightsOutClientService [4] PrepareWakeUp
2009-04-26 17:48:27.5810 LightsOutClientService [4] sendWakeUp: NetworkAvailable=True, Interval=320
2009-04-26 17:48:27.5810 LightsOutClientService [4] WakeUp
2009-04-26 17:48:27.7040 LightsOutClientService [4] Sent WOL packet to server with MAC = 00-1D-60-67-EE-E1
2009-04-26 17:48:30.8160 LightsOutClientService [4] >> Server is down
2009-04-26 17:48:30.8160 LightsOutClientService [4] PrepareWakeUp
2009-04-26 17:53:51.9110 LightsOutClientService [4] sendWakeUp: NetworkAvailable=True, Interval=640
2009-04-26 17:53:51.9110 LightsOutClientService [4] WakeUp
2009-04-26 17:53:52.0500 LightsOutClientService [4] Sent WOL packet to server with MAC = 00-1D-60-67-EE-E1
2009-04-26 17:53:55.1620 LightsOutClientService [4] >> Server is down
2009-04-26 17:53:55.1620 LightsOutClientService [4] PrepareWakeUp
2009-04-26 18:04:36.2270 LightsOutClientService [4] sendWakeUp: NetworkAvailable=True, Interval=1280
2009-04-26 18:04:36.2270 LightsOutClientService [4] WakeUp
2009-04-26 18:04:36.3680 LightsOutClientService [4] Sent WOL packet to server with MAC = 00-1D-60-67-EE-E1
2009-04-26 18:04:36.3680 LightsOutClientService [4] >> Server is alive
Benutzeravatar
Martin
Moderator
Beiträge: 9981
Registriert: 11. Sep 2007, 10:51
Wohnort: Im wilden Süden

Re: Lights Out Konflikt mit VirtualBox 2.2.0 ?

Beitrag von Martin »

Der LightsOut Client sendet den Broadcast auf 255.255.255.255 raus. Damit sollte er auf allen Interfaces rausgehen.
Mir sind ähnliche Probleme auch mal mit Vmware berichtet worden, konnte die allerdings nie reproduzieren.

Wenn du das VirtualBox Interface deaktivierts, geht es dann?

Gruß
Martin
Essentials 2016 unter Windows Server 2022 auf HP Microserver Gen 8.
Entwickler von Lights-Out
franz_post
Foren-Einsteiger
Beiträge: 5
Registriert: 26. Apr 2009, 20:39

Re: Lights Out Konflikt mit VirtualBox 2.2.0 ?

Beitrag von franz_post »

Bingo, sofort und ohne Probleme!

Aber eine wirkliche Lösung ist das ja noch nicht! Irgendeine Idee, wie man da weiter analysieren kann?

Gruss, Franz
Benutzeravatar
Martin
Moderator
Beiträge: 9981
Registriert: 11. Sep 2007, 10:51
Wohnort: Im wilden Süden

Re: Lights Out Konflikt mit VirtualBox 2.2.0 ?

Beitrag von Martin »

Schau mal in deine PM.

Gruß
Martin
Essentials 2016 unter Windows Server 2022 auf HP Microserver Gen 8.
Entwickler von Lights-Out
torri
Foren-Einsteiger
Beiträge: 1
Registriert: 6. Mai 2009, 07:47

Re: Lights Out Konflikt mit VirtualBox 2.2.0 ?

Beitrag von torri »

Hallo,

ich habe das selbe Problem sobald ich meinen Virtualbox host adapter aktiviere geht WOL nicht mehr.
Ich muß bei aktiviertem Virtualbox host adapter immer bei der WOL.exe die aktuelle IP Adresse meiner
WLAN Karte mit angeben. Wenn ich den VB Hostadapter deaktiviere geht WOL.exe ohne die Angabe der
IP Adresse rein nur mit der MAC Adresse des Servers und Lights Out kann dann auch den WHS Server ohne
Probleme starten.

Mein Log sieht eigentlich genauso aus wie von franz.

Gibt es da schon eine Lösung?

Danke!

Gruß
Torri
Groej
Foren-Einsteiger
Beiträge: 29
Registriert: 1. Mär 2008, 07:57

Re: Lights Out Konflikt mit VirtualBox 2.2.0 ?

Beitrag von Groej »

Hallo an Alle,

ich habe das selber Problem mit VMware Server. Seit ich das Teil installiert habe geht Lightsout nicht mehr und mit WOL.exe bekomm ich den Server auch nicht mehr wach. Von meinen anderen Clienst funktioniert es tadellos wie immer. Ich werd mal im netz Suchen ob ich eine Lösung finde. Wir können ja da nicht die einizgen seien. Es liegt für mich also an Lightsout.

Gruß

Jörg
Sh4gr4th
Foren-Einsteiger
Beiträge: 4
Registriert: 4. Jan 2010, 03:13

Re: Lights Out Konflikt mit VirtualBox 2.2.0 ?

Beitrag von Sh4gr4th »

Hallo,
habe das gleiche Problem. Gibt´s diesbezüglich einen neuen Kenntnisstand?
Benutzeravatar
Martin
Moderator
Beiträge: 9981
Registriert: 11. Sep 2007, 10:51
Wohnort: Im wilden Süden

Re: Lights Out Konflikt mit VirtualBox 2.2.0 ?

Beitrag von Martin »

Das ist doch schon lange gelöst und sollte auch mit der neuen 1.0 kein Problem mehr darstellen.
Was setzt ihr denn für eine Version ein?

Gruß
Martin
Essentials 2016 unter Windows Server 2022 auf HP Microserver Gen 8.
Entwickler von Lights-Out
Antworten