netbios dns and node types

[Guest]

Archived from groups: microsoft.public.win2000.dns,microsoft.public.win2000.networking (More info?)

We have a pure win2k wan with several sites all converging back to one Head
Office via various sized vpn links.

It has been decided WINS is no longer required so all the wins servers have
been disabled. This leaves me with the question as to how to make name
resolution either more efficient or simply just correct. We are using w2k AD
integrated DNS servers and each site has its own so DNS and it is generally
working fine.

The question I have at the moment is, what node type should servers/systems
be set to as DNS seems bottom of the list on all node types. As there wont
be a WINS server to query is B node the only type to use as thats the only
one that doesnt try to query a netbios name server?

Alternatively, if it doesnt matter if asking a netbios name server is in the
list as the machine is not configured with an address for one then maybe P
node would be the more efficient as it would not broadcast and get to DNS
more quickly without generating lots of local traffic?

..... or have I just lost the plot and none of the node types really make all
that much difference???

For Node type info tht I am going from is:-

B-Node (Broadcast Node)
Broadcast mode uses broadcasts only.

1. NetBIOS Name Cache
2. Broadcast a NetBIOS Name Query
3. Checking the LMHOSTS file
4. Checking a HOSTS file
5. Checking with a DNS server

Configuration - Leave the WINS address empty
Use- Broadcasts are typically blocked by routers so a b-node configuration
will only be effective on a single subnet.

P-Node(Peer-to-Peer Node)

1. NetBIOS Name Cache
2. Asking a NetBIOS Name Server
3. HOSTS file
4. DNS

Configuration - Configure though DHCP lease offering

M-Node(Mixed Node)

1. NetBIOS Name Cache
2. Broadcast a NetBIOS Name Query
3. Checking the LMHOSTS file
4. Asking a NetBIOS Name Server
5. Checking a HOSTS file
6. Checking with a DNS server

Configuration - Configure though DHCP lease offering

H-Node(Hybrid Node)

1. NetBIOS Name Cache
2. Asking a NetBIOS Name Server
3. Broadcast a NetBIOS Name Query
4. Checking the LMHOSTS file
5. Checking a HOSTS file
6. Checking with a DNS server

Configuration - Enter the WINS server address

 

[Guest]

Archived from groups: microsoft.public.win2000.dns,microsoft.public.win2000.networking (More info?)

In news:41c176a3$0$217$bed64819@news.gradwell.net,
jas0n <no@email.here> commented
Then Kevin replied below:
> We have a pure win2k wan with several sites all
> converging back to one Head Office via various sized vpn
> links.
>
> It has been decided WINS is no longer required so all the
> wins servers have been disabled. This leaves me with the
> question as to how to make name resolution either more
> efficient or simply just correct. We are using w2k AD
> integrated DNS servers and each site has its own so DNS
> and it is generally working fine.

So are you going to wean yourself off Network Neighborhood?
Nethood relies on the computer browser service, which uses NetBIOS
broadcasts, LMHosts or WINS. Most routers block NetBIOS bradcasts so LMHosts
or WINS is required to populate Network places accross multiple subnet. WINS
being dynamic is usually easier.



--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================

 

[Guest]

Archived from groups: microsoft.public.win2000.dns,microsoft.public.win2000.networking (More info?)

In article <#L5yJi34EHA.1296@TK2MSFTNGP10.phx.gbl>, admin@nospam.WFTX.US
says...
> In news:41c176a3$0$217$bed64819@news.gradwell.net,
> jas0n <no@email.here> commented
> Then Kevin replied below:
> > We have a pure win2k wan with several sites all
> > converging back to one Head Office via various sized vpn
> > links.
> >
> > It has been decided WINS is no longer required so all the
> > wins servers have been disabled. This leaves me with the
> > question as to how to make name resolution either more
> > efficient or simply just correct. We are using w2k AD
> > integrated DNS servers and each site has its own so DNS
> > and it is generally working fine.
>
> So are you going to wean yourself off Network Neighborhood?
> Nethood relies on the computer browser service, which uses NetBIOS
> broadcasts, LMHosts or WINS. Most routers block NetBIOS bradcasts so LMHosts
> or WINS is required to populate Network places accross multiple subnet. WINS
> being dynamic is usually easier.

we have no use for network neighborhood - all shares are accessed via 1
drive letter which is handed out via logon script, the drive letter
opens up several dfs site links which in turn lead to all the data - if
you access your local dfs site its nice and quick as its over the lan -
access a remote one and its nice and slow over the various wan links

anyway, it turns out that i missed the fact that netbios and dns is done
at the same time, not dns at the end.

 

[Guest]

Archived from groups: microsoft.public.win2000.dns,microsoft.public.win2000.networking (More info?)

> anyway, it turns out that i missed the fact that netbios and dns is
done
> at the same time, not dns at the end.

Not really. It really depends if NetBIOS or DNS name resolution is needed.
Each has its own name resolution flow but they meet at some point.


"jas0n" wrote:

> In article <#L5yJi34EHA.1296@TK2MSFTNGP10.phx.gbl>, admin@nospam.WFTX.US
> says...
> > In news:41c176a3$0$217$bed64819@news.gradwell.net,
> > jas0n <no@email.here> commented
> > Then Kevin replied below:
> > > We have a pure win2k wan with several sites all
> > > converging back to one Head Office via various sized vpn
> > > links.
> > >
> > > It has been decided WINS is no longer required so all the
> > > wins servers have been disabled. This leaves me with the
> > > question as to how to make name resolution either more
> > > efficient or simply just correct. We are using w2k AD
> > > integrated DNS servers and each site has its own so DNS
> > > and it is generally working fine.
> >
> > So are you going to wean yourself off Network Neighborhood?
> > Nethood relies on the computer browser service, which uses NetBIOS
> > broadcasts, LMHosts or WINS. Most routers block NetBIOS bradcasts so LMHosts
> > or WINS is required to populate Network places accross multiple subnet. WINS
> > being dynamic is usually easier.
>
> we have no use for network neighborhood - all shares are accessed via 1
> drive letter which is handed out via logon script, the drive letter
> opens up several dfs site links which in turn lead to all the data - if
> you access your local dfs site its nice and quick as its over the lan -
> access a remote one and its nice and slow over the various wan links
>
> anyway, it turns out that i missed the fact that netbios and dns is done
> at the same time, not dns at the end.
>