NetServerEnum() flakey when enumerating WORKGROUP machines from a domain server machine

[Will]

I'm using the NetServerEnum() API to enumerate remote machines on a LAN. I'm
using the "domain" parameter to filter the domain/workgroup that I want to
enumerate machines for.

I'm having a problem enumerating machines that are configured as a workgroup
on the LAN as opposed to a domain member. When I use NetServerEnum(), it
doesn't always return all of the machines in the workgroup. i.e. If you run
it 10 times, sometimes it will see all machines, sometimes a couple,
sometimes almost all. I know all of the remote workgroup machines are up and
running.

It works fine at enumerating domain member machines.

I'm not sure if it makes any difference (and I can't test this now), but the
software is being run from a 2000 SP2 server.

Is there anything I can do to improve this situation?

[Yan-Hong Huang[MSFT]]

Hi Will,

All I have done till now is to use this API to enumerate servers in a
domain. I am not sure if it works in a workgroup. I will go to test it and
reply you later.

Best regards,
yhhuang
VS.NET, Visual C++
Microsoft

This posting is provided "AS IS" with no warranties, and confers no rights.
Got .Net? http://www.gotdotnet.com
--------------------
!From: "Will" <wi...@will.net>
!Subject: NetServerEnum() flakey when enumerating WORKGROUP machines from a
domain server machine
!Date: Wed, 18 Dec 2002 11:08:29 -0600
!Lines: 19
!X-Priority: 3
!X-MSMail-Priority: Normal
!X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
!X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
!Message-ID: <uKhUAgrpCHA.1948@TK2MSFTNGP10>
!Newsgroups: microsoft.public.win32.programmer.networks
!NNTP-Posting-Host: d1c47cb5.gw114.dsl.airmail.net 209.196.124.181
!Path: cpmsftngxa06!TK2MSFTNGP08!TK2MSFTNGP10
!Xref: cpmsftngxa06 microsoft.public.win32.programmer.networks:3571
!X-Tomcat-NG: microsoft.public.win32.programmer.networks
!
!I'm using the NetServerEnum() API to enumerate remote machines on a LAN.
I'm
!using the "domain" parameter to filter the domain/workgroup that I want to
!enumerate machines for.
!
!I'm having a problem enumerating machines that are configured as a
workgroup
!on the LAN as opposed to a domain member. When I use NetServerEnum(), it
!doesn't always return all of the machines in the workgroup. i.e. If you run
!it 10 times, sometimes it will see all machines, sometimes a couple,
!sometimes almost all. I know all of the remote workgroup machines are up
and
!running.
!
!It works fine at enumerating domain member machines.
!
!I'm not sure if it makes any difference (and I can't test this now), but
the
!software is being run from a 2000 SP2 server.
!
!Is there anything I can do to improve this situation?
!
!
!

[Yan-Hong Huang[MSFT]]

BTW, could you plz post your main snippet code here? Thanks.

Best regards,
yhhuang
VS.NET, Visual C++
Microsoft

This posting is provided "AS IS" with no warranties, and confers no rights.
Got .Net? http://www.gotdotnet.com
--------------------
!From: "Will" <wi...@will.net>
!Subject: NetServerEnum() flakey when enumerating WORKGROUP machines from a
domain server machine
!Date: Wed, 18 Dec 2002 11:08:29 -0600
!Lines: 19
!X-Priority: 3
!X-MSMail-Priority: Normal
!X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
!X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
!Message-ID: <uKhUAgrpCHA.1948@TK2MSFTNGP10>
!Newsgroups: microsoft.public.win32.programmer.networks
!NNTP-Posting-Host: d1c47cb5.gw114.dsl.airmail.net 209.196.124.181
!Path: cpmsftngxa06!TK2MSFTNGP08!TK2MSFTNGP10
!Xref: cpmsftngxa06 microsoft.public.win32.programmer.networks:3571
!X-Tomcat-NG: microsoft.public.win32.programmer.networks
!

!I'm using the NetServerEnum() API to enumerate remote machines on a LAN.
I'm

!using the "domain" parameter to filter the domain/workgroup that I want to
!enumerate machines for.
!

