1) If you make configuration changes on one server and each of your servers has its own copy of the website files, the changes will be seen only on the server you make the changes. This is why it is recommended that for NLB solutions to set the storing of configuration files to database.
2) When you define the webserver paths for each node in the NLB environment, make sure that that the nodes can communicate between each other and that the MSMQ messages to the respective nodes are not blocked by a firewall. The addresses of the nodes are needed to make sure that each server has the latest version of your items cached. So for example when you edit and publish a page the server that you made the change on messages the rest of the servers over MSMQ to invalidate the cache dependency for this page, and make sure that when the page is requested on a node in the NLB the proper version of the page is returned. If you edit a page on one server and the the page is not updated on the rest of the servers, after you have configured NLB settings, this means that either the configuration is not applied on all servers, or something is preventing the servers from communicating with each other.
3) The second level cache of the ORM does not work under NLB. For this reason we automatically disable it when you configure the website to run under NLB.
All the best,
the Telerik team
Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking
system and vote to affect the priority of the items