Unsolved
This post is more than 5 years old
4 Posts
0
2005
Name resolution failed for the host with IP address: n.n.n.n
Can not figure out what's wrong. This particular client is newly created and has no backup earlier. Every time I try to start a backup from it, it always ends with the error mesage "save: error, Name resolution failed for the host with IP address: 10.161.88.3".
Have record the name in the Hosts file on both the client and the server, the long one as well as the short. Have also double checked the servers file on the client. Have emptied the temp folder on both the client and the server and restarted the services. Nothing seem to work.
I can ping the server from the client. Ping also works from the server to the client. Both with the short or the long name.
What more can be done?
Have record the name in the Hosts file on both the client and the server, the long one as well as the short. Have also double checked the servers file on the client. Have emptied the temp folder on both the client and the server and restarted the services. Nothing seem to work.
I can ping the server from the client. Ping also works from the server to the client. Both with the short or the long name.
What more can be done?
vsemaska
194 Posts
0
July 1st, 2007 13:00
Did you double check the name of the client defined within NetWorker?
Vic
SteBol
4 Posts
0
July 1st, 2007 14:00
Yes, I even did recreate the client definition once. Also installed the client package once again. I'm beginning to think that the message is misleading. It may be something else than the name resolution but I can not figure out what.
The server is in the bol.internal domain and the client in the boliden.internal domain. Both can ping each other, with the short as well with the long names. So that's not a problem. Why I always get this "name resolution" error is strange, thats why I think it may be something else.
Sten
benzino1
244 Posts
0
July 1st, 2007 22:00
Could you please provide the information if the CLIENT is multihomed (multiple NICs) ? I've seen such behavior when the routing table on the client side is set in such way that the communication with NW server is done via different NIC than that defined as client resource.
SteBol
4 Posts
0
July 2nd, 2007 02:00
The client uses two NIC's in a team (Broadcom, BASP Virtual Adapter) with only one IP address (Smart Load Balancing). We use this config on several clients without any backup problems.
Any more suggestions on that?
benzino1
244 Posts
0
July 2nd, 2007 02:00
1. hostname
2. cat /etc/hosts
3. ifconfig -a
dpinink_silva
724 Posts
0
July 2nd, 2007 13:00
DougEFresh1
4 Posts
0
July 11th, 2007 11:00
Also check that there is an entry in DNS for the client in question.
jcastanuella
23 Posts
0
July 11th, 2007 15:00
First what is the OS of the Client. If Windows OS the binding order of the nics should have the nic with the IP address you are using bound first.
Verify the name of the client server. In windows the computer can have a short and long name (not including the domain name) Verify the long name of the client server is used first in the host file. Your host file entries on both servers should be in the same format. Ie
IP address long name short name domain name>
verify the host file entry is correct (no typo's)
If there is a storage node involved be sure it has a host file entry for the client server if you are using its media devices. Also be sure the client server has a host file entry for the storage node.
Leave the servers file blank (no entries)
Try to backup from the client side. If this works then this helps narrow down the problem.
Do the nslookup suggestion as posted by someone else.
Also try rpcinfo from the backup server
try recreating the client with the short name, if that doesn't work create it with the long name.
Be sure the client software was installed with admin rights.
fjsacristan
159 Posts
0
July 12th, 2007 09:00
Is there between the server and the client any firewall?
Inma.