!I'm having a problem enumerating machines that are configured as a
workgroup
!on the LAN as opposed to a domain member. When I use NetServerEnum(), it
!doesn't always return all of the machines in the workgroup. i.e. If you run
!it 10 times, sometimes it will see all machines, sometimes a couple,
!sometimes almost all. I know all of the remote workgroup machines are up
and
!running.
!
!It works fine at enumerating domain member machines.
!
!I'm not sure if it makes any difference (and I can't test this now), but
the
!software is being run from a 2000 SP2 server.
!
!Is there anything I can do to improve this situation?
!
!
!

[Will]

I'm basically using the same code as the snippet in the SDK. The only
changes are that it's filtering with servertype=SV_TYPE_SERVER and
domain="workgroup" (in this particular case).

"Yan-Hong Huang[MSFT]" <yhh...@online.microsoft.com> wrote in message
news:x9zUxAypCHA.1844@cpmsftngxa09...

[Yan-Hong Huang[MSFT]]

Hi Will,

Browsing in workgroups relies entirely on network datagrams sent as
broadcasts. This is unreliable and does not work over routers, as they
usually don’t forward broadcasts. You should also see quite some outages
when machines come and go in the workgroup.

In domains, browsing is mainly done by the domain controllers and the PDC
has the role of compiling the list each network segment has and combine it
to a global list of computers.

So the API works for both domains and workgroups, but the infrastructure of
the domain is much better.

Best regards,
yhhuang
VS.NET, Visual C++
Microsoft

This posting is provided "AS IS" with no warranties, and confers no rights.
Got .Net? http://www.gotdotnet.com
--------------------
!From: "Will" <wi...@will.net>

!References: <uKhUAgrpCHA.1948@TK2MSFTNGP10> <x9zUxAypCHA.1844@cpmsftngxa09>
!Subject: Re: NetServerEnum() flakey when enumerating WORKGROUP machines

from a domain server machine

!Date: Wed, 18 Dec 2002 23:56:03 -0600
!Lines: 64

!X-Priority: 3
!X-MSMail-Priority: Normal
!X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
!X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

!Message-ID: <un4t2MypCHA.704@TK2MSFTNGP09>

!Newsgroups: microsoft.public.win32.programmer.networks
!NNTP-Posting-Host: d1c47cb5.gw114.dsl.airmail.net 209.196.124.181

!Path: cpmsftngxa09!TK2MSFTNGP08!TK2MSFTNGP09
!Xref: cpmsftngxa09 microsoft.public.win32.programmer.networks:3590
!X-Tomcat-NG: microsoft.public.win32.programmer.networks
!
!I'm basically using the same code as the snippet in the SDK. The only
!changes are that it's filtering with servertype=SV_TYPE_SERVER and
!domain="workgroup" (in this particular case).
!
!
!"Yan-Hong Huang[MSFT]" <yhh...@online.microsoft.com> wrote in message
!news:x9zUxAypCHA.1844@cpmsftngxa09...
!> BTW, could you plz post your main snippet code here? Thanks.
!>
!> Best regards,
!> yhhuang
!> VS.NET, Visual C++
!> Microsoft
!>
!> This posting is provided "AS IS" with no warranties, and confers no
!rights.
!> Got .Net? http://www.gotdotnet.com
!> --------------------
!> !From: "Will" <wi...@will.net>
!> !Subject: NetServerEnum() flakey when enumerating WORKGROUP machines from
!a
!> domain server machine
!> !Date: Wed, 18 Dec 2002 11:08:29 -0600
!> !Lines: 19
!> !X-Priority: 3
!> !X-MSMail-Priority: Normal
!> !X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
!> !X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
!> !Message-ID: <uKhUAgrpCHA.1948@TK2MSFTNGP10>
!> !Newsgroups: microsoft.public.win32.programmer.networks
!> !NNTP-Posting-Host: d1c47cb5.gw114.dsl.airmail.net 209.196.124.181
!> !Path: cpmsftngxa06!TK2MSFTNGP08!TK2MSFTNGP10
!> !Xref: cpmsftngxa06 microsoft.public.win32.programmer.networks:3571
!> !X-Tomcat-NG: microsoft.public.win32.programmer.networks
!> !

