Here is environment:
1 SQL Server with DNN DB
2 IIS Servers with equal DNN Portals installed connecting the same SQL DB
DNN Portals are accessed through a network balancer that relays the requests to the IIS with less connections so we have a balanced number of connections in both IIS Servers.
A user makes an update on an HTML Module using the Edit Content > Save buttons.
Only the content in the users actual DNN Portal is updated, the other DNN Portal (other IIS Server) isn't updated immediatly for all Portal users (only some users).
The Workaround I have to bypass the problem is by logging in to the other IIS Server, access with http://localhost and force the module update.
Since the DB is the same, shouldn't the content of the module be updated in both DNN Portals since one of them did an update?
Is it a caching problem? How can I change the environment so when an update is made on one DNN Portal and the other automatically assumes?
Thanks in advance,