PDC Emulator is missing in network browsing list

Hi everyone,

This problem is giving me headaches. I have a DC which holds all 5 FSMO
roles but is not showing up in the browsing list. This DC is the
masterbrowser for the domain.

The server is not hidden and is not multihomed.

I have run through KB188305 and KB231312 but none of the steps has even
revealed a problem.

When using the "browstat status" command I noticed that sometimes I get a
message "Unable to retrieve server list from server01: 64 (net helpmsg 64 =
The specified network name is no longer available ).

Running the same command again will give me the list. What does this mean ?

With netdiag I only get one warning: failed to query SPN registration on DC
server01; the other tests all pass.

DcDiag test all pass too.

Anyone any idea ?

Thanks.

Ruud de Heij
The Netherlands

Make sure netbios is enabled on all problem machines
and that there is nothing blocking netbios e.g., software
firewall.

"Ruud de Heij" <Ruud de (E-Mail Removed)> wrote in message
news:
> Hi everyone,
>
> This problem is giving me headaches. I have a DC which holds all 5
FSMO
> roles but is not showing up in the browsing list. This DC is the
> masterbrowser for the domain.
>
> The server is not hidden and is not multihomed.
>
> I have run through KB188305 and KB231312 but none of the steps has
even
> revealed a problem.
>
> When using the "browstat status" command I noticed that sometimes I
get a
> message "Unable to retrieve server list from server01: 64 (net
helpmsg 64 =
> The specified network name is no longer available ).
>
> Running the same command again will give me the list. What does this
mean ?
>
> With netdiag I only get one warning: failed to query SPN registration
on DC
> server01; the other tests all pass.
>
> DcDiag test all pass too.
>
> Anyone any idea ?
>
> Thanks.
>
> Ruud de Heij
> The Netherlands
>
>

Hi,

Netbios is enabled on all machines; there is no firewall blocking.

Ruud de Heij

"Michael Giorgio - MS MVP" schreef:

> Make sure netbios is enabled on all problem machines
> and that there is nothing blocking netbios e.g., software
> firewall.
>
> "Ruud de Heij" <Ruud de (E-Mail Removed)> wrote in message
> news:
> > Hi everyone,
> >
> > This problem is giving me headaches. I have a DC which holds all 5
> FSMO
> > roles but is not showing up in the browsing list. This DC is the
> > masterbrowser for the domain.
> >
> > The server is not hidden and is not multihomed.
> >
> > I have run through KB188305 and KB231312 but none of the steps has
> even
> > revealed a problem.
> >
> > When using the "browstat status" command I noticed that sometimes I
> get a
> > message "Unable to retrieve server list from server01: 64 (net
> helpmsg 64 =
> > The specified network name is no longer available ).
> >
> > Running the same command again will give me the list. What does this
> mean ?
> >
> > With netdiag I only get one warning: failed to query SPN registration
> on DC
> > server01; the other tests all pass.
> >
> > DcDiag test all pass too.
> >
> > Anyone any idea ?
> >
> > Thanks.
> >
> > Ruud de Heij
> > The Netherlands
> >
> >
>
>
>

On the PDC emulator open a dos prompt and run nbtstat -n.
Do you see a domain name 1b unique name for domains?
Open the WINS database and sort by name then check for
the 1b name and the the tcp/ip address associated with it.

"Ruud de Heij" <(E-Mail Removed)> wrote in message news:
> Netbios is enabled on all machines; there is no firewall blocking.

Hi, thanks for your efforts so far !

The domain name is listed with 1b unique

In WINS the 1b entry is associated with the correct ip address

In WINS I have one domain 1E normal group name which points to a workstation
and a 00 Workgroup pointing to the same workstation.

I also have two 1C entries:
* domain 1C Domain controller pointing to the PDC
* Inet~services 1C Domain controller pointing to our ISA server



"Michael Giorgio - MVP" wrote:

> On the PDC emulator open a dos prompt and run nbtstat -n.
> Do you see a domain name 1b unique name for domains?
> Open the WINS database and sort by name then check for
> the 1b name and the the tcp/ip address associated with it.
>
> "Ruud de Heij" <(E-Mail Removed)> wrote in message news:
> > Netbios is enabled on all machines; there is no firewall blocking.
>
>
>
>

"Ruud de Heij" <(E-Mail Removed)> wrote in message
news:A0E3452F-357B-45E5-81BD-(E-Mail Removed)...

> I also have two 1C entries:
> * domain 1C Domain controller pointing to the PDC
> * Inet~services 1C Domain controller pointing to our ISA server

