Legato 6.1.3 On NT4/W2K

[pepedekirda]

Hello,

Since our update from 6.0.x to 6.1.3 on our NT legato servers/clients we get name resolution problems. Our setup is to use WINS and our systems are not part of a DNS domain.
Several multihomed systems fail their backups periodically with the errors "RCP error : Unable to receive" or client : cannot revolve host to IP address ... .
At the OS base the network traces and other functionning services prove that the naming service is working correctly. It seems that the client itselfs fails to resolve its name toof its addresses ( mentionned in the error but not always the same one ). We did setup a DNS server to provide this service. Again the traces show the correct requests and answers going over the network, but the backups keep failing.

Any idea.

 

[LGTObug]

You could try to add your ip-address and Hostnames to the Clients HOSTS-file.
under Windows2000
c:\windows\system32\drivers\etc\Hosts

otherwise add the FQDN (full qualified domain name) to the alias names in the clients config under networker.

 

[pepedekirda]

Hello,

Thanks for the first answer. I will be more verbose about what I tried out already. First you have to understand that our systems are not part of a DNS domain and therefore do not have a FQDN.

- In this version of Networker, on all our Windows clients
we had to add in the hosts file an entry for each of the Networker server interface and add the corresponding name in the servers file. This was not necessary before because Networker used corectly the WINS multihome records.
One name per interface is not necessary in NT/W2K normally.
This workaound has been discussed with support and agreed.

- For the remaining problem that some clients give the error : upiter:SYSTEM STATE:\ save: error, Warning, cannot resolve host 'JUPITER' to 'xxx.xxx.xxx.13', name server may be misconfigured. Or sometimes the probe of the filesystems to backup gives the RPC error Unable to receive" we did several tests.

. Add all client interfaces in both the server and client hosts. No results.
. Add a DNS server in the list of DNS servers to use and configure it to be capable to resolve the client name and do the reverse lookup also.
. On the client add one of the client inferfaces in the lmhosts with the #PRE option to avoid the WINS multihomed records.
. Put one of the clients in a DNS domain .backup, setup the FQN aliases in Networker, configure a DNS server for this domains.

Nothing helped.

 

[mcurran1]

Do yourself a favor and use the hosts files....trust me we tried everything and this is the best solution.