Policies not applied on Windows Server 2008 R2 clients?

Question

Active Directory

Kind.
I ran into a problem at the institute, deployed AD on Windows Server 2008 R2, set it up according to the manuals and the beginnings of common sense.
As a result, if you log in through the terminal (1C uses accounting via RDP), they have all the settings applied and all prohibitions are active.
If you start the machine (windows xp pro sp3) in the domain, then
1) none of the policies work, there is not a single prohibition
2) the system logs in for 5 minutes (login, applying settings ...)
A test group policy object was created, is associated with a domain, the group of users for whom this group policy is intended is selected in the filters. All other user groups are not listed in it.
habreffect.ru/files/ecc/9d5ac3c38/01.png
habreffect.ru/files/097/cec6c6b31/02.png
With the help of group policy modeling, the login of one of the users of this group on the local computer was emulated, in the report the created test object of the GPU is listed in the "Applied Group Policy Objects". But on the local computer without changes
habreffect.ru/files/3cf/045333461/03.png

Answer 1

Can it is banal on the client and the server different time is exposed? what does it say in the client logs?

Answer 2

A long domain login can be banal due to a bad patch cord, incorrectly set duplex on the switch ...

Answer 3

+ 1 check date and time, what type of AD is created?

Answer 4

Long entry.
1. Native drivers are not installed on the network card.
2. Incorrect network settings, including DNS.