Home › Forum › WDM and WMS › Win 10 (Wyse 5070) TC Not registering With WMS Via DNS
- This topic has 5 replies, 4 voices, and was last updated 4 years ago by
MoPositive.
-
AuthorPosts
-
August 28, 2019 at 9:00 pm #50683
I have Windows 10 TCs (Wyse 5070) that will not register with WMS 1.4.0.42077
WDA ver is 14.2.0.51
This is a new build. The TCs can ping the FQDN of the WMS server. I have added the appropriate DNS records (SRV and TXT). SRV records are in ._tcp and the TXT records are in the domain root
SRV
_WMS_MGMT, port 443, FQDN of wms server
_WMS_MQTT, 1883, FQDN of WMS server
TXT
_WMS_GROUPTOKEN , defa-GroupToken
_WMS_CAValidation , False
In the WyseDeviceAgent.Log I see the following error:
I 2060 6 Domain is unknown, DNS discovery can not be performed
I then see this a few lines further down
I 2060 6 DtcWDMAgentCore: Doing discovery with Method = DNS_SRV_RECORD
I 2060 6 DoDNSSRVRecordDiscovery: Entered DoDNSSRVRecordDiscovery
E 2060 6 DoDNSSRVRecordDiscovery: DNS SRV Discovery Failed
I 2060 6 DtcWDMAgentCore: Doing discovery with Method = DNS_HOSTNAME
I 2060 6 DoDNSHostnameDiscovery: Entered DoDNSHostnameDiscovery
E 2060 6 DoDNSHostnameDiscovery: DNSHost Discovery FailedAny thoughts on why these TC cannot register via DNS lookup? I can register them manually without issue.
September 13, 2019 at 12:15 pm #50736Can you ping the WMS server FQDN name that you have used with your DNS entry from the client?
CG
September 13, 2019 at 3:35 pm #50745Yes, i can ping the FQDN of the WMS server from the Thin Client. I can also perform an NSLOOKUP and see the records.
Also of note, the TC is not a member of a domain
I have also tried using an alias of WMS and WDM for the server in case the software was attempting to lookup those names.
September 14, 2019 at 5:07 pm #50753When you verify locally on the client’s WDA settings, does this reflect the correct WMS settings?
CG
September 20, 2019 at 9:35 am #50792Hi,
as a “non Domain-Member”, could it be that your DHCP Server is not handing over the correct Domain-Name… (Domain Members will pick it up during Domain-Join)
e.g.:
DomainName: domain.local
DHCP hands over “nothing” and though WDA will look for “_WMS_MGMT” in the assigned DNS server and NOT for “_WMS_MGMT.domain.local”
Regards
Volker
October 2, 2019 at 6:32 pm #50862Agree with VNad, the issue is most likely that the DNS suffix handed out by the DHCP server is not the same as the domain where you set up the SRV records. Run IPConfig on the thin client and note the Connection-specific DNS Suffix, does it match the domain where you set up the records?
-
AuthorPosts
- You must be logged in to reply to this topic.