|
Posted by Roger Abell [MVP] on November 6, 2006, 8:54 am
If you were Registered and logged in, you could reply and use other advanced thread options Did you follow the advise in the guide and use the SCW (security
configuration wizard)? IOW is the W2k3 firewall in use?
Just as a note, the templates are intended as examples to be evaluated
and used as a basis from which one crafts the settings appropriate for
one's environment.
Why not use the GPMC modelling capability to see what settings
are effective for the webserver when it is in each of the two places,
the Web OU or the Computers container ??
Without our having access to view the specific policy settings in
use it is pretty hard to pin-point any specific settings that are in play
to cause the non-connectivities.
> Hello
>
>
> I have an Ad-environment with 2 Windows 2003 SP1 eng server and some
> Windows 2003 SP1 eng member server.
> I have applied some EC-server policy from Microsoft document from april
> 2006.
>
>
> On Domain root I have applied EC-Domain.inf
> On Domain Controller OU I have applied EC-Domain Controller.inf
> On Member Server OU I have applied EC-Member Server Baseline.inf
> On sub OU Web OU I have applied EC-IIS server.inf
>
> I joined 2 new web-servers to the domain and put them in the default
> Computer OU. Lets call them lt104 and lt135 as servername.
>
> Now my problems starts
>
> If I from DC run My Computer > Manage > Connect to another computer,
> select server104 see errors in word file.
>
> If I from a member server that lies in Web OU run MBSA against all server
> in the domain I get errors from scanning lt104 se word file
>
> If I move the server lt104 to Web OU, none of the above errors occur. But
> the server lt104 needs to connect to a standalone server to get picture
> and I cant connect to that standalone server if lt104 is in the Web OU but
> it works if it lies in Computer OU.
>
>
> Any ideers whats causing this problem
>
> Regards
>
> Mikael
>
>
|