!> !I'm using the NetServerEnum() API to enumerate remote machines on a LAN.

!> I'm
!> !using the "domain" parameter to filter the domain/workgroup that I want
!to
!> !enumerate machines for.
!> !

!> !I'm having a problem enumerating machines that are configured as a

!> workgroup
!> !on the LAN as opposed to a domain member. When I use NetServerEnum(), it
!> !doesn't always return all of the machines in the workgroup. i.e. If you
!run
!> !it 10 times, sometimes it will see all machines, sometimes a couple,
!> !sometimes almost all. I know all of the remote workgroup machines are up
!> and
!> !running.
!> !

!> !It works fine at enumerating domain member machines.
!> !
!> !I'm not sure if it makes any difference (and I can't test this now), but

!> the
!> !software is being run from a 2000 SP2 server.

!> !
!> !Is there anything I can do to improve this situation?
!> !

!> !
!> !
!>
!
!
!

[Will]

yhhuang

Thanks for your reply. I can understand now why it's flakey with workgroups.

Is there an alternate method of enumerating machines that would be more
reliable? How does the "network neighborhood" browser do it? Is it caching
the machine names as it finds them?

Thanks

Will

"Yan-Hong Huang[MSFT]" <yhh...@online.microsoft.com> wrote in message

news:u$EToozpCHA.3248@cpmsftngxa06...

[Yan-Hong Huang[MSFT]]

hmmm. If the response is not stable, caching the machine names is a
feasible method for it.

Best regards,
yhhuang
VS.NET, Visual C++
Microsoft

This posting is provided "AS IS" with no warranties, and confers no rights.
Got .Net? http://www.gotdotnet.com
--------------------
!From: "Will" <wi...@will.net>
!References: <uKhUAgrpCHA.1948@TK2MSFTNGP10>

<x9zUxAypCHA.1844@cpmsftngxa09> <un4t2MypCHA.704@TK2MSFTNGP09>
<u$EToozpCHA.3248@cpmsftngxa06>

!Subject: Re: NetServerEnum() flakey when enumerating WORKGROUP machines
from a domain server machine

!Date: Thu, 19 Dec 2002 10:28:01 -0600
!Lines: 133

!X-Priority: 3
!X-MSMail-Priority: Normal
!X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
!X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

!Message-ID: <uRAU9t3pCHA.1988@TK2MSFTNGP12>

!Newsgroups: microsoft.public.win32.programmer.networks
!NNTP-Posting-Host: d1c47cb5.gw114.dsl.airmail.net 209.196.124.181

!Path: cpmsftngxa09!TK2MSFTNGP08!TK2MSFTNGP12
!Xref: cpmsftngxa09 microsoft.public.win32.programmer.networks:3618
!X-Tomcat-NG: microsoft.public.win32.programmer.networks
!
!yhhuang
!
!Thanks for your reply. I can understand now why it's flakey with
workgroups.
!
!Is there an alternate method of enumerating machines that would be more
!reliable? How does the "network neighborhood" browser do it? Is it caching
!the machine names as it finds them?
!
!Thanks
!
!Will
!

!
!
!"Yan-Hong Huang[MSFT]" <yhh...@online.microsoft.com> wrote in message

!news:u$EToozpCHA.3248@cpmsftngxa06...
!> Hi Will,
!>
!> Browsing in workgroups relies entirely on network datagrams sent as
!> broadcasts. This is unreliable and does not work over routers, as they
!> usually don’t forward broadcasts. You should also see quite some outages
!> when machines come and go in the workgroup.
!>
!> In domains, browsing is mainly done by the domain controllers and the PDC
!> has the role of compiling the list each network segment has and combine
it
!> to a global list of computers.
!>
!> So the API works for both domains and workgroups, but the infrastructure
!of
!> the domain is much better.

