Could be any number of reasons, but I find it best not to question the idiosyncratic behavior of windows operating systems. Sometimes it is best to just go with what works, for you may allow your head to explode with all of windows' weird behaviors.
While most all can be explained, it is hard to help you with this problem since much more information is necessary to make an educated guess. -TOny -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, February 04, 2002 12:56 AM To: NT 2000 Discussions Subject: DHCP won't authorize...update, and request for explanation Hello again. Down below is my original post for reference. Well. This is interesting. I changed the DC's ip from 192.168.101.200 to 192.168.101.4. I changed the default gateway, DNS, and WINS to this ip too. I left the mask at 255.255.255.0. This is the only thing I changed, other than deleting the original scope. This time I left the scope out altogether. Guess what? Now DHCP authorized itself. I didn't have to do it. When I opened DHCP, I had a green arrow. As long as I use 192.168.101.4 as the ip and not 192.168.101.200, this remains true. If I change back to .200, I get a red arrow again. What gives with that? The usable range of hosts on a 24 bit mask is 1 through 254, correct? So, why can I use .4 and not .200 for the host portion of the DC's ip? Would someone be kind enough to explain please? Thanks. Greg Original post: <<Hello All, I am practicing my new mcse skills on a single machine at home. I am logged on as administrator of course. I recently reinstalled 2000 advanced server on a clean hard drive. All service packs and patches are in. Everything is working fine. Everything is at default. I promoted to a domain controller, accepting all defaults during the wizard, including installing DNS. All went smoothly. This DC is not linked to any another machines yet. I configured this home machine DC with a static ip of 192.168.101.200, and with a subnet mask of 255.255.255.0. In addition, the default gateway (metric 1), the primary DNS, and WINS, are all configured with that same ip in tcp/ip properties. I created one scope in DHCP, 192.168.101.1 to 192.168.101.254. I excluded the static ip of the DC, 192.168.101.200. I activated the scope. I did not configure any scope options. All still was well. Then I authorized DHCP. Something is wrong, however. The red arrow on the DHCP server won't go away. It won't turn green. And the details pane still says the server needs to be authorized. When I try to authorize it again, I get a message that says "The specified servers are already present in the directory service." What is wrong? What do I need to do here? What do I need to know to successfully authorize DHCP? Thanks. Greg>> ------ You are subscribed as [EMAIL PROTECTED] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to [EMAIL PROTECTED] ------ You are subscribed as [email protected] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to [EMAIL PROTECTED]