Why is the ISA a second DC? Either DCPromo it down to a member server,..or
if it must remain a DC then make sure the binding order is properly set so
that the Internal NIC is the highest Nic in the priority.

That may not specifically be your problem, but it is a good place to start
and that stuff should be "cleaned up" anyway.

272294 - Active Directory Communication Fails on Multihomed Domain
Controllers
http://support.microsoft.com/default...b;en-us;272294

191611 - Symptoms of Multihomed Browsers
http://support.microsoft.com/default...b;EN-US;191611

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

Okay do you see a 1D entry either in WINS or the nbtstat -n
command on the PDC?

"Ruud de Heij" <(E-Mail Removed)> wrote in message
news:
> Hi, thanks for your efforts so far !
>
> The domain name is listed with 1b unique
>
> In WINS the 1b entry is associated with the correct ip address
>
> In WINS I have one domain 1E normal group name which points to a
workstation
> and a 00 Workgroup pointing to the same workstation.
>
> I also have two 1C entries:
> * domain 1C Domain controller pointing to the PDC
> * Inet~services 1C Domain controller pointing to our ISA server

Phillip the Inet~services 1C name is registered by IIS, it doesn't
mean that particular machine is a DC.

"Phillip Windell" <@.> wrote in message
news:(E-Mail Removed)...
> "Ruud de Heij" <(E-Mail Removed)> wrote in message
> news:A0E3452F-357B-45E5-81BD-(E-Mail Removed)...
>
> > I also have two 1C entries:
> > * domain 1C Domain controller pointing to the PDC
> > * Inet~services 1C Domain controller pointing to our ISA server
>
> Why is the ISA a second DC? Either DCPromo it down to a member
server,..or
> if it must remain a DC then make sure the binding order is properly
set so
> that the Internal NIC is the highest Nic in the priority.
>
> That may not specifically be your problem, but it is a good place to
start
> and that stuff should be "cleaned up" anyway.
>
> 272294 - Active Directory Communication Fails on Multihomed Domain
> Controllers
> http://support.microsoft.com/default...b;en-us;272294
>
> 191611 - Symptoms of Multihomed Browsers
> http://support.microsoft.com/default...b;EN-US;191611
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>

In any case it looks as if the Workstation which is registering
the 1E entry is attempting to be the SMB or segment master
browser which will cause a problem since by default he PDC
/ emulator is the SMB or segment master browser. Try disabling
the comptuer browser service on the workstation and see if the
PDC emulator takes back the SMB role..

"Ruud de Heij" <(E-Mail Removed)> wrote in message
news:
> Hi, thanks for your efforts so far !
>
> The domain name is listed with 1b unique
>
> In WINS the 1b entry is associated with the correct ip address
>
> In WINS I have one domain 1E normal group name which points to a
workstation
> and a 00 Workgroup pointing to the same workstation.
>
> I also have two 1C entries:
> * domain 1C Domain controller pointing to the PDC
> * Inet~services 1C Domain controller pointing to our ISA server

Hi Philip,
The ISA server is indeed not a DC. I mentioned here because it look a bit
strange to me that it was registered as 1C Domain Controller.

Can I assume that is a normal WINS registration ?

"Michael Giorgio - MS MVP" wrote:

> Phillip the Inet~services 1C name is registered by IIS, it doesn't
> mean that particular machine is a DC.
>
> "Phillip Windell" <@.> wrote in message
> news:(E-Mail Removed)...
> > "Ruud de Heij" <(E-Mail Removed)> wrote in message
> > news:A0E3452F-357B-45E5-81BD-(E-Mail Removed)...
> >
> > > I also have two 1C entries:
> > > * domain 1C Domain controller pointing to the PDC
> > > * Inet~services 1C Domain controller pointing to our ISA server
> >
> > Why is the ISA a second DC? Either DCPromo it down to a member
> server,..or
> > if it must remain a DC then make sure the binding order is properly
> set so
> > that the Internal NIC is the highest Nic in the priority.
> >
> > That may not specifically be your problem, but it is a good place to
> start
> > and that stuff should be "cleaned up" anyway.
> >
> > 272294 - Active Directory Communication Fails on Multihomed Domain
> > Controllers
> > http://support.microsoft.com/default...b;en-us;272294
> >
> > 191611 - Symptoms of Multihomed Browsers
> > http://support.microsoft.com/default...b;EN-US;191611
> >
> > --
> >
> > Phillip Windell [MCP, MVP, CCNA]
> > www.wandtv.com
> >
> >
>
>
>