Wyse 5070 Failed to Connect to MQTT Server

Viewing 12 posts - 1 through 12 (of 12 total)
  • Author
    Posts
  • #52131
    strattosa
    Participant
    • Total Post: 4
    • Newbie

    I have a 5070 with Win 10 Ent 2016 LTSB (Image Version 10.03.06.11.19.00) and WDA version 14.4.3.5. WMS Server v2.0 – I get the error “Failed to connect to MQTT server fleetwms:1883”
    I can telnet the server on this port and I can see via netstat the connection established, which means that MQTT service is running and listening to MQTT connections.
    If I do not restart the device to check in all the commands sent to it stay in the queue.
    This is fresh WMS installation.

    I have seen a same case with WMS 1.3 reported in this forum but since I have WMS 2.0 I wrote this post again.

    P.S. I cannot go to a newer OS version since I am running some troubleshooting cases with DELL support but I don’t believe that this is related to the TC’s OS version in any case.

     

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

    Could you open a Powershell command and enter
    Test-NetConnection -ComputerName WMS_FQDN_IP -port 1883 -InformationLevel Detailed

    Do you have TcpTestSucceeded : True or TcpTestSucceeded : False?

    CG

    #52139
    strattosa
    Participant
    • Total Post: 4
    • Newbie

    I guess you want me to run the PS command from the TC towards the WMS server. Correct?

    Or do you want to run it locally on the WMS server running the MQTT broker?

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

    Yes, from the client or a PC attached to the same port as the client towards the WMS server.

    CG

    #52141
    strattosa
    Participant
    • Total Post: 4
    • Newbie

    TcpTestSucceeded: True

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

    Then obviously the client CAN contact the MQTT server.
    The problem must be somewhere else.
    Have you checked with a network trace, if you can see anything in there?

    CG

    #52160
    strattosa
    Participant
    • Total Post: 4
    • Newbie

    I managed to solve this.
    When IPV6 was enabled on the WMS server-side MQTT commands were never reaching the NIC. Wireshark could not trace anything MQTT related.

    Disabling the IPV6 on the NIC of the WMS Server brings everything back to normal.

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

    Good finding. Thanks for sharing.

    CG

    #52768
    fmcc
    Participant
    • Total Post: 10
    • Regular Joe
    • ★★

    same issue here. but WMS is hosted on us1.wysemanagementsuite.com. how can I disable ipv6 there?

    Scheduled an image update for a 5060 at a remote site. machine got the command, clicked update on thinclient (via VNC) and then lost all connected. Failed to Connect to MQTT Server is the last event I see on the wms portal.

    #52775
    jamesjhughes
    Participant
    • Total Post: 22
    • Regular Joe
    • ★★

    MTQQ for the US public cloud is

    us1-pns.wysemanagementsuite.com:1883

    Make sure the device can get to this (and your repo server).

    #52793
    fmcc
    Participant
    • Total Post: 10
    • Regular Joe
    • ★★

    thanks a lot james.

    #107313
    Rockhard
    Participant
    • Total Post: 3
    • Newbie

    I am also having this issue, but I am on-Prem

    When I run the PowerShell command from up above, I get the answer: FALSE, with a warning Name Resolution of WMS_IP:1883 failed.  Same answer using the FQDN, or IP Address of the WMS Server.

    The 5070 does receive Updates such as WDA, Wyse Easy Setup and Merlin through WMS, but does not seem to want to pull or push an image.

    Any ideas?

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