Master Browser not working on server

Hello,

We have a small peer-to-peer network with 1 Windows 2003 server (Standard
Edition) It's roles are file & print server and Internet sharing.
On all the workstations I have disabled the browser service, the problem is
that the server doesn't show any workstations in its browser list. A soon as
I start the browser service, on any workstation in the network, the Master
Browser seems to be moved to the latter and the list of available PC's is
correctly setup (after a couple of seconds or at last a couple of minutes)
When I turn it back of then the Master Browser becomes te server (according
to the "browstat status" command), but unfortunately the list is never
correct.... only the server itsself and sometimes a workstation are listed.
The server is the only station we never shut down, hence I want it to be the
Master Browser all the time. Any idea why the server is the only station in
our network not able to perform this mission?

All help appreciated,
Kind Regards,
Perry

Are all the workstations and the server itself in the same workgroup? It
seems like the server and one workstation are in a different workgroup from
the other workstations.

"Perry Diels" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hello,
>
> We have a small peer-to-peer network with 1 Windows 2003 server (Standard
> Edition) It's roles are file & print server and Internet sharing.
> On all the workstations I have disabled the browser service, the problem
> is that the server doesn't show any workstations in its browser list. A
> soon as I start the browser service, on any workstation in the network,
> the Master Browser seems to be moved to the latter and the list of
> available PC's is correctly setup (after a couple of seconds or at last a
> couple of minutes) When I turn it back of then the Master Browser becomes
> te server (according to the "browstat status" command), but unfortunately
> the list is never correct.... only the server itsself and sometimes a
> workstation are listed. The server is the only station we never shut down,
> hence I want it to be the Master Browser all the time. Any idea why the
> server is the only station in our network not able to perform this
> mission?
>
> All help appreciated,
> Kind Regards,
> Perry
>

Hello Bill,

Thanks for your answer.

Yes they are all in the same workgroup. Meanwhile I have discovered that
just after booting the workstations, they do appear in My network
Places\View Network Computers, but after a while they dissapear. Connection
from server to workstation and vice versa remains intact, it is possible to
browse in both directions (for example via run \\PCName)

I don't understand why the browse list is not maintained. Any idea?

Thanks again,
Perry





"Bill Grant" <not.available@online> wrote in message
news:%(E-Mail Removed)...
> Are all the workstations and the server itself in the same workgroup? It
> seems like the server and one workstation are in a different workgroup
> from the other workstations.
>
> "Perry Diels" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Hello,
>>
>> We have a small peer-to-peer network with 1 Windows 2003 server (Standard
>> Edition) It's roles are file & print server and Internet sharing.
>> On all the workstations I have disabled the browser service, the problem
>> is that the server doesn't show any workstations in its browser list. A
>> soon as I start the browser service, on any workstation in the network,
>> the Master Browser seems to be moved to the latter and the list of
>> available PC's is correctly setup (after a couple of seconds or at last a
>> couple of minutes) When I turn it back of then the Master Browser becomes
>> te server (according to the "browstat status" command), but unfortunately
>> the list is never correct.... only the server itsself and sometimes a
>> workstation are listed. The server is the only station we never shut
>> down, hence I want it to be the Master Browser all the time. Any idea why
>> the server is the only station in our network not able to perform this
>> mission?
>>
>> All help appreciated,
>> Kind Regards,
>> Perry
>>
>
>

On the Windows 2003 Server , go into Network Connections > LAN Connection >
Properties > General Tab. Deselect the checkbox for File and Printer
Sharing for Microsoft Networks > click OK > Check the box to enable it again
> click OK. Also, examine this setting in the registry of the Windows 2003
Server:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Browser\Parameters\IsDomainMaster

Is IsDomainMaster configured with TRUE or FALSE?

--
Todd J Heron, MCSE
Windows Server 2003/2000/NT
----------------------------------------------------------------------------
Note: I do not top-post or bottom-post so that my responses are always easy
to read in this forum and the Google Archives. This posting is provided
"as is" with no warranties and confers no rights.

Hello Todd,

Thanks for your answer. I have followed the steps as you describe but it
didn't help.

The setting in the registry is set to TRUE
The setting just below "MaintainServerList" = Yes. I don't know if that's
important, just in case!

The only machine that remains always visible from the browse list is the
server itself... the workstations only after booting.

Another remark, less important for the time being but it might be a hint,
from My Network Places\Entire Network\Microsoft Windows Network\ only one
Workgroup is visible. That's the workgroup where the server and workstations
belong to, but occasionally other PC's that belong to other workgroups are
connected to our network. Those workgroups never show up from this place
.....not normal isn't it? I remember that the different available workgroups
should be listed here.

