How to Connect VEEAM B&R to Laptop

Make sure TCP port 10005 is allowed through the laptop's firewall and that the Veeam Agent service is running. It’s also a good idea to test connectivity using telnet from the Veeam server (telnet <laptop_IP> 10005) and run netstat -an | findstr 10005 on the laptop to check if the port is listening. Additionally, verify if any antivirus or security software might be blocking the connection — you can temporarily disable them for testing purposes.

If the issue persists, checking the logs might provide more insight:

• Veeam B&R Server: C:\ProgramData\Veeam\Backup

• Laptop: C:\ProgramData\Veeam\Endpoint

To add another thing to check which is DNS based on this line from the error -

Failed to establish connection: no valid IP addresses were found

Can you ping the FQDN and it resolves the IP and can you ping with -a to resolve the IP to FQDN?  If not on a domain you might need a hosts entry.

This is all contingent on the laptop being added by computer name to the VBR console.  If added by IP then other checks need to be done.

thank you ​@matheusgiovanini and ​@Chris.Childerhose

I am learning more than ever. First my VEEAM server needs telnet activated, lol, figured out how to do this. ​@Chris.Childerhose the laptop was set up by name and not IP, thanks for adding this. 

telnet on VEEAM server after typing telnet <hostname>:10005 message back claims that a connection could not open to the host, on port 23: connect failed

so there is a connection issue possible due to antivirus i assume, our office uses Vipre for antivirus. 

​@Chris.Childerhose reading your FQDN command, enter this on which machine (server or laptop)

You can do this from the server if the VBR server manages the Veeam Agent on the laptop -

ping fqdn --- see if the IP comes back

ping -a ip --- see if the fqdn/hostname comes back

My guess is you need to test the first one and if pinging the FQDN/Hostname does not return an IP then a host entry if you are not on Domain or DNS update on DNS Server.

ping the laptop returned an IP successfully.

I turned off the windows and vipre firewall and tried to telnet <hostname>:10005 and message back still reads a connection could not open to the host, on port 23: connect failed

firewall back on

I ran ping -a ip with IP + :10005 port and came up negative, then ran ping -a IP with IP only, the ping worked

So there is something in the configuration of the Firewalls I am guessing blocking things.  Check this out for the ports used by Veeam - Ports - User Guide for VMware vSphere

Hi ​@TuRK_182 -

Since telnet’ing to the host:port isn’t working, telnet <hostname> <port-number> , try to run netstat to see what is using the port needed: netstat -aof | findstr :10005 or run a simple PoSH script to do so: 

Get-Process -Id (Get-NetTCPConnection -LocalPort YourPortNumberHere).OwningProcess

Something is more than likely using the port (10005?) as Chris suggested. Once determined, stop the process using it (Task Manager maybe, or services), then re-attempt connection with Veeam. 

​@coolsport00 thanks for getting onboard. on the VBR server I ran the netstat command and returned with info that I believe is appropriate. Did same command on laptop and returned with NO information. 

Well, if running netstat on the laptop doesn’t show the port in use (or listening) for a given service, then it should be opened. Unless I or the others can think of something else...at this point, I recommend contacting Support. I mean..your error above says “no valid IP could be found”...so there is something preventing communication. What?...not sure.

Are you going through the Veeam Agent Management Guide to work through the process of backing up your laptop? Maybe something in there will trigger a resolution:

https://helpcenter.veeam.com/docs/backup/agents/introduction.html?ver=120

Have you gone to Advanced Sharing Settings on the laptop, opened the network connection profile you’re on (probably private or domain), and checked the option to “Allow File and Printer Sharing”? 

Give that a try and see if it allows your Veeam server to connect to the laptop.

​@Tommy O'Shea thanks for your input. My laptop had Network Sharing on for all except Public, a setting which was on before me beginning this task.

One other thing that seems to have been missed is that port 10005 is only used from the agent to the Veeam server, not the other way around. That would indicate the laptop is having problems communicating with the Veeam server.

Can you run the following command and share the output (replacing “veeamserver” with the full DNS name of your Veeam server). This will test two things; if the laptop can resolve the IP address of the Veeam server, and if it can communicate with it on port 10005.

Test-NetConnection veeamserver -port 10005

​@Tommy O'Shea 

ComputerName           : <veeamserver>
RemoteAddress          : <veeamserver IP>
RemotePort             : 10005
InterfaceAlias         : Ethernet 3
SourceAddress          : <veeam agent IP>
PingSucceeded          : True
PingReplyDetails (RTT) : 0 ms
TcpTestSucceeded       : False

Ok, now we’re getting somewhere. When I run that command against a Veeam server, it comes back with: TcpTestSuceeded: True
 

When installing Veeam, it should have automatically created windows firewall rules. Has there been some modification to these rules, or some kind of antivirus in place which could be blocking things? For reference, here’s what the firewall rules list looks like on one of my Veeam servers:
 

Your program path may different depending on the installation location you chose.

​@Tommy O'Shea thanks for the help, will dive into this task later today/tonight. I have Vipre installed on the laptop for antivirus. 

Ok. To clarify, those screenshots I took were on the Veeam server.

Regarding Vipre, make sure you review this KB article regarding exclusions that need to be put in place.

Yeah...Vipre will either need to be temporarily disabled or folder/file exclusions provided from the KB Tommy shared. Keep us posted how it goes ​@TuRK_182 

​@TuRK_182 - I wanted to follow up and see if you were able to get this issue resolved so we can mark an answer even if it is your details.  Let us know.