If you disable Netbios over TCP/IP on the client computers, browsing
won't work at all! The browser service depends on broadcasts of Netbios
names to build a browse list. The reason for disabling NetBT on the public
interface is to force the server (which is the master browser) to use its
private IP address only for Netbios functions.
Enable NetBT on the workstations again. Wait half an hour or so for the
browser function to settle down.
NuBee wrote:
> I disabled NetBIOS over TCP/IP on the public NIC. Before I did this,
> it took a few minutes before the workgroup computers would show up
> when I clicked the workgroup icon on the server. Now, it pops right
> up ... immediately. So, this really helped.
>
> I did the same (disabled NetBios) at the client computers in the
> workgroup. Now, if I click the workgroup icon at a client computer,
> it allows me to go past this icon and open the workgroup, but no
> computers (server or clients) appear in the window. If I leave the
> default selected, then when I click the network icon at a client
> computer, the workgroup icon won't open and I get an error "Workgroup
> is not accessible ... ".
>
> The "disable NetBIOS" at the public NIC really helped to allow quick
> viewing of the workgroup from the server -- many thanks! However, it
> did not fix the problem at the client computers. I still can not see
> any computers (server or clients) from a client computer.
>
> What do I try now?
>
>> Your clients can't access the master browser because it is
>> multihomed (ie there are two IP addresses linked to its Netbios
>> name). Try disabling Netbios over TCP/IP on the public NIC.
>>
>> NuBee wrote:
>>> I'm running win2003 server SP1 with two NIC's using workgroups.
>>> Nic1 is connected to the Internet via DSL modem and Nic2 is
>>> connected to internal private network via a wireless NETGEAR router
>>> with DHCP. I have file and print server installed as well as
>>> IIS6.0. From the server, I can see all computers in the workgroup.
>>> But, I can not see any of the computers in workgroup from any
>>> individual computer in the internal private network. What might be
>>> the problem?
|