Seite 1 von 1
LightsOut 0.8.2 - Client weckt anderen Client auf
Verfasst: 16. Aug 2009, 11:32
von schneeflocke
Hi, ich hab das interessante Verhalten, dass mein einer Client Rechner den Server und gleichzeitig auch einen weiteren Client zum starten veranlasst.
Client A hat den LightsOut Dienst installiert, Client B ebenso. Server ist LightsOut in der Version 0.8.2 installiert.
Schalte ich Client A ein, so wird nach dem hochfahren, das "wakeup" an den Server verschickt. Exakt im gleichen Moment wacht dann auch Client B auf. Wenn ich den WHS Server physikalisch vom Netzwerk trenne und das gleiche spiel nochmal mach, dann wacht Client B ebenso nach dem hochfahren von Client A auf.
Bei mir im Netzwerk läuft alles via DHCP.
Re: LightsOut 0.8.2 - Client weckt anderen Client auf
Verfasst: 19. Aug 2009, 15:27
von schneeflocke
Ergänzend zu meinen obigen Angaben noch ein Auszug aus dem Log-File des Clients:
Der Client hat tatsächlich zwei verschiedene MAC-Adressen für den WHS gespeichert. Deinstallation des LightsOut Clients und Neuinstallation bringen auch nichts.
Wo speichert der LightsOutClientService die Informationen über die WHS MAC Adresse?
2009-08-19 14:58:26.9531 LightsOutClientService [1] -----------------------
2009-08-19 14:58:26.9843 LightsOutClientService [1] Logging started, LightsOutClientService Version 0.8.2.235
2009-08-19 14:58:26.9843 LightsOutClientService [1] Log cleanup LightsOutClientService.*.log:0
2009-08-19 14:58:27.2031 LightsOutClientService [1] LAN-Verbindung: IP Address 192.168.41.146
2009-08-19 14:58:27.2031 LightsOutClientService [1] Server IP Address 192.168.41.42
2009-08-19 14:58:27.2031 LightsOutClientService [1] Read Server MAC = 00-14-17-32-9C-D0,00-23-64-6A-B3-75
2009-08-19 14:58:30.0156 LightsOutClientService [6] Service should start
2009-08-19 14:58:30.0156 LightsOutClientService [6] Service started
2009-08-19 14:58:30.0156 LightsOutClientService [4] WolThread started
2009-08-19 14:58:31.9375 LightsOutClientService [4] sendWakeUp: NetworkAvailable=True, Interval=240
2009-08-19 14:58:32.6875 LightsOutClientService [4] WakeUp
2009-08-19 14:58:32.7968 AxoNet.LightsOut.WakeOnLan [4] sending magic packet to 192.168.41.255:12287
2009-08-19 14:58:32.8593 LightsOutClientService [4] Sent WOL packet(s) to server with MAC = 00-14-17-32-9C-D0
2009-08-19 14:58:33.9375 LightsOutClientService [4] >> Server is down
2009-08-19 14:58:33.9531 LightsOutClientService [4] PrepareWakeUp
2009-08-19 14:58:33.9687 AxoNet.LightsOut.WakeOnLan [4] sending magic packet to 192.168.41.255:12287
2009-08-19 14:58:33.9843 LightsOutClientService [4] Sent WOL packet(s) to server with MAC = 00-23-64-6A-B3-75
2009-08-19 14:58:34.9375 LightsOutClientService [4] >> Server is down
2009-08-19 14:58:34.9843 LightsOutClientService [4] PrepareWakeUp
2009-08-19 14:58:36.9375 LightsOutClientService [4] sendWakeUp: NetworkAvailable=True, Interval=10
2009-08-19 14:58:36.9531 LightsOutClientService [4] WakeUp
2009-08-19 14:58:36.9843 AxoNet.LightsOut.WakeOnLan [4] sending magic packet to 192.168.41.255:12287
2009-08-19 14:58:36.9843 LightsOutClientService [4] Sent WOL packet(s) to server with MAC = 00-14-17-32-9C-D0
2009-08-19 14:58:37.9375 LightsOutClientService [4] >> Server is down
2009-08-19 14:58:37.9375 LightsOutClientService [4] PrepareWakeUp
2009-08-19 14:58:37.9531 AxoNet.LightsOut.WakeOnLan [4] sending magic packet to 192.168.41.255:12287
2009-08-19 14:58:37.9687 LightsOutClientService [4] Sent WOL packet(s) to server with MAC = 00-23-64-6A-B3-75
2009-08-19 14:58:38.9375 LightsOutClientService [4] >> Server is down
2009-08-19 14:58:38.9375 LightsOutClientService [4] PrepareWakeUp
2009-08-19 14:58:50.9375 LightsOutClientService [4] sendWakeUp: NetworkAvailable=True, Interval=40
2009-08-19 14:58:50.9375 LightsOutClientService [4] WakeUp
2009-08-19 14:58:50.9687 AxoNet.LightsOut.WakeOnLan [4] sending magic packet to 192.168.41.255:12287
2009-08-19 14:58:50.9843 LightsOutClientService [4] Sent WOL packet(s) to server with MAC = 00-14-17-32-9C-D0
2009-08-19 14:58:51.9375 LightsOutClientService [4] >> Server is down
2009-08-19 14:58:51.9375 LightsOutClientService [4] PrepareWakeUp
2009-08-19 14:58:51.9531 AxoNet.LightsOut.WakeOnLan [4] sending magic packet to 192.168.41.255:12287
2009-08-19 14:58:51.9687 LightsOutClientService [4] Sent WOL packet(s) to server with MAC = 00-23-64-6A-B3-75
2009-08-19 14:58:52.9375 LightsOutClientService [4] >> Server is down
2009-08-19 14:58:52.9531 LightsOutClientService [4] PrepareWakeUp
2009-08-19 14:59:33.9687 LightsOutClientService [4] sendWakeUp: NetworkAvailable=True, Interval=160
2009-08-19 14:59:33.9687 LightsOutClientService [4] WakeUp
2009-08-19 14:59:34.0000 AxoNet.LightsOut.WakeOnLan [4] sending magic packet to 192.168.41.255:12287
2009-08-19 14:59:34.0156 LightsOutClientService [4] Sent WOL packet(s) to server with MAC = 00-14-17-32-9C-D0
2009-08-19 14:59:34.0156 LightsOutClientService [4] >> Server is alive
2009-08-19 14:59:34.0937 AxoNet.LightsOut.WakeOnLan [4] sending magic packet to 192.168.41.255:12287
2009-08-19 14:59:34.0937 LightsOutClientService [4] Sent WOL packet(s) to server with MAC = 00-23-64-6A-B3-75
2009-08-19 14:59:34.1093 LightsOutClientService [4] >> Server is alive
Re: LightsOut 0.8.2 - Client weckt anderen Client auf
Verfasst: 23. Aug 2009, 15:19
von Martin
Dienst stoppen, dann zu
HKEY_LOCAL_MACHINE\SOFTWARE\AxoNet Software GmbH\LightsOutClient
gehen und die falsche MAC löschen,
Dienst neu starten, fertig.
Gruß
Martin
(immer noch in Schweden)