RCP not responding - POrt 135 Not Listening

Question

Hello,

For some time, I can't communicate on port 135 with one of my servers (especially via VEEAM which uses RPC for guest indexing.
I don't have an application firewall and this port is open on my network.
The RPC and DCOM services are well started.

I tried several things (enable IPV6, disable TEREDO etc...) but nothing works, when I try the powershell command "Test-NetConnection "server" -port 135", I get a failed.

Is there any manipulation to do to switch port 135 to LISTENING?

I thank you in advance.

Answer 1

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.