!>
!> Best regards,
!> yhhuang
!> VS.NET, Visual C++
!> Microsoft
!>
!> This posting is provided "AS IS" with no warranties, and confers no
!rights.
!> Got .Net? http://www.gotdotnet.com
!> --------------------
!> !From: "Will" <wi...@will.net>

!> !References: <uKhUAgrpCHA.1948@TK2MSFTNGP10>
!<x9zUxAypCHA.1844@cpmsftngxa09>
!> !Subject: Re: NetServerEnum() flakey when enumerating WORKGROUP machines
!> from a domain server machine
!> !Date: Wed, 18 Dec 2002 23:56:03 -0600
!> !Lines: 64

!> !X-Priority: 3
!> !X-MSMail-Priority: Normal
!> !X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
!> !X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

!> !Message-ID: <un4t2MypCHA.704@TK2MSFTNGP09>

!> !Newsgroups: microsoft.public.win32.programmer.networks
!> !NNTP-Posting-Host: d1c47cb5.gw114.dsl.airmail.net 209.196.124.181

!> !Path: cpmsftngxa09!TK2MSFTNGP08!TK2MSFTNGP09
!> !Xref: cpmsftngxa09 microsoft.public.win32.programmer.networks:3590

!> !X-Tomcat-NG: microsoft.public.win32.programmer.networks
!> !

!> !I'm basically using the same code as the snippet in the SDK. The only
!> !changes are that it's filtering with servertype=SV_TYPE_SERVER and
!> !domain="workgroup" (in this particular case).
!> !
!> !

!> !"Yan-Hong Huang[MSFT]" <yhh...@online.microsoft.com> wrote in message

!> !news:x9zUxAypCHA.1844@cpmsftngxa09...
!> !> BTW, could you plz post your main snippet code here? Thanks.

!> !>
!> !> Best regards,

!> !> yhhuang
!> !> VS.NET, Visual C++
!> !> Microsoft
!> !>

!> !> This posting is provided "AS IS" with no warranties, and confers no

!> !rights.
!> !> Got .Net? http://www.gotdotnet.com
!> !> --------------------
!> !> !From: "Will" <wi...@will.net>
!> !> !Subject: NetServerEnum() flakey when enumerating WORKGROUP machines
!from
!> !a
!> !> domain server machine
!> !> !Date: Wed, 18 Dec 2002 11:08:29 -0600
!> !> !Lines: 19
!> !> !X-Priority: 3
!> !> !X-MSMail-Priority: Normal
!> !> !X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
!> !> !X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
!> !> !Message-ID: <uKhUAgrpCHA.1948@TK2MSFTNGP10>
!> !> !Newsgroups: microsoft.public.win32.programmer.networks
!> !> !NNTP-Posting-Host: d1c47cb5.gw114.dsl.airmail.net 209.196.124.181
!> !> !Path: cpmsftngxa06!TK2MSFTNGP08!TK2MSFTNGP10
!> !> !Xref: cpmsftngxa06 microsoft.public.win32.programmer.networks:3571
!> !> !X-Tomcat-NG: microsoft.public.win32.programmer.networks

!> !> !
!> !> !I'm using the NetServerEnum() API to enumerate remote machines on a

!LAN.
!> !> I'm
!> !> !using the "domain" parameter to filter the domain/workgroup that I
!want
!> !to
!> !> !enumerate machines for.

!> !> !
!> !> !I'm having a problem enumerating machines that are configured as a

!> !> workgroup
!> !> !on the LAN as opposed to a domain member. When I use NetServerEnum(),
!it
!> !> !doesn't always return all of the machines in the workgroup. i.e. If
!you
!> !run
!> !> !it 10 times, sometimes it will see all machines, sometimes a couple,
!> !> !sometimes almost all. I know all of the remote workgroup machines are
!up
!> !> and
!> !> !running.

!> !> !
!> !> !It works fine at enumerating domain member machines.
!> !> !
!> !> !I'm not sure if it makes any difference (and I can't test this now),

!but
!> !> the
!> !> !software is being run from a 2000 SP2 server.

!> !> !
!> !> !Is there anything I can do to improve this situation?
!> !> !
!> !> !
!> !> !

!> !>

!> !
!> !
!> !
!>
!
!

!