- This topic has 6 replies, 2 voices, and was last updated 3 years, 2 months ago by
.
-
Posts
-
Got test 8.x client recognized by new WMS 3.2 server. Policy is from imported wnos.ini file. Synced bios pw (even though I can’t even recall setting a bios pw, someone in another thread on technicalhelp suggested this).
On reboot, seems like the client gets the bulk of the imported wnos.ini settings. But it refuses to let me logon in admin mode. I’ve changed the pw several times and published, rebooted the 3040 multiple times. No errors in sys info event log. I can even get Admin mode button to hide or show.
Also can’t force a remote restart from the WMS server either.
Suggestions? Thx again! : )
In most cases either the Admin Mode parameters are set in a wrong way, or you haven’t set the privilege level to low or none.
Post your config to verify.CG
On WMS it was set to ‘none’ already; switched to ‘low’, saved, rebooted client, same problem. But even if that had fixed it, surely that wouldn’t affect remotely restarting from WMS?
wms 3.2 security settings –
Try to use unencrypted password.
The typical reason for not being able to reboot the client via WMS is, that MQTT is not reaching the client and vice versa. Make sure that this is working.
This has nothing to do with your Admin Mode issue.CG
Thanks!
Turning off unencrypted password: still does not work.
Admit I know very little about MQTT. If it helps, this is an on-premises WMS with no internet access. I tried looking for MQTT settings on WMS, but the only reference I find in the manual points to
Portal Administration -> System -> Setup
and in my 3.2 console there, there is no sign of the ‘WMS URLs’ section – if that is relevant.
Just make sure your firewall is not blocking port 1883 which is used by the MQTT service running along with WMS.
CG
Nothing on the WMS server. I also spoke with my supervisor about our domain firewall policy as well; nothing should be blocked inside the ntework, but to guarantee nothing is blocked for purposes of this test, I moved it to a troubleshooting OU where there is no enforced firewall policy at all. Same problem.
- You must be logged in to reply to this topic.