• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 245
  • Last Modified:

Prevent Notes Client's access to another server with a replica


We have a distributed Domino deployment. We have a WAN connecting our different offices. There is a domino server at each location and the data is replicated at a set interval over the WAN.

One problem we have is that whenever a client is not able to access the Domino server specified in the document (because the server may not be available temporarily), it tries to connect to other servers and tries to find a replica copy of the database on it. Since we have a WAN and the replica copy is available, the User starts working on the database hosted at the remote location without realising that he is doing so. Obviously the performance will be slow on the WAN link as the bandwidth is limited.

We wish to find a way to prevent Notes Clients accessing another server when opening the database. Basically, lookup redirection doesn't happen during database Open event.

Thanking you in anticipation,


3 Solutions
You can limit of the access of the users to the servers ...i.e Server of Location A ...list who call can access the server, do the same for all location. So this will prevent the user of location A to access the database on server B.

Sjef BosmanGroupware ConsultantCommented:
It's standard Notes behavious, and very hard to block in such a way that the user won't start complaining.

Read the following documents:
- http:Q_21299899.html "Don't connect to a replica"
- http:Q_21138685.html "Database Links do not point to the desired domino server but to another domino server which contains a replica of the database"
Is this for when a user clicks a link in a document?  Or when a user opens a database from the workspace?  or when a user opens a bookmark from the user bookmark bar?

Each of these three behaves lsightly differently.  The workspace only fails over automatically when in a cluster, but if it does fail, it will ask teh user where to hunt.  The user is given the chouce, and you can't block it.

Links will automatically try to find an alternate source.  It will try both the "hindted" server (whichever server the original link was created on), and all servers listed in the catalog as containing a copy.  Faling all that, it will prompt the user, as in the workspace.  You can cut down on some of this by not having a global catalog, though there are some trade-offs in doing that.

What you CAN do is create groups that list which users should be able to access which servers altogether.  Put those groups in the allow access list for the servers, and users will not be able to access the long-range servers at all.  Make sure to include all servers as being able to access each other, as well as all admins.

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now