Issue:
Need to set up access to multiple Domino servers via one externally available Domino server.
This has to be done in two parts.
- Before folks can take advantage of this Domino feature, the Domino administrator has to set-up the server's to allow it on the Domino servers participating in this feature.
- Once this is completed, the end users can update their workstation configuration to passthrough the "front" server to all the others behind it.
In our example:
- Front/external server providing passthrough: DomFront/MWNet
- Behind/internal server getting access: DomBack/MWNet
- Group of People who can use Passthrough: zMWNetPassthru
We are going to make our changes on the "primary" or "Domain" domino server. This is typically the first and primary Domino server. In this example, the primary server is DomFront/MWNet. It has a gold key on its server icon where the other Domino servers do not.
Part A: Domino server set-up:
(Performed by the Domino administrator)
1. Connect to the management Domain Domino server:
- Domino Administrator (client) --> MWNet Domain (left side bar icon) --> DomFront/MWNet
2. Update the front Domino server document for DomFront/MWNet to allow passthrough access:
Configuration (tab) --> Server (left menu twistie/category) --> All Server Documents (left menu view) --> Open DomFront/MWNet server document
In the server document, click Security (tab), scroll down to the Passthru Use section.
Update the following:
- Route through: <add> zMWNetPassthru
- Destinations allowed: DomBack/MWNet (or LocalDomainServers, if you want to make all the other servers available, too)
Click Save & Close
3. Update the behind Domino server document for DomBack/MWNet to allow passthrough access:
- Configuration (tab) --> Server (left menu twistie/category) --> All Server Documents (left menu view) --> Open DomBack/MWNet server document
In the server document, click Security (tab), scroll down to the Passthru Use section.
Update the following:
- Access this server: <add> zMWNetPassthru <and add> DomFront/MWNet
Note:
- There was an old Domino release that had a bug where the secondary server needed to be set Route through, even though this was the final destination. Some of our really old Domino servers have the same values in the Route through field, too.
Click Save & Close
Part B: Notes client set-up:
(Performed by the Domino administrator remotely, or a Notes power user)
1. Open the Notes client, login, and open the local Contacts app:
- Notes (client) --> <login> --> Contacts (left side bar icon)
2. In the Contacts app, open the Connections view:
- Advanced (left menu bottom link) --> Connections (left menu)
Notes:
- At this point, the directions may diverge. In an internal business network, the Person's "home" mail server will automatically give that Person the destination Domino server and often the Notes client will automatically create a connection document. So if the app on the behind server has already been used, the connection document will likely already exist and need to be updated. If the connection document does not exist we'll create it. For this example, we are going assume the connection document doesn't exist, but just edit one if it already does exist.
3. Create the behind connection:
In the Advanced\Connections view, click New --> Server connection
On the Basics tab, update the following:
Under the Basics heading,
- Use LAN port: TCPIP checked/enabled
Afterwards, change the field:
- Connection type: Passthru Server
Now unhidden, change the the field:
Passthru server name or hunt group name: DomFront/MWNet
Under the Destination heading,
- Server name: DomBack/MWNet
Click Save & Close
Additional Notes:
At this point, the connection will work.
- If this Notes client workstation is carried back into the internal workplace, this Notes client will still talk through front passthrough server rather talking directly to the behind server. This might slightly slow that communication down enough to be noticeable to the user. If so ...
- - One way to address this is creating two connection documents, one for internal and one for external, and making two location documents which each using one of the connection docs, that way the connections can be toggled w/o actually editing them.
- - Alternately, the passthrough connection can be edited when on the internal workplace network and change the connection priority from "Normal" (Advanced tab) to "Low", and connection will not be used. The home mail server and the local DNS will be used instead.
previous page
|