Hi,
Welcome to Q&A platform.
I would suggest you could run the command netstat -a in a CMD window with admin privilege's from the problematic machines side to confirm if the port 135 was in listening status.
Meanwhile, I would like to confirm when did the issue occurred and how did you verify the issue is related to port 135 was not in listening status. Whether the issue only occurred when using VEEAM or also occurred when using some other applications or services.
Best Regards,
Sunny
----------
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.