obviously 192.168.0.111 is my ip of weblm but you can use the FQDN, the important bit is the port 52233 and the /WebLM extension on the end of the address.
We've got 3 AES pairs throughout our company and WebLM is working just like above fine. However, one of our pairs just starting throwing a similar error (generally it is a Timeout Error for the page). Haven't figured out what is causing yet.
When I checked the service Controller page I see this " Application Enablement Service is not licensed in the license file". Is this related to the WebLM page issue?
Some releases have a bug where the files are not startable in the directory, and you need to specify the exact file.
404 is just a "cannot find the page" html notification.
In answer to your question yes you do need weblm loaded as a OVA on your hypervisor , good advice from Soundslikethe network , i assumed you had already deployed this.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.