Lost Group policy object on win2k server.


P

Paul

Dear All,
I hope someone maybe able to help me with a problem that I believe is
to with my home network and my registered domain name.

Overview of my Setup

Win2k Server SP4.
AD Domain name = "MYDOMAINNAME".COM
2 NIC's
LAN Static IP 192.168.0.1
WAN Auto IP from ISP

4 x Win2k clients.
DHCP enabled in range 192.168.0.2 - 192.168.0.10

The issues I am trying to overcome are.

1) I am unable to view the group policy objects for the domain
controller security policy and the domain security policy. When I
click on the admin tools/ domain controller security policy, the
server hangs for about a minute and returns with " Failed to open
group policy object. You may not have the appropriate rights." Details
"The network path was not found"

2) When I go to the DHCP management console, I note that the
"mydomainname.com" is associated with the ISP providers IP for my WAN
NIC. This is not shown as active. I can delete this entry and
authorise "mydomainname.com" on LAN NIC ( 192.168.0.1). This will
provide all clients with the logon to LAN and access to the WAN.
However if I reboot the server the original DHCP configuration of
"mydomainname.com" associated with the inactive WAN NIC remains.

3)Home network Security, We have 6 users who can log on to any of the
4 clients, and gain access to all network resources and WAN. Each user
is registered in the AD user accounts, and has specific logon hours
assigned for each user. Although the server is able to restrict the
logon time for each user, once the logon time expires the user is not
automatically logged off from the LAN or WAN. This control I
understand is in the group policy object console, but I cannot gain
acces to this console at present.

My thoughts on these issues stem from the possibility that I have a
registered public domain name "mydomainname.com" with a public IP
address. This address is supplied by a 3rd Party and carries a web
page. The home network domain is also called "mydomainname.com" and
has a static LAN address.

Just for your info I have also previously had the home network domain
name as "mydomainname.local" and this provided the solution to 1 & 2
above, however some of the security feateures in 1 above where not
implimented and point3 above sill was uncontrolable.

Any suggestions on the above would be greatly appreciated.

Many thanks in advance

Paul
 
Ad

Advertisements


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top