Unable to connect to Server via RPC or DCOM
Posted on 2015-02-11
We have applications that connect through DCOM and RPC to a main server, but this server is no longer allowing connections on port 135. I have performed a port test from several other machines in the same domain, but it is not accepting requests from anywhere. I have also attempted to Telnet using port 135 but this doesn't work either.
In addition to the above I have performed a netstat -a on the affected server and it states that there is a connection over port 135 to one of the domain controllers, but when I perform a port query to the affected server from the domain controller it comes back as not listening.
Finally I have performed a Wireshark capture on the server and when a SYN packet comes through the affected server responds with a RST ACK which also suggests that the port isn't listening.
Could anyone shed any light on how I might resolve this issue? I know that a reboot will fix the problem in the short term but in a week or so the problem will reappear, so I am looking for something a little more permanent.
Thanks in Advance