Hi,
We have multiple devices located in different countries with a webinterface inside the connector. Dataminer server has access to all those devices but when a user from Country 1 wants to connect to a device in Country 2 the webinterface doesn´t work due to the network restrictions from the client machine.
Is there a way to overcome this ? Would a Visio be able to open the webpage from the DMA server and work properly (logins, button clicks, etc) in the client ?
Thank you in advance.
Kind regards,
There’s no build-in functionality in DataMiner for this.
In the IIS web server on the DMA server you could set-up a reverse proxy server that directs those http requests to the device. In the DataMiner connector you should then configure the url that goes through that proxy which users can access.
Hi Ben,
Thanks for your reply.
We have this issue at the monment and we cannot allow traffic between the two territories due to some network overlapping and security issues. However, DM is hosted in AWS and have acess to both networks and we need the engineers in one territory to access the devices web interfaces that are on the other territory.
@Wim,
Thanks for the details.
We have tried to enable the Reverse Proxy but it did not work. We also were unable to access the DM Cube after enabling the proxy. Not sure if we have done the right config. Do you have more details on how would be done on a DMA?
The reverse proxy should be configured on a subfolder or a separate port so that it doesn’t impact the DMA communication. You don’t want to proxy the DMA communication to that device. Safest approach would be to create a new web site in IIS on a different port, and configure the reverse proxy there.
Question is if you really want that. If client X cannot access the web interface of a device on location A, then I guess this is on purpose. Setting up a proxy through a DMA is technically possible, but isn’t that like punching a hole between two networks that are intended to be separated? If it is desirable to have client X access the web interface of a device on location A, isn’t then the proper solution to simply configure the underlying network to accommodate that rather than blocking it?