lalehgol
asked on
Legato Networker 7.4.2 Backup
Hi,
One of my server client stop connecting to my backup server. no changes.
I can ping the BA server og like vise. I get Error on my BA server at "Hostname resolution failed". I have reinstalled networker.msi on server again but it did not helped. This is a Windows 2000 server and backup worked without any problem before.
please let me know if you need more info.
One of my server client stop connecting to my backup server. no changes.
I can ping the BA server og like vise. I get Error on my BA server at "Hostname resolution failed". I have reinstalled networker.msi on server again but it did not helped. This is a Windows 2000 server and backup worked without any problem before.
please let me know if you need more info.
ASKER
Thank you for fast feedback.
I have check the DNS with on server that works fine and they are the same. where should it examine my DNS configuration?
I have check the DNS with on server that works fine and they are the same. where should it examine my DNS configuration?
Try 'nslookup [IP.of.failing.client]' on your BA server and see what you get.
Note that you'll have to use the IP address (xxx.xxx.xxx.xxx) of the client, not its name.
Should you get 'Non-existent host ...' from the above, you'd have to check the tables configured on your DNS server itself.
wmp
Note that you'll have to use the IP address (xxx.xxx.xxx.xxx) of the client, not its name.
Should you get 'Non-existent host ...' from the above, you'd have to check the tables configured on your DNS server itself.
wmp
ASKER
I get the right name back from my BA server.
Just to be sure - you are logged in at your BA server, start a CMD window, issue the above nslookup and get a valid hostname back when querying the IP of your failing client?
ASKER
Yes, that is correct:-)
Well,
... and the similar procedure works on the client, too - doing nslookup for the BA server's IP?
If this is the case, I admit I will have to do some research, as DNS configuration errors I mentioned in my first post are the most common (and usually the only) cause for "Hostname resolution failed".
I assume your BA server doesn't get a non-static IP address via DHCP?
wmp
... and the similar procedure works on the client, too - doing nslookup for the BA server's IP?
If this is the case, I admit I will have to do some research, as DNS configuration errors I mentioned in my first post are the most common (and usually the only) cause for "Hostname resolution failed".
I assume your BA server doesn't get a non-static IP address via DHCP?
wmp
ASKER
Nslookup from client site is giving the right name too.
No, it does not get non static IP.
No, it does not get non static IP.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
it seems thet the reverse lookup table of your DNS accidentally doesn't contain the address of your failing client anymore.
Examine the DNS configuration for errors/missing entries.
HTH
wmp