First off I would get rid of NetBEUI, it is a legacy
protocol that wil just throw a bunch of unwanted traffic
on your network.
If this is a Windows 2000 (or 2003) domain I have read
that you can publish your shares in Active Directory.
Since Win2k and XP have LDAP querying tools built right
into the OS (and win98 machines can download the AD
querying tools) that will be much more reliable than
relying on master browser, domain master browsers,
elections.....what a pain in the rump.
Also, if most of your machines are win2k or above then
why not put the server's IP in DNS and when people need
to get to the system they just go to start + run and type
in
\\server\share
(or the fully qualified domain name)
\\server.domain.com\share
Lastly, if all of your network clients point to the same
WINS server (or to WINS servers that replicate their
entries with one another) then you can do the "Start"--
"Run" --> UNC share thing listed above. If I were you I
would work towards having your entries in DNS (win2k and
xp clients can be set to update their own entries in DNS
if you like.... if you do not think it is a security risk)
Good luck,
Brian Gibson
Systems Administrator
Wheaton College
-----Original Message-----
Steve, I tried the browstat and it comes back as a unknown
command is there anything special or which server to run
it on?
JEss
-----Original Message-----
Hi Jessie. Browse problems usually occur when a
computer
can not see a
computer on another subnet because the browse masters
can
not communicate
since they need wins to find each other. Browse
problems
also happen if
workstations can not find the browsemaster because they are not using wins
if subnets are involved or the browsemaster [usually a server/pdc fsmo] is
not a wins client, or if the browsemaster has more then one nic. Browsing
problems are a real headache. I will leave a couple
links
and you may want
see
security
.
