Skip to main content

In very restricted environments, What is the best tool to test required open ports for Veeam distributed components requirements?

Veeam ports tool

https://www.veeambp.com/ports/

With this you can generate a list of needed ports between Veeam components.


No 3rd party tool I can think of off-hand @Moustafa_Hindawi . But, if you’re just wanting to see what ports are being listened to on your VBR server, you can simply run netstat and direct the output to a txt file and review what’s open & being listened on:

netstat -an > C:\path\to\folder\ports.txt

If you want FQDN names, run nestat -af > \path\to\ports.txt

Hope that gives you what you want.


Didn’t even know that existed @JMeixner . Good one! How long has the BP guide had that?..do you know?


Mhh… I don’t know exactly how long this exist, but I think I have seen it one and a half year ago. Or it was something very similar, I am not sure...


I do know the BP was updated...hmm...maybe just a couple yrs or so ago. Maybe it was added then? Anyway...good find!


Thank you @JMeixner & @coolsport00  for your support, that was very helpful.


Sure thing!


You are welcome 😎


You can always try Telnet as well just to see if the connection to a port works. Used that as well as Netstat for troubleshooting.  That other tool Joe posted is great too.


Thank you @Chris.Childerhose 


If you’re working in restrictive environments, you’re more likely to be able to have access to PowerShell than being able to download binaries, in which case for TCP connections I use the Test-NetConnection cmdlet.

 

It’s extremely powerful, can give you the interface it used, ICMP results, route tracing diagnostics etc.

 

https://learn.microsoft.com/en-us/powershell/module/nettcpip/test-netconnection?view=windowsserver2022-ps


@MicoolPaul 

Interesting! I have to try it. Thank you so much!


If you’re working in restrictive environments, you’re more likely to be able to have access to PowerShell than being able to download binaries, in which case for TCP connections I use the Test-NetConnection cmdlet.

 

It’s extremely powerful, can give you the interface it used, ICMP results, route tracing diagnostics etc.

 

https://learn.microsoft.com/en-us/powershell/module/nettcpip/test-netconnection?view=windowsserver2022-ps

I forgot about PowerShell another really great tool for this stuff.  Use this more than others typically.


If you’re working in restrictive environments, you’re more likely to be able to have access to PowerShell than being able to download binaries, in which case for TCP connections I use the Test-NetConnection cmdlet.

 

It’s extremely powerful, can give you the interface it used, ICMP results, route tracing diagnostics etc.

 

https://learn.microsoft.com/en-us/powershell/module/nettcpip/test-netconnection?view=windowsserver2022-ps

Same as Michael, i’m using posh to do it. If you have network administrators who work like goblins like in my company in the past. Sometimes networks ports became close or not working for no apparent reason. You can schedule a posh script from your monitoring tools to check it everyday. 


Thank you @BertrandFR 


Comment