Reboot Wyse V10L remotely

  • This topic is empty.
Viewing 15 posts - 1 through 15 (of 18 total)
  • Author
    Posts
  • #6142
    Brazil
    Member
    • Total Post: 54
    • Back Stage Pass
    • ★★★★

    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

    #19133
    Anonymous
    Inactive
    • 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|

    #19139
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    You can do this with my ConfGen tool from this site.

    CG

    #19145
    Brazil
    Member
    • Total Post: 54
    • Back Stage Pass
    • ★★★★

    Thanks 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
    WDM

    What 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

    #19146
    Anonymous
    Inactive
    • 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.

    #19148
    Brazil
    Member
    • Total Post: 54
    • Back Stage Pass
    • ★★★★

    Thanks,

    is there a guide where I can find out about these commands?

    #19149
    Brazil
    Member
    • Total Post: 54
    • Back Stage Pass
    • ★★★★

    Ok,

    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

    #19150
    Anonymous
    Inactive
    • 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.

    #19151
    Brazil
    Member
    • Total Post: 54
    • Back Stage Pass
    • ★★★★

    OK,

    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.

    #23037
    JCLyon
    Member
    • Total Post: 1
    • Newbie

    Config 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?

    #23062
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    For a reboot just send
    &V52&CI=59|RB=1 to the client. That’s all.

    CG

    #23203
    squirrel
    Member
    • Total Post: 18
    • Regular Joe
    • ★★

    @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?

    #23301
    ab17182
    Member
    • Total Post: 9
    • Regular Joe
    • ★★

    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. 🙂

    #23336
    squirrel
    Member
    • Total Post: 18
    • Regular Joe
    • ★★

    @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.

    #23337
    squirrel
    Member
    • Total Post: 18
    • Regular Joe
    • ★★

    @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?

Viewing 15 posts - 1 through 15 (of 18 total)
  • You must be logged in to reply to this topic.