Domain Controller Not Master Browser

[LucyMR]

I have a server running W2K, AD and Exchange 2000. This is the only DC on
the network. It supports approximately 18 users.

The DC is not the master browser. I would like to be able to force an
election, but I do not have the resource kit to load to force an election.

Is there something else I can do to make the DC the master browser again?
Currently this role bounces from workstation to workstation (all WinXP), and
the DC never accepts the role. Even after a reboot, the server will not
take on the role.

Consequently, some items are not able to browse the network - a Canon
ImageRunner 6020 for example.

This machine was originally WinNT 4.0 and was upgraded to W2K (not my
idea!).

Are there any other tools, other than those in the resource kit, that would
enable me to force an election and force the DC to become the master
browser?

Thanks!

 

[SaltPeter]

I have a server running W2K, AD and Exchange 2000. This is the only DC on
the network. It supports approximately 18 users.

The DC is not the master browser. I would like to be able to force an
election, but I do not have the resource kit to load to force an election.

A DC can't be a master browser. The rootDC is the default "domain master
browser" of your domain. While a workgroup supports 2 levels of browse list
providers, a domain has 3: domain master, master and backup.

Is there something else I can do to make the DC the master browser again?
Currently this role bounces from workstation to workstation (all WinXP), and
the DC never accepts the role. Even after a reboot, the server will not
take on the role.

Consequently, some items are not able to browse the network - a Canon
ImageRunner 6020 for example.

OK, a print device can't be browsed for, but a print queue can. The point
here is that whatever system the printer is attached to is managing the
print queue. Then we hit the issue of name resolution.

Browsing is netbios based. Clients like XP always use DNS name resolution
before netbios name resolution(thats true even when a WINS server is
present). So the question here is: is DNS is running on the network? Is a
WINS running on the network? Is the WINS server, if any, the same server
serving the print queue. Is there a subnet issue? Was the DC's netbios over
tcp/ip disabled?

 

[LucyMR]

Ok, I can accept the part about a DC can't be a master browser. That's
fine.

As far as the Canon ImageRunner not being able to browse the network, I
guess I didn't make myself clear. I am not trying to sit at an XP
workstation (or any other kind) and browse to find the printer. What I am
trying to do is, at the printer console, I am trying to browse the network
and find a share on the server. This printer is able to scan documents
directly to a network share. You are supposed to be able to browse the
network and save the document to any share on your network - yes, you have
to provide credentials to save the file. FYI - if you haven't worked with
one, the ImageRunners are kinda cool. You can email from them, fax from
them, or scan a doc in PDF or TIFF. And its a printer and regular copier
too.

I am able to hard code a path on the ImageRunner to the file and print
server (also the DC) and provide credentials and successfully scan a
document to the server, but I cannot browse and see the server, any server.
I have used ImageRunners at other locations and have been able to do this.

What you have said about netbios being bound over tcp/ip might be my problem
here. I also do not have a WINS server running at all. DNS is running and
it is working. The ImageRunner has a statis IP and can be pinged by name or
IP and no one has any trouble printing to it, emailing from it, or finding
it to add as a printer.

In another month or so I will be replacing the current DC with a new server,
and setting up from scratch. At that point I would put in a WINS server.

Thanks

 

[SaltPeter]

Ok, I can accept the part about a DC can't be a master browser. That's
fine.

As far as the Canon ImageRunner not being able to browse the network, I
guess I didn't make myself clear. I am not trying to sit at an XP
workstation (or any other kind) and browse to find the printer. What I am
trying to do is, at the printer console, I am trying to browse the network
and find a share on the server. This printer is able to scan documents
directly to a network share. You are supposed to be able to browse the
network and save the document to any share on your network - yes, you have
to provide credentials to save the file. FYI - if you haven't worked with
one, the ImageRunners are kinda cool. You can email from them, fax from
them, or scan a doc in PDF or TIFF. And its a printer and regular copier
too.

The problem i was having with the word "printer" is that a printer in W2K
does not denote the hardware. A printer is a queue. The Canon is a print
device.

Never used that stand-alone printer but looking forward to the day i do.
Since by your description of the problem it doesn't appear to be access
permissions or rights, does the Canon's network configuration as far as the
static ip allow for a DNS pointer in order to resolve the servers?

I am able to hard code a path on the ImageRunner to the file and print
server (also the DC) and provide credentials and successfully scan a
document to the server, but I cannot browse and see the server, any server.
I have used ImageRunners at other locations and have been able to do this.

Perhaps this might help since the domain was migrated from NT to W2K. NT4
relies on netbios name resolution. W2K relies on DNS name resolution. Its
perfectly ok to identify a station or server using server1 in NT4 but W2K
requires hierarchy( ex: server1.domain.com) to resolve.
Perhaps the issue you have is that the printer is trying to resolve using
the wrong name resolution system. Which can also raise other issues since
netbios doesn't cross a router.

What you have said about netbios being bound over tcp/ip might be my problem
here. I also do not have a WINS server running at all. DNS is running and
it is working. The ImageRunner has a statis IP and can be pinged by name or
IP and no one has any trouble printing to it, emailing from it, or finding
it to add as a printer.

In another month or so I will be replacing the current DC with a new server,
and setting up from scratch. At that point I would put in a WINS server.

Not needed (WINS) unless you provide support for older operating systems.
Its much faster for a W2K or XP system to resolve the same computer or
server using its dns name than it is to resolve its netbios name.

slow(netbios)
//server1/share

fast(dns)
//server1.domain.com/share

Which begs me to ask: whats the Canon's network name? You might also
consider checking with manufacturer as well since some of those printers
rely on SNMP. Happy hunting.