Best regards,
Perry

-----------


"Todd J Heron" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> On the Windows 2003 Server , go into Network Connections > LAN Connection
> >
> Properties > General Tab. Deselect the checkbox for File and Printer
> Sharing for Microsoft Networks > click OK > Check the box to enable it
> again
> > click OK. Also, examine this setting in the registry of the Windows
> > 2003
> Server:
>
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Browser\Parameters\IsDomainMaster
>
> Is IsDomainMaster configured with TRUE or FALSE?
>
> --
> Todd J Heron, MCSE
> Windows Server 2003/2000/NT
> ----------------------------------------------------------------------------
> Note: I do not top-post or bottom-post so that my responses are always
> easy
> to read in this forum and the Google Archives. This posting is provided
> "as is" with no warranties and confers no rights.
>

The display you see in Microsoft Windows Network is just a graphic
version of the browse list. The browsing process is a bit strange if you
have multiple workgroups but no domain. Only a domain controller, in fact
only the PDC (or PDC emulator in w2k/2k3) can merge browse lists. Also
stopping the browser service on all machines except the server could cause a
problem with multiple workgroups.

Are all these machines in the same segment (ie on the same wire)? No
routers, bridges etc? No remote access servers?

"Perry Diels" <(E-Mail Removed)> wrote in message
news:eg$%(E-Mail Removed)...
> Hello Todd,
>
> Thanks for your answer. I have followed the steps as you describe but it
> didn't help.
>
> The setting in the registry is set to TRUE
> The setting just below "MaintainServerList" = Yes. I don't know if that's
> important, just in case!
>
> The only machine that remains always visible from the browse list is the
> server itself... the workstations only after booting.
>
> Another remark, less important for the time being but it might be a hint,
> from My Network Places\Entire Network\Microsoft Windows Network\ only one
> Workgroup is visible. That's the workgroup where the server and
> workstations belong to, but occasionally other PC's that belong to other
> workgroups are connected to our network. Those workgroups never show up
> from this place ....not normal isn't it? I remember that the different
> available workgroups should be listed here.
>
> Best regards,
> Perry
>
> -----------
>
>
> "Todd J Heron" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> On the Windows 2003 Server , go into Network Connections > LAN Connection
>> >
>> Properties > General Tab. Deselect the checkbox for File and Printer
>> Sharing for Microsoft Networks > click OK > Check the box to enable it
>> again
>> > click OK. Also, examine this setting in the registry of the Windows
>> > 2003
>> Server:
>>
>> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Browser\Parameters\IsDomainMaster
>>
>> Is IsDomainMaster configured with TRUE or FALSE?
>>
>> --
>> Todd J Heron, MCSE
>> Windows Server 2003/2000/NT
>> ----------------------------------------------------------------------------
>> Note: I do not top-post or bottom-post so that my responses are always
>> easy
>> to read in this forum and the Google Archives. This posting is provided
>> "as is" with no warranties and confers no rights.
>>
>
>

Hello Bill,

Thanks again for your answer.

Al the machines are on the same segment, there's only switches between them
(no routers).
There is a remote access server configured on the same server (W2K3 VPN),
but thats via the second NIC, connected to the outside world (Internet)

Could that cause a problem?
Perry



"Bill Grant" <not.available@online> wrote in message
news:%(E-Mail Removed)...
> The display you see in Microsoft Windows Network is just a graphic
> version of the browse list. The browsing process is a bit strange if you
> have multiple workgroups but no domain. Only a domain controller, in fact
> only the PDC (or PDC emulator in w2k/2k3) can merge browse lists. Also
> stopping the browser service on all machines except the server could cause
> a problem with multiple workgroups.
>
> Are all these machines in the same segment (ie on the same wire)? No
> routers, bridges etc? No remote access servers?
>
> "Perry Diels" <(E-Mail Removed)> wrote in message
> news:eg$%(E-Mail Removed)...
>> Hello Todd,
>>
>> Thanks for your answer. I have followed the steps as you describe but it
>> didn't help.
>>
>> The setting in the registry is set to TRUE
>> The setting just below "MaintainServerList" = Yes. I don't know if that's
>> important, just in case!
>>
>> The only machine that remains always visible from the browse list is the
>> server itself... the workstations only after booting.
>>
>> Another remark, less important for the time being but it might be a hint,
>> from My Network Places\Entire Network\Microsoft Windows Network\ only one
>> Workgroup is visible. That's the workgroup where the server and
>> workstations belong to, but occasionally other PC's that belong to other
>> workgroups are connected to our network. Those workgroups never show up
>> from this place ....not normal isn't it? I remember that the different
>> available workgroups should be listed here.
>>
>> Best regards,
>> Perry
>>
>> -----------
>>
>>
>> "Todd J Heron" <(E-Mail Removed)> wrote in message
>> news:%(E-Mail Removed)...
>>> On the Windows 2003 Server , go into Network Connections > LAN
>>> Connection >
>>> Properties > General Tab. Deselect the checkbox for File and Printer
>>> Sharing for Microsoft Networks > click OK > Check the box to enable it
>>> again
>>> > click OK. Also, examine this setting in the registry of the Windows
>>> > 2003
>>> Server:
>>>
>>> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Browser\Parameters\IsDomainMaster
>>>
>>> Is IsDomainMaster configured with TRUE or FALSE?
>>>
>>> --
>>> Todd J Heron, MCSE
>>> Windows Server 2003/2000/NT
>>> ----------------------------------------------------------------------------
>>> Note: I do not top-post or bottom-post so that my responses are always
>>> easy
>>> to read in this forum and the Google Archives. This posting is provided
>>> "as is" with no warranties and confers no rights.
>>>
>>
>>
>
>

