09-16-2011 02:35 AM
We are currently in the process of rolling out Thinclients which we manage via HP Device Manager 4.4.
Those thinclients are on multiple subnets, but we only use one Device Management Gateway.
The Device Management Gateway is on 172.20.0.0/16 and the Thinclient i am trying to wakeup is on 172.16.1.0/24.
When i send a task to wake it up the management gateway sends a wake on lan packet to the mac address FF:FF:FF:FF:FF:FF and the ip address 172.20.255.255.
This obviously wont work because the thinclient is on a different subnet.
If i manually send a wake on lan packet to 172.16.1.255 with the destination mac address of the gateway it works just fine.
How can i tell the people at HP this, is there a place to report bugs ?
09-16-2011 04:26 AM
Do you have other Thin Clients in that subnet too?
Since HP DM 4.4 there is a new feature which wakes up other Thin Clients in one subnet without the need of a HP DM Gateway but there need to be at least one unit running.
Although I am an HP employee, I am speaking for myself and not for HP
*** Click on the KUDOS star on the left to say 'Thanks' ***