Using Microsoft DHCP instead of Novell to hanf out option 78 and 79?

[cajuntank]

I have found two references that pop up consistantly on the Internet in regards of using Microsoft's DHCP server instead of Novell's. The problem I am having is defining the option 78 and 79 for SLP. Using Microsoft's article

http://support.microsoft.com/kb/285019

got me no where. Couldn't get the machine to see the tree. Following

http://www.ithowto.com/microsoft/w2kdhcpslp.htm

gets the machine to see the tree and eventually log in, but it takes a lot longer than before when the Novell was doing the DHCP. Also, I have seen reference to create an A record in DNS for your tree name, so I have done that as well.

Any ideas?

 

[marvhuffaker]

You need to take a packet trace and make sure that you are getting the values as you would expect them. It's possible that you do not have the hex numbers in the right format. Even if off by 1 bit, you could have problems.

If you do a packet trace using NetWare for DHCP with SLP, then compare your new Windows DHCP setup, you should get a good idea of where you're going wrong. You can use Wireshark for this.

Marvin Huffaker, MCNE
Marvin Huffaker Consulting, Inc.
A Novell Platinum Partner

http://www.redjuju.com

 

[cajuntank]

I think I have this figured. I blew my options away and tried the Microsoft route again; however, this time, I did the options one at a time to see what information slpinfo/all was giving me at the client side. Just having option 78 defined and configured, my login was very fast and in doing a slpinfo/all, it must have gleaned the info from the DA to populate the scope list name. Putting in both options 78 and 79, again following Microsoft's article, the login was painfully slow. Removed option 79 and everything's happy snappy. Will stick with that.