How to define scope on a windows 2003 cluster DHCP

Hi I have configured a DHCP service in cluster with windows 2003.  I Create some scope and reservation but when I perform the resource failover I can't see them anymore. It seem that  I have to create via mmc on the other nodes too. is this correct?
pozlu0Asked:
Who is Participating?
 
oBdACommented:
Yes, that should work.
0
 
oBdACommented:
That is most definitely not correct. In short:
Install DHCP on all nodes, set the startup type of the services on all nodes to "manual".
Pick a resource group with a drive resource with some space left for the DHCP database remaining (or use a dedicated group and drive resource).
In this group, greate an IP address resource to use for DHCP, and a network name resource; if possible.
Add the DHCP service resource to the group.
Bring the DHCP service resource group online.
Start the DHCP MMC; use the virtual network name/IP address you've created above to manage the DHCP server.
Make sure the DHCP server is only bound to the virtual address in the public network.
Authorize the server in AD.
Create your scopes.
0
 
rslangenCommented:
When a scope is created for a DHCP clustered server, the virtual IP addresses used in the cluster context must be excluded so that they are not distributed to clients. Additionally. you should configure the database path, audit log file path, and the database backup path using the Cluster Administrator tool on the shared disk.
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
pozlu0Author Commented:
I do the things explained but still I miss the change when I I move the dhcp group from a node to another
0
 
pozlu0Author Commented:
I try to recreate form scratch but noting I have scope and reservation defined only on one node and I have to recreate manually on the other. Another stane thing is that leases too appears on one node only.
0
 
pozlu0Author Commented:
Maybe the problem is related to a fact that I use vmware workstation 6 to do the test?
0
 
oBdACommented:
Are you *definitely* sure that you're connecting to the *clustered* resource with the DHCP MMC, and not to the local DHCP server on the node?
Where are you running the DHCP management MMC on? If you're running it locally on the nodes, make sure you're connecting to the clustered IP address; don't use the standard server that the MMC connects to by default.
0
 
pozlu0Author Commented:
yes, I'm quite sure I use an mmc placed on another dhcp server and point directly to the ip address of the clustered dhcp, hovewer now I'll try to connect using the console of cluster's node pointing to the ip addrees as you suggest and then I'll tell you the result thanks a lot
0
 
pozlu0Author Commented:
i do also this test but if I configure o modify somethig I can see it after makin failover
0
 
oBdACommented:
This is definitely not normal. Is your cluster (in this *exact* configuration!) in the compatibility list for cluster?
The Microsoft support policy for server clusters, the Hardware Compatibility List, and the Windows Server Catalog
http://support.microsoft.com/?kbid=309395

In case you want to start over with the cluster configuration:
How to Uninstall the Cluster Service on a Windows Server 2003 Cluster
http://support.microsoft.com/?kbid=282227

Guide to Creating and Configuring a Server Cluster Under Windows Server 2003
http://www.microsoft.com/downloads/details.aspx?familyid=96F76ED7-9634-4300-9159-89638F4B4EF7&displaylang=en

You should maybe try to install Virtual Server and try server clustering in a virtual test environment. A two node cluster is fully supported:
Microsoft Virtual Server 2005 R2
http://www.microsoft.com/windowsserversystem/virtualserver/default.mspx

Using Microsoft Virtual Server 2005 to Create and Configure a Two-Node Microsoft Windows Server 2003 Cluster
http://www.microsoft.com/technet/prodtechnol/virtualserver/deploy/cvs2005.mspx

0
 
pozlu0Author Commented:
I confirm that the problem is related to Vmware infact even if I create a file on the shared disk this is not present when I do the failover.
Thank you so much! Only one more information. Have I to flag DNS registration must succeded and enable Kerberos authentication too?
DHCP-COnfiguration.JPG
0
 
rslangenCommented:
Enable kerberos is only for extra security. I you have machines like unix they won't get an IP adres.
0
 
oBdACommented:
Once you enable Kerberos and bring the resource online, the cluster service will create a computer object in AD with the name of the the network name resource; you'll then be able to use Kerberos authentication against the virtual name.
It's not necessary to enable it, but recommended.
Whether DNS registration *has* to be successful for the resource to come online is up to you; even if this checkbox is unchecked, the server will still try to register the name in DNS. If the box is checked, and DNS registration is not successful, the resource will not come online (very probably on any node, because that's usually a general error, not one bound to certain node). I usually don't set it.
0
 
pozlu0Author Commented:
Ok so If I let cluster create an account computer name I can use this to put in the DnsUpdateProxy group to provide dynamic dns update is this right?
0
 
pozlu0Author Commented:
Thank you so much for help
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.