Solved

Retired WINS server reference keeps coming back even though it is not in current DHCP server options

Posted on 2013-06-28
6
432 Views
Last Modified: 2013-07-16
We migrated a customer to a new domain a while back, but left their old domain controllers online for quite a while just to make sure no issues came up.  After shutting them off, we did have name resolution issues which seem to have been resolved.  What I can't get rid of, however, is the reference to the old WINS server on Windows XP DHCP clients.  I can release/renew and get rid of it, but after a while, it seems to show back up.

What is causing this to show back up, despite it not being an option in the DHCP scope of the Windows 2008 R2 domain controller?  Is there a way to clean all references to the old server from the network, or do I need to just manually disable WINS on each XP NIC?
0
Comment
Question by:MnemonixTech
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
6 Comments
 
LVL 24

Expert Comment

by:Nagendra Pratap Singh
ID: 39286189
Are these Xp clients using the same DHCP you are checking?

There may be another DHCP on the LAN.

check ipconfig /all.

DHCP server shows in that
0
 

Author Comment

by:MnemonixTech
ID: 39288526
Yes, that's the odd part.  They show the correct DHCP server each time.  I ran a tool to check for rogue DHCP servers and it only found the legitimate server.
0
 
LVL 40

Expert Comment

by:footech
ID: 39288712
Any chance you have a script being applied via Group Policy that is setting WINS via netsh command?
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
LVL 24

Expert Comment

by:Nagendra Pratap Singh
ID: 39288907
In this case, trying with a fresh XP machine can tell if it is the policy.
0
 
LVL 26

Accepted Solution

by:
Leon Fester earned 250 total points
ID: 39295943
You can try resetting the TCP/IP stack on the affected workstations as sometime the old NIC settings are "remembered".

See instructions to reset your TCP/IP protocol.
http://support.microsoft.com/kb/299357

Have you checked NIC settings the workstation itself?
You may find that the WINS settings are added to the properties of TCP/IP.
These settings will still be used even if DHCP is enabled on the NIC.
0
 
LVL 20

Assisted Solution

by:compdigit44
compdigit44 earned 250 total points
ID: 39300706
Are you sure the IP address for your WINS server are not statically set on your client NIC setting or in the LMHost file
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Auditing domain password hashes is a commonly overlooked but critical requirement to ensuring secure passwords practices are followed. Methods exist to extract hashes directly for a live domain however this article describes a process to extract u…
Let's recap what we learned from yesterday's Skyport Systems webinar.
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …
This video shows how to use Hyena, from SystemTools Software, to update 100 user accounts from an external text file. View in 1080p for best video quality.
Suggested Courses

623 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question