You all know how to setup a DHCP Server it is easy , start,run,appwiz.cpl,add components,network services<> ADD DHCP.

Well it is almost the same but than different.

Ok I have a 3 node cluster and a DC running. I made a ISCSI target and published it to the cluster as free space.

So here is my cluster Windows 2008 R2

   What We need for the DHCP is a disk

I created a 5 Gb ISCSI disk and added this to my cluster.

So the first step we do is add the dhcp role to the cluster .start the server Manager to add the role

you have to do this on every node !

Now start the cluadmin.msc and under services and applications right click <> configure a Service or application

 

Select the DHCP Role and as you can see my node 3 does not have the DHCP Role, I decide to ignore this error ! to get errors for troubleshooting later !

So we need a name this will be the cluster group name and an IP

Next is select the Disk for this resource. I used the 5 Gb disk

In the beginning we had this error no dhcp on node 3. if you missed this the next screen can’t be missed

To bad this error is also in yellow. So I have a failure but it is no show stopper.

The Cluster Resources and IP Right click on the resource you can see all the options, I choose Manage DHCP

the nice thing about this is it is a cluster resource single point of configuration one console to set all. I created my scope just like in NT ;-) in the properties there are new Tabs

  there is a new configure button name protection This feature supports prevention of name squatting issues caused due to non-Windows OS machines. Using this feature one could prevent registration of non-Windows OS machine with a same name that is already registered for another machine in DNS Server.

You can use Network Access Protection with DHCP to enforce health policies, which can help protect a network against the spread of viruses, worms, and malicious software (malware).

there is now a filter who can receive a DHCP IP

there is the collision detection works if you have multiple DHCP servers with the same scope.

One this that is important is the credentials to register the IP in the DNS if you are running a secure DNS

So now that the DHCP server is up and running on node 1 I move this resource to node 3

as you can see DHCP server failed , remember I did not install DHCP on node 3

I added a time server and move the resource back to node 1

Next time we do WINS / DFS

 

 

 

For troubleshooting you can use several tools. This time I used the microsoft network monitor 3.3 tool for network sniffing.

no not wireshark first I had to update I used an old version so after I installed 3.3 I’m ready to go. But after a “binging” I found extra updates and tools for the MNN3.3 Below is Info I grabed to get you started. Source info : Network Monitoring Team

Updated Parsers:

As you probably already know, we release new parsers on CodePlex every month. In these updates we've included updates for Windows 7 protocols. We also have support for Remote Windows Sockets (RWS) which is used to proxy TCP and UDP traffic from Winsock applications. Check out this blog for more information.

We post all the source code for the parsers, and you are free to look at the code, file bugs, request we take your parser code etc. This is a fully open-source parser project!

New Experts:

TCP Analyzer - TCP Analyzer lets you view TCP traffic visually and determine performance issues. This blog has more information.

Top Users - Top Users is an expert that lets you view the heaviest talkers on your network. This allows you to get a high level view and narrow down on machines that could be expectedly consume network bandwidth.

If you would like to create your own expert feel free to contacts us for information. http://nmexperts.codeplex.com has more details on how to submit a project for consideration.

New Public Forums:

The forums on Connect are normally for supporting our betas, though we'll answer any question you have. However we now have public forums here, which is geared towards supporting the currently released version. Please post your Network Monitor 3.3 questions there so all users can learn from each other and feel free to answer question as well to help others out.

Hopefully this quick note will help you keep in touch with everything that is going on with Microsoft Protocols and Network Monitor 3.

Enjoy,

Network Monitor Team