I get this error message10/16/2009 03:57:29 PM Error connecting to server Domfppq3/FPPQ: The remote server is not a known TCP/IP host.
10/16/2009 03:57:29 PM Notes Traveler: SEVERE *system failed to open mailbox db on CN=Domfppq3/O=FPPQ
after the installation of Traveler
note that Domfppq3 is the Domino Server where Traveler is installed (so, itself)
Any help will be appreciated
Subject: How to “Fix” - “Error connecting to server” in Traveler 8.5.1
Hi Charles,
I’ve done a few upgrades in the last few days and have encountered this error.
The common thread between the servers that have displayed this issue - and the servers that don’t - appears to be linked to the “fully qualified internet host name” field in the server document, and whether it is the same as the “Full Computer Name” - FCN of the host.
Fully Qualified Internet Host Name is found on the “Basics” tab of your “Server Document” in the Domino Directory:
Full Computer Name is found under computer properties:
EG:
Windows Host:
domsvr1.mydomain.local
FQDN:
Is a machine that has the error, while:
Windows Host:
FQDN:
is fine.
The obvious solution is to ensure that the FQDN of the Domino server matches the windows host (Note: This is also a similar issue to that encountered with the stbroadcastgateway problem documented else-where), however this is not always possible. This is especially the case where a server behind a firewall is receiving network traffic relayed from a “real-world” address to an internal host.
The easy fix.
Rule No: 1 - The COMMS Rule. If the OS Can’t see it - neither can Domino.
EITHER:
Fix your internal DNS so that machines on the Internal network resolve “traveler.mydomain.com” to the Traveler machine’s INTERNAL host ip address, OR
Edit the Hosts file on the server to include the FQDN of the Domino server and it’s local IP Address (ie: 192.168.1.1, NOT 127.0.0.1).
A combination of the above has resolved the issue for me during a number of installs.
Hope this helps,
Mat
Subject: How to “Fix” - “Error connecting to server” in Traveler 8.5.1
Excellent post Mathew even if it was 12 months ago. I would like to add a couple more keywords as I did not find your post easily.
Initially try testing traveler by using a browser instead of a phone. If you get the following errors:
On the Domino console:
“sync session does not exist for this user”
and also
“error on opening database path”
Returned to the user’s browser:
“the lotus notes traveler server encountered an internal error validating your user id”
Refer to Mathews post (above)for solution.
Subject: I’m getting the same error
With a fresh install of Domino 8.5.1 on Windows Server 2008 R2 Standard.
Basically, after getting the server up and running, then shutting it down, then installing Traveler. Re-starting server results in the same errors you cited.
I have a feeling intervention w.r.t. names.nsf is required, going to try opening up the ACL.