XP Pro and WINS or LMHOSTS

[MIke F]

I need some help with some networking questions. I'm not
a network person so I'm struggling with this but making
progress.

I've set up a small peer-to-peer network that includes
three local PCs and one remote PC connected over a VPN.
All PCs are running Windows XP Pro with current updates.
The VPN is controlled by Linksys router/firewall/VPN boxes
(BEFSX41) on both ends. The local network is connected to
DSL with a static IP address and the remote dynamic. The
size of the network will not grow much over the next few
years.

In order to use standard naming conventions (NETBIOS) I'm
looking into WINS or LMHOSTS. I can't seem to find
answers to some basic questions:

1) Do I need a Windows Server machine to run either WINS
or LMHOSTS (or DNS for that matter) or is XP enough?

2) Does a WINS server require a Static IP address within
my network?

3) If I go LMHOSTS am I correct in that all PCs must have
static IP addresses within my network?

4) Does anyone have a reference for clear WINS setup
instructions (I found lots of theory and protocol
explanations but no setup).

I'm not really considering DNS because I may add a Windows
98 PC on the remote end.

Any thing else I should consider?

Thanks.

 

[Sarah]

Hi Mike

I'll see if I can explain this ... here goes

First I think you need to understand the purpose of WINS and LMHOSTS.

Basically, computers have names and these are referred to as NETBIOS names.
If you need to communicate with another computer on your network then
NETBIOS name resolution must take place. (NETBIOS name resolution is a
process that resolves a NETBIOS name to TCP\IP Address) There are in fact 6
ways this in which this can happen.

1) NetBIOS name cache
2) WINS
3) Broadcast
4) LMHosts File
5) HOSTS file
6) DNS

WINS is a dynamic way of maintaining NETBIOS \ TCP\IP information. If a
computer is configured to use a WINS server then the computer name and
TCP\IP address is automatically registered with the WINS Server. The WINS
Server must have a static IP Address but the Clients can be DHCP controlled.

LMHOSTS is not dynamic. You must configure the LMHOSTS file manually. The
LMHOSTS file is stored locally on each pc. This is not practical for large
networks. Any changes IP addresses must be reflected in the LMHOSTS file.
Larger networks use DHCP so you probably wouldn't find many LMHOSTS files on
these systems.

If you have none of the above on your network then the NETBIOS name
resolution will happen by Broadcast. The computer will send a broadcast to
everyone on the Local Network. One thing to mention about Broadcasts is that
they cannot go any further than your router.

So in answer to your questions

1) as far as I know you need the server version of windows for WINS
2) yes a WINS server requires a static IP Address
3) yes you need static IP addresses for LMHOSTS
4) there must be something available somewhere.. If I find anything I will
let you know.

Now, if you want to perform HOST name resolution then there are a different
set of rules.

I hope this helps.

Sarah

 

[Sarah]

Mike

No you don't have a PDC (Primary Domain Controller). You would only have
this is you had a domain but you are running a workgroup.

Sarah

 

[Sarah]

Mike

The following would be an example of a LMHOSTS file

192.168.0.1 computera #PRE
192.168.0.2 computerb #PRE

You don't have to add the #PRE at the end but if you do then when the pc
boots up the #PRE entries will be loaded into NetBIOS name cache. This will
make the name resolution process much quicker. If you go back and look at
the 6 ways in which names are resolved you will see that NetBIOS Name cache
is number 1 on the list. This is the first place the system will look for a
response.

Sarah

 

[Mike F.]

Thanks for your help Sarah! I'm back on track now.