Where does DHCP have the setting for where the clients get WINS?

This may sound silly, but I set up DHCP & WINS on a new box. When I set up
the scope I set itself as the WINS server in the "scope options" and "server
options". Yet somehow all of it's DHCP clients are pulling WINS from the old
WINS server (which I can find no mention of in DHCP's settings).

I changed the TCPIP settings on the server to also look at itself for WINS
(in the NIC settings) too. Didn't help.

I'm stumped. So what did I miss?

I setup my second site the same way, and it's working just fine.

 

What node type are the WINS clients? If they are configured as b-node, they
broadcast WINS messages, so the first WINS server that receives the packets
will respond.

You might want to give this a try to see if it resolves your problem:

Configure the DHCP scope (or server) option #46 to set the node type to h-
node (hybrid node). Hybrid node clients send WINS messages to WINS servers
first; if they can't find a WINS server, they will then broadcast.

To set this option at a scope level, open DHCP, then under the scope you
want to configure click Scope Options. Right click Scope Options for the
context-sensitive menu, then click Configure Options...

Scroll down the list to option 046 WINS/NBT Node Type, and check the
checkbox. In the text box that appears named "Byte," type 0x8.

--
James McIllece, Microsoft

Please do not send email directly to this alias. This is my online account
name for newsgroup participation only.

This posting is provided "AS IS" with no warranties, and confers no rights.

 

They are already set to 0x8 on both the old (NT4) and new (2k3) WINS
servers. Any other thoughts?

 

If they are already hybrid nodes and the old WINS server is receiving the
query, but the clients are not configured to use the old server, I would
suspect there is a good possibility that the clients are failing to contact
the new WINS server and are therefore broadcasting. The old server is
probably receiving and answering broadcasts.

So I would focus for now on verifying that clients have access to the new
WINS server.

Can you ping the new WINS server from the clients, either by IP or by name?
(Do you also have DNS installed?)

Have you verified that the clients are receiving leases from the DHCP
server via doing an "ipconfig" on clients to review what settings they
have? If there is a router between the DHCP server and the clients, you
need to configure it to forward DHCP messages/to act as a DHCP relay agent.

I realize that you probably have tried this stuff and know about it, just
trying to think of something that might solve the problem.



--
James McIllece, Microsoft

Please do not send email directly to this alias. This is my online account
name for newsgroup participation only.

This posting is provided "AS IS" with no warranties, and confers no rights.

 

You are correct that I have tried that already. I have one DHCP server (in
this subnet) and it is on the same box as the wins server. So, yes, they are
able to contact the server. However as more computers renewed their lease
from this DHCP server, I have noticed that some will grab the correct WINS
server, and others will not.

Is there a limit to the number of connections that the server will respond
to (is it governed by the number of licenses I entered into it)? Maybe I
just need more licenses? I had hoped to let the old WINS server run until
everyone migrated off of it, but maybe I'll try just shutting it down and
expiring everyone's DHCP to speed up that process.

 

I am not that familiar with licensing, however it seems logical to assume
that if the server doesn't have enough licenses it won't provide service to
some clients.

Are there any events in the Event Log related to licensing and/or WINS or
DHCP?

BTW, here's a brief article on licensing in case you need the info:

"Windows Server 2003 Client Access Licensing Overview"
http://www.microsoft.com/windowsserver2003/howtobuy/licensing/caloverview.m
spx

--
James McIllece, Microsoft

Please do not send email directly to this alias. This is my online account
name for newsgroup participation only.

This posting is provided "AS IS" with no warranties, and confers no rights.