- This topic is empty.
-
AuthorPosts
-
September 29, 2010 at 3:38 pm #6142
Hi,
I am looking for a way to reboot the V10L terminals remotely. I know this can be done using WDM, but can it be done any other way?
Many thanks,
Ben
September 30, 2010 at 8:56 am #19133AnonymousInactive- Total Post: 132
- Legend in Own LunchBox
- ★★★★★
try this (found on http://www.wyse.com support forums)
http://THIN_CLIENT_IP/&V52&CI=59|RB=1|MT=3||HS=1.1.1.1|September 30, 2010 at 9:34 am #19139You can do this with my ConfGen tool from this site.
CG
September 30, 2010 at 11:00 am #19145Thanks guys,
I’ve got this working when sending the command to a terminal without any config settings. However the client will not accept the command when I have used a config file. I have enabled Admin mode. I’ve also disabled the following services, however enabling them didnt make any difference:
SNMPD
Thinprint
VNCD
WDMWhat needs to be enabled in order to run this command?
Would I need to provide admin credentials in order to reboot the terminal? If not, what is preventing anyone from running this command?
Many thanks,
Ben
September 30, 2010 at 11:25 am #19146AnonymousInactive- Total Post: 132
- Legend in Own LunchBox
- ★★★★★
WDM service is responsible for handling this request. Please enable it. try http://THIN_CLIENT_IP/&V52&CI=59|RB=1| – immediate reboot without dialog box. I don’t remember wether you can remap WDM service to some different port (just to hide this) but …maybe you can put terminals to the separate LAN and forbid port 80 there for everybody except you. Smth like this.
September 30, 2010 at 11:36 am #19148Thanks,
is there a guide where I can find out about these commands?
September 30, 2010 at 11:56 am #19149Ok,
So I’ve managed to reboot the terminal with the config file applied by enabling WDM. I’ve got Admin mode on and lockdown on. I am able to reboot the terminal without using any Admin credentials. Is there any way to lockdown the ability to send the reboot command, or does opening the WDM service enable anyone to send the reboot command?
Thanks,
Ben
September 30, 2010 at 12:03 pm #19150AnonymousInactive- Total Post: 132
- Legend in Own LunchBox
- ★★★★★
AFAIK there’s an option of using wdm via SSL. This should close the way for others to send commands to thin clients. But I never used it in this way.
September 30, 2010 at 12:30 pm #19151OK,
so is that a setting on the Wyse Client? I’m worried about anyone sending the HTTP command to a client and rebooting. It seems that if WDM service is on then anyone can send to it. The WDM server at this point is irrelevant as it is not required to send the reboot command. It seems like there is a massive security risk with leaving the WDM service enabled as there is no prevention mechanism to stop unauthorised commands.
November 26, 2012 at 9:17 pm #23037Config Generator is Great and worked to reboot however I want to be able to send specific V10L devices a reboot command in sequence. When I tried the command line noted it would shut the unit off and not reboot.
Is there anything different than the command
http://THIN_CLIENT_IP/&V52&CI=59|RB=1|MT=3||HS=1.1.1.1| reflecting how Config Generator sends the remote command?December 3, 2012 at 2:15 pm #23062For a reboot just send
&V52&CI=59|RB=1 to the client. That’s all.CG
December 26, 2012 at 3:59 pm #23203@ConfGen wrote:
For a reboot just send
&V52&CI=59|RB=1 to the client. That’s all.CG
In my testing, this command will shut down the terminal, not reboot it. Does it act differently with different firmware versions perhaps?
January 12, 2013 at 4:27 pm #23301Just as a head’s up, you can also use snmpset.exe as it can also be used to reboot a list of WYSE thin clients or a single one as well. Download snmpset here [http://www.snmpsoft.com/freetools/snmpset.html] and install it. Then run the below cmd against a list of thin client IP addresses. PLEASE err on the side of caution when running this as it could be disruptive to end users if the incorrect IPs are in the list:
for /f %i in (c:tempthin_client_IP_addresses.txt) do @c:toolssnmpset -v:1 -c:SNMPWYSE -r:%i -o:.1.3.6.1.4.1.714.1.2.6.1.1.0 -val:0 -tp:int
The above runs snmpset against a text file which contains a list of IPs. The WNOS.INI has SNMP enabled along with setting the community string to SNMPWYSE [i.e. Community=SNMPWYSE]. The OID is .1.3.6.1.4.1.714.1.2.6.1.1.0.
Hope this helps. 🙂
January 18, 2013 at 2:13 pm #23336@ab17182 wrote:
Just as a head’s up, you can also use snmpset.exe as it can also be used to reboot a list of WYSE thin clients or a single one as well. Download snmpset here [http://www.snmpsoft.com/freetools/snmpset.html] and install it. Then run the below cmd against a list of thin client IP addresses. PLEASE err on the side of caution when running this as it could be disruptive to end users if the incorrect IPs are in the list:
for /f %i in (c:tempthin_client_IP_addresses.txt) do @c:toolssnmpset -v:1 -c:SNMPWYSE -r:%i -o:.1.3.6.1.4.1.714.1.2.6.1.1.0 -val:0 -tp:int
The above runs snmpset against a text file which contains a list of IPs. The WNOS.INI has SNMP enabled along with setting the community string to SNMPWYSE [i.e. Community=SNMPWYSE]. The OID is .1.3.6.1.4.1.714.1.2.6.1.1.0.
Hope this helps. 🙂
This would be excellent if it works, I’ll give it a shot. Thanks for the information. Where did you find the OID? I’m curious if there is a different OID to trigger a factory reset remotely using this method.
January 18, 2013 at 6:08 pm #23337@squirrel wrote:
@ab17182 wrote:
Just as a head’s up, you can also use snmpset.exe as it can also be used to reboot a list of WYSE thin clients or a single one as well. Download snmpset here [http://www.snmpsoft.com/freetools/snmpset.html] and install it. Then run the below cmd against a list of thin client IP addresses. PLEASE err on the side of caution when running this as it could be disruptive to end users if the incorrect IPs are in the list:
for /f %i in (c:tempthin_client_IP_addresses.txt) do @c:toolssnmpset -v:1 -c:SNMPWYSE -r:%i -o:.1.3.6.1.4.1.714.1.2.6.1.1.0 -val:0 -tp:int
The above runs snmpset against a text file which contains a list of IPs. The WNOS.INI has SNMP enabled along with setting the community string to SNMPWYSE [i.e. Community=SNMPWYSE]. The OID is .1.3.6.1.4.1.714.1.2.6.1.1.0.
Hope this helps. 🙂
This would be excellent if it works, I’ll give it a shot. Thanks for the information. Where did you find the OID? I’m curious if there is a different OID to trigger a factory reset remotely using this method.
I’m getting “%Failed to set value to SNMP variable. Timeout.” when testing this on a single client. I’ve set the SNMP community and it shows up correctly in the event log. I also tried explicity setting Service=SNMPD disable=no, but I assume it’s enabled by default. Any suggestions?
-
AuthorPosts
- You must be logged in to reply to this topic.