DC having RPC 1722 errors

[juniper911]

Hello all...

One of my domain controllers seems to be having a range of problems and one of them is RPC 1722 exceptions. I cannot manage other servers's services using the MMC nor can I manage this DC's services from other servers using the MMC.

I read somewhere that 1722 could indicate that the DC may have lost the secure password with the other DC.

Is this correct?

There is also group policy problems but I think that the RPC problem may be the root cause of it all.

 

[juniper911]

I cannot map a drive to another DC's sysvol from the problematic DC

 

[itsp1965]

From Eventid.net;

As per Microsoft: "A distributed (RPC) application has tried to reach a server that is not available. For instance, the server might be shut down, there might be a network hardware problem, there might be no common transports, or the server might not exist". Check the MS knowledgebase for more detail

Hope this helps

 

[sutors]

RPC 1722 means no connectivity.

Does your AD replication work fine?

The easiest way to check if secure channel is broken is to attempt to access a share of another domain controller by using FQDN. If that fails then most likely you need to reset the secure channel.

Some of the errors indicating broken secure channel are access denied errors or target principal name is incorrect errors.

 

[juniper911]

The problem was to do with the MTU size. There was nothing set and thats why certain things would work. By setting an MTU,everything now works properly.