Hello,
I'm sorry, but I found another problem. I want to wake up a PC through a VPN and installed the WOL agent on a Windows Server. I added the firewall rules and this is working fine (UDP Port 9 and ICMP are open).
The problem is in the Wake On LAN software itself. For using the WOL agent I put the IP-Adress of the Windows Server with the WOL agent installed on in the field "FQDN / IP" of the page "Wake Up" in the properties of the PC I want to wake. But now the pinger can't show any more if the PC is online or offline.
I think the Wake On LAN software tries to ping the server with the WOL agent and not the PC to which I sent the magic packet.
The problem even exists in the local network and when I changed it back that it should send the WOL to Broadcast IP.
The 192.168.1.20 is the IP of the Windows Server with WOL agent. When I put the IP of the PC I want to wake there, it's working.
I hope that you understand what I mean and I hope that you can fix it, so that the pinger uses the IP-adress which is located in the "Status / Control" page of the properties.
Greetings
websurfer83.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There are two panels involved here, because there are two technologies at work.
You configured the Wake-up IP address using the "broadcast" field on the "wakeup" tab.
The FQDN/IP field tells it how to go directly to the host. This is used to determine online status.
So, broadcast should point to your Agent.
FQDN should be the ip or name of your host.
I use this configuration myself to wakeup remote computers using Agent, and it does correctly show me the online status.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I'm sorry, but I found another problem. I want to wake up a PC through a VPN and installed the WOL agent on a Windows Server. I added the firewall rules and this is working fine (UDP Port 9 and ICMP are open).
The problem is in the Wake On LAN software itself. For using the WOL agent I put the IP-Adress of the Windows Server with the WOL agent installed on in the field "FQDN / IP" of the page "Wake Up" in the properties of the PC I want to wake. But now the pinger can't show any more if the PC is online or offline.
I think the Wake On LAN software tries to ping the server with the WOL agent and not the PC to which I sent the magic packet.
The problem even exists in the local network and when I changed it back that it should send the WOL to Broadcast IP.
Here is a screenshot:
http://www.bilder-hosting.info/viewer.php?id=viu1430815223d.PNG
The 192.168.1.20 is the IP of the Windows Server with WOL agent. When I put the IP of the PC I want to wake there, it's working.
I hope that you understand what I mean and I hope that you can fix it, so that the pinger uses the IP-adress which is located in the "Status / Control" page of the properties.
Greetings
websurfer83.
There are two panels involved here, because there are two technologies at work.
You configured the Wake-up IP address using the "broadcast" field on the "wakeup" tab.
The FQDN/IP field tells it how to go directly to the host. This is used to determine online status.
So, broadcast should point to your Agent.
FQDN should be the ip or name of your host.
I use this configuration myself to wakeup remote computers using Agent, and it does correctly show me the online status.