Re: Network Neighborhood
- From: "Michael Giorgio - MS MVP" <Michael.Giorgio@xxxxxxxxxxxxxxxxxxx>
- Date: Wed, 22 Jun 2005 10:54:45 -0400
"Frances [MSFT]" <v-franhe@xxxxxxxxxxxxx> wrote in message news:
> Good to hear from you.
>
> According to the message, I understand that you have some concern about
> using network neighborhood in the win2k3 domain because there will be on
> WINS server. Is this correct?
>
> As far as I know, without WINS server, there will still be master browsers
> and domain master browsers. In the win2k3 domain, if all the clients are
> winXP or win2k, there will be no need to configure WINS server. The
> browsing process will depend on the NetBIOS over TCP/IP, which is enabled
> by default in winXP. Actually, the default setting is "Use NetBIOS setting
> from the DHCP server. If static IP address is used or DHCP server does not
> provide NetBIOS setting, enable NetBIOS over TCP/IP".
>
> So there will be no problem using network neighborhood to browse client's
> PCs. However, using the search feature in AD is always recommend in case
> there are some issues due to the complicated real network environment on
> your side.
In a routed TCP/IP environment, NetBIOS over TCP/IP alone will not
be enough to enumerate the browse list. Some form of NetBIOS name
resolution will be needed. Broadcast name resolution does not traverse
routers.
.
- References:
- Network Neighborhood
- From: Michael
- RE: Network Neighborhood
- From: Frances [MSFT]
- Network Neighborhood
- Prev by Date: Re: Migrating NT PDC to AD Domain
- Next by Date: RE: migrating WINS
- Previous by thread: Re: Network Neighborhood
- Next by thread: Migrated workstation shows FQDN domain name instead of Netbios nam
- Index(es):
Relevant Pages
|
Loading
