When the Client is being added in Client Management, an error message appeared that the Client wasn’t responding; even though the NetVault Services on that Client are running and the Security tab in the NetVault Configurator has been setup to be added to the Server.
The NetVault Server and all NetVault Clients have been given enough ports for NetVault and SmartDisk within the Firewall tab on their Configurator.
We also performed the following network commands to make sure that the communication was working in both directions:
a] From server: ping of client hostname, nslookup of Client IP Address and name.
b] From client: ping of server hostname, nslookup of Server IP Address and name.
c] From Server CLI: telnet [IP Address from Client] 20031
d] From Client CLI: telnet [IP Address from Server] 20031
For more information on this topic, please see the Administration Module 1 Introduction to NetVault Backup-Web-based Training
The DNS Server was running for the name resolution, but we also amended the hosts file on the NetVault Server and Client to include its own name and IP Address as well as opponent machine; but still we couldn’t add the Client.
All the Firewall IPTables on the NetVault Server and Client were stopped as well. Here was the command we used:
bash /etc/init.d/SuSEfirewall2_setup stop
We removed all the Firewall port ranges from the NetVault Configurator – Firewall tab on the NetVault Server and Client; as well as stopping the SuSE Linux Firewall Service to make sure that there were no restrictions. Again, we still couldn’t add that Client.
We did notice that when we added the IP Address in Client Management that the name of the machine that NetVault Server could find was the incorrect name.
It was odd that the forward and reverse lookup from the NetVault Server to the Client and vice-versa was correct, but when we checked the individual DNS Server Forward and Reverse settings, that the Reverse entry was incorrect. So we amended this to the correct entry.
Still the Client couldn’t be added and the Client was still being called a different name.
So we checked the command line prompt of that Client and could see that the Operating System Host Name had a different name next to the prompt for some reason (maybe this was changed by someone?), so this was changed to the correct name and we could then successfully add the Client.
Then we added all the Firewall port ranges on the NetVault Server and Client, started the SuSE Firewall service and we could still scroll down the Client Filesystem.
