Unable to find path to server

Hi,we set up a new server in Singapor called MAIL/COMPANYSG/SG. We cross certified it with our server calle IFH/COMPANY/DE. I set up a connection document an we can exchange mails. The new server also can replicate with our server here, but we can not replicate with the new server. I always get “Unable to find path to server MAIL/COMPANYSG/SG”.

but when I make a trace on the Notes console either

trace MAIL or

trace MAIL/COMPANYSG/SG

i get a wonderful

Network: Determining path to server MAIL

Network: Available Ports: TCPIP TCP_CLS

etwork: Checking normal priority connection documents only…

Network: Local network connection document found for MAIL/COMPANYSG/SG

Network: Verifying address ‘…246’ for MAIL/COMPANYSG/SG on TCPIP

Network: Using address ‘…246’ for MAIL/COMPANYSG/SG on TCPIP

So, why can I not replicate? I’m I missing access rights on the new server and just get a “wrong” error message?

I’m clueless, thanks for any ideas.

Oliver

Subject: Unable to find path to server

what do you see in the log file or on the console when you try to force replication??

Shawn

Subject: RE: Unable to find path to server

Unfortunatly, the log just shows nothing. But what I just found is, that I can replicate from the console. When I enter

replicate MAIL/COMPANYSG/SG names.nsf

it replicates. But when I start from the client with

File - replication - New replica

enter the Severname I get “Unable to find path to server”

How strange is this?

Thanks

Oliver

Subject: really strange

When I setup a connection document in my personal address-book to this server, replicating works. Is there a client setting, how to use the server connection documents?Thanks

Oliver

Subject: Not really strange

Oliver,

This is not strange at all, it all has to do with TCP/IP communications between the machines involved.

To communicate with IP via hostnames the host name needs to be resolved to an IP address, you have given the client the ability to do this by creating the connection document at the client, another way to do this is via a DNS or host file entry for the servers host name. The server already had a connection document so it could resolve the name. I would recommend adding a DNS entry for the new server so you don’t need to create connection documents in all clients you need to access it.

Hope this helps

Danny

Subject: RE: Not really strange

Thanks for the info,but how do I setup a DNS for a Notes-Server. The Address is

MAIL/COMPANYSG/SG

What do I enter into my DNS then? Only MAIL? But there might be serveral servers called MAIL (I have one). I can not enter shlashes “/” into W2K-DNS, so I’m really not sure how I could do this.

Thanks

Oliver

Subject: RE: Not really strange

Oliver,

You add an “A” record to the DNS domain that the host is a member of. Membership is defined at the host OS level and the DNS domain name is either asigned statically or via DHCP.

If you are using 2k or 2k3 you can optionally check to register the computer in DNS.

Once you create that record you should be able to ping hostname.domain.com

hth,

Shawn

Subject: RE: Not really strange

Hi,

in your local names.nsf there are all Informations the client needs.

Take a look at the fields of the current locationDocument:

$SavedServer

$SavedAddress

etc…

see

http://www-1.ibm.com/support/docview.wss?uid=swg21094111

If you open the server in singa. via the tcp/ip adress the first time, everythin gwill be fine. Maybe an old Information ist stored int the local nab.

Good Luck

Torben