Unsolved
This post is more than 5 years old
1 Rookie
•
28 Posts
3
25784
November 6th, 2009 06:00
Name is not a valid hostname
We have created a new client with the FQDN as client name. The alias was the short clientname. Then we decided to rename this client with the short name, so we deleted the original one and tried to create the new client with the short name. However, NetWorker comes back with:
Name is not a valid hostname
Then we tried to create the original client again with the FQDN. Now it states, that it
Found alias: client map using client id: xxxxxxxxx
If renaming client: specify this client id.
Otherwise, re-apply to create a new client id
Whether we re-ally or we put the "old" client id in the "new"client, we always get:
Name is not a valid hostname.
We already removed all old index entries and all we could find in relation to this client, but it always fails. Network connections are fine: nslookup, rpcinfo and ping from both sides (client and server) work well.
Now we cannot backup this client. What can we do to solve this problem?
Regards,
Name is not a valid hostname
Then we tried to create the original client again with the FQDN. Now it states, that it
Found alias: client map using client id: xxxxxxxxx
If renaming client: specify this client id.
Otherwise, re-apply to create a new client id
Whether we re-ally or we put the "old" client id in the "new"client, we always get:
Name is not a valid hostname.
We already removed all old index entries and all we could find in relation to this client, but it always fails. Network connections are fine: nslookup, rpcinfo and ping from both sides (client and server) work well.
Now we cannot backup this client. What can we do to solve this problem?
Regards,
No Events found!
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
November 6th, 2009 08:00
HCLBACKUP
2 Intern
•
150 Posts
0
November 9th, 2009 08:00
Anonymous User
1 Message
0
November 6th, 2012 22:00
I got the same error. Full message:
"Unable to connect to host. Please check networker security settings. Unable to dtermine the name of 192.168.15.142. No such host is known."
(where 192.168.15.142 was the IP of the Networker Server machine.)
My setup
Networker 8 Server on CentOS Linux
Networker Client on Windows 7
Windows Server 2008 R2 for DNS services
My solution
1. Set up DNS names for both. Check that ping in terminal/command prompt works on both machines
2. Set up Reverse look-up zones on the DNS server. Check that it works by going in to each machine and running command nslookup
3. Restart the Networker Server machine (I got other errors before restarting, but after that it worked).
Bebo2k
544 Posts
0
November 7th, 2012 12:00
Hi Harry,
This is name resolution issue , and most probably as the previous replies mentioned it is reverse lookup issue, but i would like to add another recommendation which is deleting the nsr peer information from the client and server, Please follow the steps given below to delete the NSR peer information on NetWorker Server and on the Client.
nsradmin -p nsrexec
print type:nsr peer information; name:client_name
delete
y
(specify the name of the client in the place of client_name)
nsradmin -p nsrexec
print type:nsr peer information
delete
y
This is an additional recommendation beside the naming resolution investigations that is needed specially the reverse lookup.
Hope this helps,
Ahmed Bahaa
Allbertik
1 Rookie
•
38 Posts
0
February 9th, 2017 02:00
We have this problem too:
Name 'lexserv26clst.bashneft.ru' is not a valid host name.
NetWorker version 8.2.3.7
Client version 8.2.4
edino1
39 Posts
0
February 9th, 2017 03:00
Verify if DNS or hosts file has entries for that hostname. If yes then you have to flush NW's DNS cache by command "dbgcommand -p FlushDnsCache" or restart NW server. After that you should be able to create client.