It sure can! (So can the external NIC) .As soon as a remote user
connects, the server acquires an additional IP, so now it has three.
Multihomed browsers have been a problem since NT days, and the software is
still essentially the same.

You need to disable Netbios over TCP/IP on the public NIC and also on
the "virtual" interface. The latter requires a registry edit. See KB 292822
items 1f, 1g and 1h.


"Perry Diels" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hello Bill,
>
> Thanks again for your answer.
>
> Al the machines are on the same segment, there's only switches between
> them (no routers).
> There is a remote access server configured on the same server (W2K3 VPN),
> but thats via the second NIC, connected to the outside world (Internet)
>
> Could that cause a problem?
> Perry
>
>
>
> "Bill Grant" <not.available@online> wrote in message
> news:%(E-Mail Removed)...
>> The display you see in Microsoft Windows Network is just a graphic
>> version of the browse list. The browsing process is a bit strange if you
>> have multiple workgroups but no domain. Only a domain controller, in fact
>> only the PDC (or PDC emulator in w2k/2k3) can merge browse lists. Also
>> stopping the browser service on all machines except the server could
>> cause a problem with multiple workgroups.
>>
>> Are all these machines in the same segment (ie on the same wire)? No
>> routers, bridges etc? No remote access servers?
>>
>> "Perry Diels" <(E-Mail Removed)> wrote in message
>> news:eg$%(E-Mail Removed)...
>>> Hello Todd,
>>>
>>> Thanks for your answer. I have followed the steps as you describe but it
>>> didn't help.
>>>
>>> The setting in the registry is set to TRUE
>>> The setting just below "MaintainServerList" = Yes. I don't know if
>>> that's important, just in case!
>>>
>>> The only machine that remains always visible from the browse list is the
>>> server itself... the workstations only after booting.
>>>
>>> Another remark, less important for the time being but it might be a
>>> hint, from My Network Places\Entire Network\Microsoft Windows Network\
>>> only one Workgroup is visible. That's the workgroup where the server and
>>> workstations belong to, but occasionally other PC's that belong to other
>>> workgroups are connected to our network. Those workgroups never show up
>>> from this place ....not normal isn't it? I remember that the different
>>> available workgroups should be listed here.
>>>
>>> Best regards,
>>> Perry
>>>
>>> -----------
>>>
>>>
>>> "Todd J Heron" <(E-Mail Removed)> wrote in message
>>> news:%(E-Mail Removed)...
>>>> On the Windows 2003 Server , go into Network Connections > LAN
>>>> Connection >
>>>> Properties > General Tab. Deselect the checkbox for File and Printer
>>>> Sharing for Microsoft Networks > click OK > Check the box to enable it
>>>> again
>>>> > click OK. Also, examine this setting in the registry of the Windows
>>>> > 2003
>>>> Server:
>>>>
>>>> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Browser\Parameters\IsDomainMaster
>>>>
>>>> Is IsDomainMaster configured with TRUE or FALSE?
>>>>
>>>> --
>>>> Todd J Heron, MCSE
>>>> Windows Server 2003/2000/NT
>>>> ----------------------------------------------------------------------------
>>>> Note: I do not top-post or bottom-post so that my responses are always
>>>> easy
>>>> to read in this forum and the Google Archives. This posting is
>>>> provided
>>>> "as is" with no warranties and confers no rights.
>>>>
>>>
>>>
>>
>>
>
>

Hello Bill,

