We have a Domino-network in an international environment protected by a VPN-solution. To enter the VPN (from an external location) the user must enter a security-key. As long as they have connections to ip-adresses on their “home”- network everything is OK. If they try to open a connection to an ip-number in another network (behind another FW in the same VPN-environment) they are being prompted for the security-key again.
This is OK as long as the user him/herself active to go to another location (file, database open, etc). But this is not okay when it’s not an active decision by the user (e.g. the replicator in Notes is trying to reach all the different servers in the same Notes Named Network). The user don’t understand why they must enter the same security-key several times in a row…and at several times every day. Then they call Helpdesk…and complain.
I know we could reduce the security in our VPN-configuration (accept access to all locations when entering the security-key the first time) or open the replicator page on all clients and change the replication-settings for all local applications. But is there a way to stop the client from connecting to all “unknown” servers (being servers with no icon on the workspace) in the same Notes Named Network (e.g. a notes.ini setting like DisableNNNLookup=1)? If there is a way of doing this - is it any caveats?
I know we could reconfigure our Domino servers to not have the same NNN’s, but that is not an option.