- This topic has 5 replies, 2 voices, and was last updated 3 years, 10 months ago by
.
-
Posts
-
Is it possible to have devices connected to an on-premise version of WMS 3.0, free version?
I have it set up working internally with devices connecting fine. With an external DNS and ports forwarded to the server, devices won’t communicate. Could I be missing something or does only the paid for version support this?
Thanks for any advice.
Yes, this is possible.
Make sure
1. the FQDN is globally accessible
2. port 443 is forwarded
3. port 1883 is forwardedCG
Thank you! We name our servers using a convention based on purpose and server version and then use DNS aliases so that when we upgrade servers we just remap an alias rather than having to change a setting in a device.
Anyway, after clients were pointed at WMS using the DNS alias, they would then get the true name of the server and try using that which is where things were breaking.
Your reply gave me the confidence that it should work and last night I resolved the issue, so we’re happily running now. Thank you!
Check the WMS troubleshooting guide in my Downloads. This will show you how to pass back the desired name instead of the real name.
CG
Thanks very much for that guide. I may have a go at renaming the server back to our convention and redo the aliases over Christmas. Thank you very much again!
- You must be logged in to reply to this topic.