Re: Loopback issues

From: Mike Huff (huffmt_at_adelphia.net)
Date: 01/28/05 

Date: Thu, 27 Jan 2005 23:05:59 -0500

I finally got this to work on a Windows 2000 workstation and a different XP
workstation.

I ran some sort of corporate provided security script about 18 months ago on
the troubled XP workstation and this also seems to affect workstations built
with a coporate provided image.

Is it possible that some sort of security is set wrong on the local box that
would prohibit the loopback processing? Some sort of security issue with
reading the local policy or paplying anything other than th elocal policy
for the User Configuraiton?

"Mike Huff" <huffmt@adelphia.net> wrote in message
news:zo-dnSer5_y6bGvcRVn-hg@adelphia.com...
>I have an OU with 10 XP workstations in it. 2003 AD.
>
> 1 GPO applied, with Loopback Processing enabled and set to replace.SUS
> policy set in Computer Configuraiton.
> GPO in User Configuration has set to not display "My Computer" on desktop
> and not to display "Add/Remove Programs" in Control Panel.
>
> Computer Configuraiton portion of GPO is working fine (SUS, etc.), but
> none of the User Configuraiton portion of the policy is being applied.
>
> Any ideas?
>

Relevant Pages

  • Re: Loopback issues
    ... policy to be interrupted by changes in ACLing (something I ... Microsoft MVP (Windows Security) ... > I finally got this to work on a Windows 2000 workstation and a different ... >> none of the User Configuraiton portion of the policy is being applied. ...
    (microsoft.public.windows.group_policy)
  • Paradigms II
    ... Secure Systems Revisited ... Performing the following very basic security evaluation on your system ... (server or workstation); however, they can be easily adapted to any other ... control over that information. ...
    (comp.security.misc)
  • Re: Paradigms II
    ... > are not about trying to circumvent security. ... > (server or workstation); however, they can be easily adapted to any other ... > to have at least a vague idea what security, and a secure environment, ...
    (comp.security.misc)
  • Re: Event ID 5719: No Windows NT or Windows 2000 Domain Controller is available for domain .
    ... In my experience what you have done with security policy should ... The workstation gets its networking information from DHCP that, ... updates DNS. ... I don't believe the problem to be at the server end though. ...
    (microsoft.public.win2000.security)
  • Re: Event ID 5719: No Windows NT or Windows 2000 Domain Controller is available for domain .
    ... manual inspection of the DNS _srv records plus NSLOOKUP from the workstation ... In my experience what you have done with security policy should ... not interfere with that computer being able to find a domain controller. ... updates DNS. ...
    (microsoft.public.win2000.security)
Loading