- This topic has 20 replies, 8 voices, and was last updated 4 years, 3 months ago by
.
-
Posts
-
Testing 8.5_012 on our 5010s w/ PCoIP, and, upon bootup, we get this cert error pertaining to our WDM server (provided to our terminals via DNS A/SRV records). The removed text is the IP of the WDM server:
We weren’t getting this with any firmware even up to 8.5_009. We provide a cert for our local CA which the WDM server is registered against, so, I’m not sure what’s changed or what we should be doing differently. If I add SecurityPolicy=low to my wnos.ini, I can click continue and it won’t pop up again, but, obviously I’d prefer not to go that route.
Same issue here. Glad that we are not alone 🙂
We go for securitypolicy=low
I opened a ticket with Dell. I’ll post any updates/resolution.
We have ours low, but have it locked down. This is what we do for both our internal and external users. I know you do not want to do it low, but if you lock it down and use a Admin password, then you should be fine.
same issue here, our Certificate is now longer working, fine with 8.5_009 and lower
No. I opened a ticket with support, who has since escalated/opened a new ticket above them. I have not had an update so far.
Update:
Was provided the 8.5_017 firmware from Dell (should be out soon). However, no luck, I am still receiving the cert error.
The line blanked out is the IP address of our WDM server, which our terminals are provided via DNS A and DNS SRV records. Nothing within our ini. Nothing about the certs has changed, and all terminals on the 8.3_109 remain fine.
I think we are on to something for our site at least.
We have defined a DNS A and SRV record for the WDM server (we didn’t use DHCP option tags). When a terminal boots up, it attempts to check in via the SRV record, and it’s being provided the IP address of the server. Not the FQDN. It seems like in 8.5+, the SSL check is choking on the mismatch between the cert common name, and the provided IP. We’re thinking our SRV record needs to be fixed to return the FQDN and not the IP. I’ve asked my DNS guy to provide the SRV record details, and we’re going to proceed from there.
We have a similar issue with WMS.
The certificate is pointing to an alias, but the thinclient is trying to do an nslookup. Will try to checkin with the hostname and than gets a certificate missmatch error:
WMS Agent failed to open HTTP Server, failed to switch to https://…..
Apparently Dell forgot to add the fix to 8.5 HF3 release. Having hte same with 8.5_017 build preview. Not using WDM/WMS.
- You must be logged in to reply to this topic.