April 29, 2010

Time Flies When You're Having Fun, But...

...Fruit flies like a banana.

 It's been a long time since I posted anything at all on here, but school and work have effectually drained my time. Plus Left 4 Dead hasn't helped things. 

 Anyway, I'm getting toward the end of my school career and am working towards focusing more on work-hobbies that help me professionally. Blogging is one of those things that I've always wanted to keep up with, but these 5-week classes are accelerated enough I have to focus on one thing at a time.

 So here's to more fun and interesting info forthcoming!

Charlie

Windows 2008 R2 DHCP + NBX Option 184

At work we are using a Windows 2008 R2 DHCP server that will take over for Linux-based BIND. I had an issue with our 3Com NBX phones not picking up the NCP when I configured option 184 on the DHCP scope. I tried using an IPADDRESS data type, but that did not work. So to properly setup 3Com option 184 (NCP) on Windows DHCP, do this:

At a command prompt, type 'netsh'.
Then you will be at a netsh prompt. Type the following commands to add the 184 optiondef and the optionvalue to a given scope:
Note this must be done on the actual DHCP server, and the command prompt window on 2008 must be run as administrator.

netsh> dhcp server <servername or IP>
netsh dhcp server> add optiondef 184 NCP BYTE 1

The 1 on the end tells DHCP the data type is an array of bytes.

You should get a message indicating the operation completed successfully.

To add the optionvalue to a scope, type the following:

netsh dhcp server> scope x.x.x.x (insert scope IP here)

Now we need to input the data for the NCP request in hex, one byte at a time. You will need to convert the IP of your NCP to hex before entering it here.The following example uses IP 172.172.172.125 converted to hex.

netsh dhcp server scope> set optionvalue 184 BYTE 0x1 0x4 0xac 0xac 0xac 0x7d

Then you should get a message indicating the command completed successfully.

Charlie