DCOM remote connection fails.

[amari]

Here is my problem with DCOM authentication.
I have a client in machineOne that needs to access a DCOM service in machineTwo. Both running WinNT 4.0 with service pack 5. both logged in to the local machine respectively. I try to connect with user name and password of the machineTwo and the connection succeeds. Now if I try it the other way (machineTwo tries to connect to machineOne) the connection fails with the well known error (RPC server is unavailable).
I ran DCOMCNFG and both machines have the same settings in all options. I ran Network Monitor and I analyzed each packet exchanged between the two machines in both directions and I found that the packet that holds the MEOW are different. The packet that succeeds carries with it the server IP address and the port number other than 135. The packet that doesn’t succeed does not carry with a such thing.

Now I am getting disappointed and regretting in using DCOM in the first place. This bug is taking me lot more than it should. Any help would be appreciated very much.

 

[amari]

Thanks God, I found the problem.

Anyone who is interested read knowledge base Q201911.
The problem might also happen if the key HKLM\SOFTWARE\Microsoft\RPC\Internet is empty. I haven't found any mention of this. The work around is to delete the Internet Key otherwise you can make a call to RpcServerUseProtSeq once for each protocol that the server wants to support.