Hi ​@MohamedSameh -

We are needing more info on your setup. Are you using Veeam Agents or Veeam Backups? Veeam Console? What version of Veeam are you using?

To start, if using Agents for Windows & Linux connected to your Veeam server, make sure DNS is setup correctly. Are you on a domain network or local non-domain network? If non-domain, you would need to add all your IPs to hosts files on all Veeam components. If your Veeam server is also your Veeam Proxy and Repo, you only need to add IPs/hostnames to the hosts file on Veeam server. Also, you can check and see if UAC is *disabled* on the Windows computer you are trying to backup.

For the Linux computer...hmm...not sure on that one, but could also be DNS..again, if you haven’t set that up. 

Best.

Hello ​@MohamedSameh!

The problem seems like a name resolution or port connectivity issue between your Veeam infrastructure and the physical machine you're trying to add.
 

From your Veeam server, try nslookup LDCazsVeeam2V.LDCGPX.local, f it fails or returns wrong IP, fix DNS or add a temporary mapping in the hosts file.

From Veeam server, test if the port is open → telnet 192.168.142.95 10006. If it fails, check firewall rules on the target machine and in the network.

This is usually a firewall or network-related issue as suggested by ​@matheusgiovanini due to the error message “connection timed out”.

Dears, 

Thanks for you answer but after the checking the DNS is given me correct output and when I telnet 

port 10006 in the veeam server itself it is open.

so the issue still exists and the DNS and port 10006 inside the server checked and they are alright 

Hello ​@coolsport00,

Thanks for your help. 
The server was doing fine before and every job was running successfully but after this error all the jobs 

started to fail and this issue happens..
I also checked the DNS and it is fine and give correct IP after resolving it 

There are only a couple other suggestions I have other than what I shared and that is to check the logs in the C:\ProgramData\Veeam\Backup\<job-name-folder> or contact Veeam Support.

We can still try to help, but not sure what else to suggest. Can you share more about your environment from what I asked above.

Hi ​@MohamedSameh Reading the posts fromthe others guys here, I can also suppose the issue is on your namesercer, try nslookup the hostname and also the reverse nslookup, example:
nslookup acme.com will return 192.168.1.22 , the reverse must return the name acme.com, nslookup 192.168.1.22, sometimes the reverse is misconfigured. 

i had the same issue week ago - with windows agent

issue was that OS team installed software, which used same port 10005, so in the job i so suddenly “No valid IP addresses were found”

after they changed port, everything was working again

That’s true Marcel, ​@MohamedSameh you can uset the netstat -ano command to check the ports