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"--[color=blue]
>"Run" --> UNC share thing listed above. If I were you I[/color]
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
[color=blue]
>-----Original Message-----
>Steve, I tried the browstat and it comes back as a[/color]
unknown[color=blue]
>command is there anything special or which server to run
>it on?
>JEss[color=green]
>>-----Original Message-----
>>Hi Jessie. Browse problems usually occur when a[/color][/color]
computer[color=blue]
>can not see a[color=green]
>>computer on another subnet because the browse masters[/color][/color]
can[color=blue]
>not communicate[color=green]
>>since they need wins to find each other. Browse[/color][/color]
problems[color=blue]
>also happen if[color=green]
>>workstations can not find the browsemaster because they[/color]
>are not using wins[color=green]
>>if subnets are involved or the browsemaster [usually a[/color]
>server/pdc fsmo] is[color=green]
>>not a wins client, or if the browsemaster has more then[/color]
>one nic. Browsing[color=green]
>>problems are a real headache. I will leave a couple[/color][/color]
links[color=blue]
>and you may want[color=green]
>>to post in the win2000.networking newsgroup. --- Steve
>>
>>[url]http://support.microsoft.com/default.aspx?scid=kb;EN-[/url][/color]
>US;102878[color=green]
>>[url]http://support.microsoft.com/default.aspx?scid=kb;EN-[/url][/color]
>US;188305[color=green]
>>[url]http://support.microsoft.com/?kbid=188001[/url]
>>
>>
wrote in message
>>news:094001c3a560$e2cbdb00$a001280a@phx.gbl...[color=darkred]
>>> Yes, this worked but now what? How do I fix it
>>> thanks cause I'm pulling my hair out on this one
>>> Jess
>>>
>>> >-----Original Message-----
>>> >That sounds like a problem with the browse list[/color][/color]
>possibly[color=green][color=darkred]
>>> not being updated
>>> >yet or a networking problem. It would not be a[/color][/color]
>pemission[color=green][color=darkred]
>>> problem. Try using
>>> >unc to see if you can connect from a workstation[/color][/color][/color]
using[color=blue][color=green][color=darkred]
>>> the the servers ip
>>> >address such as \\xxx.xxx.xxx.xxx\sharename. ---[/color][/color]
>Steve[color=green][color=darkred]
>>> >
>>> >
>>> >"Jessie" wrote in message
>>> >news:0b9101c3a549$ec9d18e0$a601280a@phx.gbl...
>>> >> I installed a new server and put in it a domain,
>>> created a
>>> >> shared needed to install software and I can not[/color][/color][/color]
see[color=blue]
>the[color=green][color=darkred]
>>> >> share from any workstation. If I go to another[/color][/color]
>server I[color=green][color=darkred]
>>> >> can see the share, what's the deal it shouldn't be[/color][/color]
>this[color=green][color=darkred]
>>> >> hard is it the workstations or a server or[/color][/color][/color]
security[color=blue]
>on[color=green][color=darkred]
>>> >> the server? Have set everyone as ADMIN and it[/color][/color][/color]
still[color=blue][color=green][color=darkred]
>>> don't
>>> >> work
>>> >>
>>> >> HELP!!!
>>> >> Jess
>>> >
>>> >
>>> >.
>>> >[/color]
>>
>>
>>.
>>[/color]
>.
>[/color]