I have followed the steps as described, both NETBIOS disabled and KB292822.
At first, after rebooting the server and all the workstations, it looked
fine. The Master Browser is the server and al the connected stations were
visible from the browser (on all stations including the server). I was
confident that this was the solution, but today when restarting the
workstations (not the server) the same problem appears again. The
workstations show up but after x-time only the server remains visible from
network browsing.
Perhaps any other bright idea?

All the best,
Perry





"Bill Grant" <not.available@online> wrote in message
news:(E-Mail Removed)...
> It sure can! (So can the external NIC) .As soon as a remote user
> connects, the server acquires an additional IP, so now it has three.
> Multihomed browsers have been a problem since NT days, and the software is
> still essentially the same.
>
> You need to disable Netbios over TCP/IP on the public NIC and also on
> the "virtual" interface. The latter requires a registry edit. See KB
> 292822 items 1f, 1g and 1h.
>
>
> "Perry Diels" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Hello Bill,
>>
>> Thanks again for your answer.
>>
>> Al the machines are on the same segment, there's only switches between
>> them (no routers).
>> There is a remote access server configured on the same server (W2K3 VPN),
>> but thats via the second NIC, connected to the outside world (Internet)
>>
>> Could that cause a problem?
>> Perry
>>
>>
>>
>> "Bill Grant" <not.available@online> wrote in message
>> news:%(E-Mail Removed)...
>>> The display you see in Microsoft Windows Network is just a graphic
>>> version of the browse list. The browsing process is a bit strange if you
>>> have multiple workgroups but no domain. Only a domain controller, in
>>> fact only the PDC (or PDC emulator in w2k/2k3) can merge browse lists.
>>> Also stopping the browser service on all machines except the server
>>> could cause a problem with multiple workgroups.
>>>
>>> Are all these machines in the same segment (ie on the same wire)? No
>>> routers, bridges etc? No remote access servers?
>>>
>>> "Perry Diels" <(E-Mail Removed)> wrote in message
>>> news:eg$%(E-Mail Removed)...
>>>> Hello Todd,
>>>>
>>>> Thanks for your answer. I have followed the steps as you describe but
>>>> it didn't help.
>>>>
>>>> The setting in the registry is set to TRUE
>>>> The setting just below "MaintainServerList" = Yes. I don't know if
>>>> that's important, just in case!
>>>>
>>>> The only machine that remains always visible from the browse list is
>>>> the server itself... the workstations only after booting.
>>>>
>>>> Another remark, less important for the time being but it might be a
>>>> hint, from My Network Places\Entire Network\Microsoft Windows Network\
>>>> only one Workgroup is visible. That's the workgroup where the server
>>>> and workstations belong to, but occasionally other PC's that belong to
>>>> other workgroups are connected to our network. Those workgroups never
>>>> show up from this place ....not normal isn't it? I remember that the
>>>> different available workgroups should be listed here.
>>>>
>>>> Best regards,
>>>> Perry
>>>>
>>>> -----------
>>>>
>>>>
>>>> "Todd J Heron" <(E-Mail Removed)> wrote in message
>>>> news:%(E-Mail Removed)...
>>>>> On the Windows 2003 Server , go into Network Connections > LAN
>>>>> Connection >
>>>>> Properties > General Tab. Deselect the checkbox for File and Printer
>>>>> Sharing for Microsoft Networks > click OK > Check the box to enable it
>>>>> again
>>>>> > click OK. Also, examine this setting in the registry of the Windows
>>>>> > 2003
>>>>> Server:
>>>>>
>>>>> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Browser\Parameters\IsDomainMaster
>>>>>
>>>>> Is IsDomainMaster configured with TRUE or FALSE?
>>>>>
>>>>> --
>>>>> Todd J Heron, MCSE
>>>>> Windows Server 2003/2000/NT
>>>>> ----------------------------------------------------------------------------
>>>>> Note: I do not top-post or bottom-post so that my responses are
>>>>> always easy
>>>>> to read in this forum and the Google Archives. This posting is
>>>>> provided
>>>>> "as is" with no warranties and confers no rights.
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Download the browsing console and use it to test the
browser functionality. Post the errors if any..

Description of NetBIOS Browsing Console (Browcon.exe)
http://support.microsoft.com/default...b;en-us;818092

"Perry Diels" <(E-Mail Removed)> wrote in message news:
> I have followed the steps as described, both NETBIOS disabled and
KB292822.
> At first, after rebooting the server and all the workstations, it looked
> fine. The Master Browser is the server and al the connected stations were
> visible from the browser (on all stations including the server). I was
> confident that this was the solution, but today when restarting the
> workstations (not the server) the same problem appears again. The
> workstations show up but after x-time only the server remains visible from
> network browsing.
> Perhaps any other bright idea?