group policy not taking effect

[mato]

I have everything set right but the group policy is not
taking effect on the client machines and for user
accounts. I have tried enforcing it using secedit and i
get a message in the application log which says: windows
can not determine the user or computer name. Return value
1722. Can anybody who understands this please help? Thanks.

 

[Sasha]

I think that you have problem with DNS.
Value 1722 - "The RPC Server is unavailable" - Usually occurs when DNS
servers are not configured properly. There is connectivity but not at the
service level. See the Q260371 link below for troubleshooting such issues.
One note here, usually it may appear that DNS is set properly but one has to
double-check all the aspects of DNS registration/resolution as the problem
may not be that obvious. See also Q261007 - It says that this behavior can
occur if the address for the configured preferred DNS server on the client
is invalid or unreachable.
From a newsgroup post: "Do the following to ensure that the SRV records for
the AD servers are in DNS properly: (from the DOS prompt)
Try to enter in TCP/IP properties of DC ip address of preferred DNS
server=127.0.0.1

 

[Guest]

Thanks a lot man. The problem was indeed with the DNS.
What I did to solve the problem was to intergrate DNS into
the active directory and allow dynamic updates. The group
policy is now working and everything seems fine. Thanks a
lot.

-----Original Message-----
I think that you have problem with DNS.
Value 1722 - "The RPC Server is unavailable" - Usually occurs when DNS
servers are not configured properly. There is connectivity but not at the
service level. See the Q260371 link below for troubleshooting such issues.
One note here, usually it may appear that DNS is set properly but one has to
double-check all the aspects of DNS

registration/resolution as the problem

may not be that obvious. See also Q261007 - It says that this behavior can
occur if the address for the configured preferred DNS server on the client
is invalid or unreachable.
From a newsgroup post: "Do the following to ensure that the SRV records for
the AD servers are in DNS properly: (from the DOS prompt)
Try to enter in TCP/IP properties of DC ip address of preferred DNS
server=127.0.0.1


"mato" <[email protected]>

ÓÏÏÂÝÉÌ/ÓÏÏÂÝÉÌÁ × ÎÏ×ÏÓÔÑÈ