Domain Controller records in WINS

I have some XP workstations that are registered in WINS as Domain Controllers
(1CH records). I've tried running an nbtstat -RR command at the workstation
in hopes that this would clean up the WINS database but it didn't. Any idea
what could cause an XP machine to register as a DC? In the Wins console, if
I Display records associated with the workstation's IP address, is it safe to
delete the 1CH record without impacting the entire domain?

Thanks,
Bill Lawn

Open a dos prompt on the XP workstations registering
the name and run nbstat -n. Do you see the 1c entry in
the cache? Is it possible the mappings are static? In any
case you can delete the mappings but they may return if
they aren't static.

"BillL" <(E-Mail Removed)`> wrote in message news:
> I have some XP workstations that are registered in WINS as Domain
Controllers
> (1CH records). I've tried running an nbtstat -RR command at the
workstation
> in hopes that this would clean up the WINS database but it didn't. Any
idea
> what could cause an XP machine to register as a DC? In the Wins console,
if
> I Display records associated with the workstation's IP address, is it safe
to
> delete the 1CH record without impacting the entire domain?

Thanks for your help. The 1C record is not in the cache on the workstations
that I have checked. The mappings aren't static. I will try deleting 1 of
them.

"Michael Giorgio - MS MVP" wrote:

> Open a dos prompt on the XP workstations registering
> the name and run nbstat -n. Do you see the 1c entry in
> the cache? Is it possible the mappings are static? In any
> case you can delete the mappings but they may return if
> they aren't static.
>
> "BillL" <(E-Mail Removed)`> wrote in message news:
> > I have some XP workstations that are registered in WINS as Domain
> Controllers
> > (1CH records). I've tried running an nbtstat -RR command at the
> workstation
> > in hopes that this would clean up the WINS database but it didn't. Any
> idea
> > what could cause an XP machine to register as a DC? In the Wins console,
> if
> > I Display records associated with the workstation's IP address, is it safe
> to
> > delete the 1CH record without impacting the entire domain?
>
>
>

Did this work for you?

"BillL" <(E-Mail Removed)`> wrote in message
news3F1DFB9-CD56-48D0-B88D-(E-Mail Removed)...
> Thanks for your help. The 1C record is not in the cache on the
workstations
> that I have checked. The mappings aren't static. I will try deleting 1
of
> them.
>
> "Michael Giorgio - MS MVP" wrote:
>
> > Open a dos prompt on the XP workstations registering
> > the name and run nbstat -n. Do you see the 1c entry in
> > the cache? Is it possible the mappings are static? In any
> > case you can delete the mappings but they may return if
> > they aren't static.
> >
> > "BillL" <(E-Mail Removed)`> wrote in message news:
> > > I have some XP workstations that are registered in WINS as Domain
> > Controllers
> > > (1CH records). I've tried running an nbtstat -RR command at the
> > workstation
> > > in hopes that this would clean up the WINS database but it didn't.
Any
> > idea
> > > what could cause an XP machine to register as a DC? In the Wins
console,
> > if
> > > I Display records associated with the workstation's IP address, is it
safe
> > to
> > > delete the 1CH record without impacting the entire domain?
> >
> >
> >

No, they repopulated because there are a number of WINS servers across our
WAN environment. It sounds like I need to break replication on all WINS
servers, delete the 1CH records, and have the DCs reregister with WINS. Then
reenable replication.

"Michael Giorgio - MS MVP" wrote:

> Did this work for you?
>
> "BillL" <(E-Mail Removed)`> wrote in message
> news3F1DFB9-CD56-48D0-B88D-(E-Mail Removed)...
> > Thanks for your help. The 1C record is not in the cache on the
> workstations
> > that I have checked. The mappings aren't static. I will try deleting 1
> of
> > them.
> >
> > "Michael Giorgio - MS MVP" wrote:
> >
> > > Open a dos prompt on the XP workstations registering
> > > the name and run nbstat -n. Do you see the 1c entry in
> > > the cache? Is it possible the mappings are static? In any
> > > case you can delete the mappings but they may return if
> > > they aren't static.
> > >
> > > "BillL" <(E-Mail Removed)`> wrote in message news:
> > > > I have some XP workstations that are registered in WINS as Domain
> > > Controllers
> > > > (1CH records). I've tried running an nbtstat -RR command at the
> > > workstation
> > > > in hopes that this would clean up the WINS database but it didn't.
> Any
> > > idea
> > > > what could cause an XP machine to register as a DC? In the Wins
> console,
> > > if
> > > > I Display records associated with the workstation's IP address, is it
> safe
> > > to
> > > > delete the 1CH record without impacting the entire domain?
> > >
> > >
> > >
>
>
>

I had a feeling. Are there any particular error or problems
you are having e.g., logon issues or access issues?

"BillL" <(E-Mail Removed)`> wrote in message news:
> No, they repopulated because there are a number of WINS servers across our
> WAN environment. It sounds like I need to break replication on all WINS
> servers, delete the 1CH records, and have the DCs reregister with WINS.
Then
> reenable replication.
>
>

We are unable to access our domain based Dfs structure through our VPN. That
is how I stumbled across the WINS abnormalities. I dpn't yet know if that is
the cause of our problems.


"Michael Giorgio - MS MVP" wrote:

> I had a feeling. Are there any particular error or problems
> you are having e.g., logon issues or access issues?
>
> "BillL" <(E-Mail Removed)`> wrote in message news:
> > No, they repopulated because there are a number of WINS servers across our
> > WAN environment. It sounds like I need to break replication on all WINS
> > servers, delete the 1CH records, and have the DCs reregister with WINS.
> Then
> > reenable replication.
> >
> >
>
>
>