Does anyone know if there is a way to force a server to read an IP address for another server from that servers’s server doc? ie without a connection doc between the 2. Currently Trace Server by name fails, but by IP address works. There are no DNS or host entries, and we were hoping to avoid having to set this up and keep it up to date, also want to avoid creating connection docs to a long list of servers as we are using a group for replication to all servers from a hub which really tidies up the address book. Many thanks in advance
Subject: Console message
Bearing in mind there are NO connection docs between the 2 servers other than a group one the points to a Server group…
If I type Trace on the server console, it finds it by doing the following:
Determining path to server
Availablle ports TCPIP
Checking normal priority connection docs only
allowing wild card connection docs
Enabling name service requests and probes
Checking for on TCPIP
is the adress of
Connected to
But if I trace by server name I get:
Determining path tpo server
Available ports TCPIP
Local network connection doc found for
Verifying address for on TCPIP
Requesting IP address for server name from DNS
DNS did not return an IP address for
Unable to connect to on TCPIP (The remote server is not a known TCP/IP host)
Unable to find any path to because The remote server is not a known TCP/IP host
THe server IP addtress is definitely listed on the server doc - is there something I am missing to get it to check there…??
Subject: Depends on which domain
If I remember correctly, if both servers are in the same Domino Domain then when they try to contact each other, the first thing they do is look at the information in the ports → Notes ports section of the server document and then use the information there (common name, DNS name or IP address). If there is a common name or a DNS name in there, then they use the OS to resolve that name. If there is not server document then they look for a matching connection document and, if one is not present, then they try the OS based on the server’s common name.
TRACE from the server console will let you see how one server is trying to contact another.
HTH
Melissa
Subject: In the same domain
Hi Melissa
and thanks for your reply. The servers are all in the same domain and the server docs are all populated with the server IP address in the Ports section. They have VPN tunnels between them, but they cannot see each other to replicate unless I create a connection doc for this with the IP address on. I thiought exactly the same as you, so am stuck now - any other ideas?
Subject: maybe by using Fully qualified Internet host name
The server does not use the information on the Ports tab for replication as far as I know. You might have more success with filling out the IP address in the Fully qualified Internet host name field on the Basic tab.
Other than that you need either connection documents, a local hostfile or DNS entries.
Hans
Subject: Fully qualified Internet host name doesn’t work
Hi Hansand many thanks for the suggestion. Unfortunately this doesn’t work either, so it is going to have to be connection docs. As we have over 100 servers it would have been great to just use a server group name for replicating and just have the one doc, but don’t want to rely on keeping the hosts or DNS up to date so connection docs it will have to be