Quantcast
Channel: Forefront TMG and ISA Server forum
Viewing all articles
Browse latest Browse all 3822

isa 2006 standard, going crazy with "Enforce Strict RPC compliance"

$
0
0

Hello,

I have read about this issue, but even so, I am not able to fix it on my own.

I am trying to join a W2k8 R2 machine to a domain. If it is in the same network as the domain controller, no problem whatosever. If instead, there is a ISA Server (2006, Standar), issues arise.

Even if I create a rule allowing all the traffic back and forth from the perimeter to the lan, the message still appears.

This is the message:

"Changing primary domain dns name "" failed. The name will remain "newdomain.org" . The specified server cannot perform the requested operation.

I have checked the client's event viewer, and there are several, regarding to netlogon, and to time server, but searching on the internet, I cannot figure it out.

In my view, it has to do with the hidden rule "Enforce Strict RPC compliance", but I disabled it and did not work either.

The domain controller and the client are both W2k8 R2 64 bits, and the ISA Server is 2006 Standar Edition on a W2k3 machine, not being attached to the domain. (That the ISA is not attached to the domain never was an issue in other Active Directory that I have set up).

I have re-started both domain controllers several times, perform dcdiag, and other tests.

I THINK IT ALL COMES DOWN TO THE ISA SERVER, BUT CANNOT WORK IT OUT.

Thanks in advance!


Luis Olías Técnico/Admon Sistemas . Sevilla (España - Spain)


Viewing all articles
Browse latest Browse all 3822

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>