Win98 DHCP Clients not Registering in DNS Host Table

Home Forums Server Operating Systems Windows Server 2000 / 2003 / 2003 R2 Win98 DHCP Clients not Registering in DNS Host Table

Viewing 1 post (of 1 total)
  • Author
  • Avatar

    (Note…originally posted this in the Client OS forum…but more and more appears to be server OS related)

    We have a very aggrivating problem. We are in the process of cleaning up a very messy inherited network. Converting everyone from static IP’s, across multiple nets to DHCP on a single net. Our DHCP is on a Win2KServer which is also our DNS box. We have a mix of Win98 & Win2K clients (~150 or so). We are also making them domain users as we go. Both the Win98 and Win2K machines are converting to the domain, taking the assigned IP from DHCP normally and are showing up in the address lease list, although the Win2K boxes are adding a .com to the domain while the Win98 are not…not sure if this is important but trying to give all info.

    The problem is that while the Win2K boxes are registering and visible in the DNS host table after being moved to DHCP, the Win98 boxes are not. This is a critical problem for us as we have a major interface that is going to rely on DNS entries. We can ping the IP’s of other servers but cannot ping them by DNS name. Can also ping the DNS box but cannot see it by name. An IPCONFIG /all shows all the correct information, including DNS IP.

    We have scoured the net and tried everything we have found to no avail. This includes:

    –> Installing the Win2K DS Client on the Win98 box
    –> On the DHCP DNS tab for both server and scope, we have enabled DNS for clients who don’t support dynamic updates and always update DNS
    –> Followed the directions on Petri’s site for Active Directory Client for Win98/NT
    –> Applied the MS hotfix for the this same issue (see Knowledge Base article Q242000)

    Looking for any wisdom on this challenge. Worried that part of the problem may be our current net config…we inherited a major mess from the folks before us. We have 3 different nets (130.0.0.n, 192.168.1.n, 192.168.100.n), taking everying to 192.168.69.n (we had to have a little fun with the numbering). We have a Watchguard Firebox on the wall with multiple gateways and routes defined but not clearly understood. We are doing everything we can to figure it out.

    So, first question is: is the problem an OS issue or a net issue? I did see a portion in the Win2K Resource Kit regarding option 81 on the DHCP options and FQDN, however, out DHCP options only go to 76.

    Any help would be greatly appreciated as this is kicking out butts…

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.