In article <3217F04D....@WyldFyre.Com>, L...@WyldFyre.Com says...
>Uwe Ackermann wrote:
>> Hello There,
>> I have a problem to run the WINS protocol(Domain service) over TCP/IP
>> instead
>> of using the NETBEUI interface.
>> Can somebody tell me, how to configure that?
>> Do I need to switch off the bindings for Netbios to the
>> NETBEUI interface?
>> Any help would be great.
>> Uwe
>> ****************************
>> Uwe Ackermann
>> Motorola GmbH
>> Munich Germany
>> ttg...@email.sps.mot.com
>I will try my best at this. Check in your C:\WINNT\SYSTEM32\DRIVERS\ETC
>Directory. There will be a file called LMHOSTS.SAM. Copy this file as
>just LMHOSTS with no extensions. Then, Edit this File. This file will
>explain how to add the WINS part Over TCP/IP. After adding and editing
>this file, run NBTSTAT -R and then NBTSTAT -c (upper case on the R and
>lower on the c). The NBTSTAT -c command will print out your cache and
>confirm that WINS has been installed for the computers you specified. If
>you need more help, feel free to ask via E-MAIL.
The lmhosts file is a static file used to resolve NetBIOS names to IP
addresses. It is the equivalent to the hosts file (used to resolve DNS
host names to IP addresses). It becomes a maintanance nightmare in a
middle to large network and is pretty much useless, when HDCP is used
to assign IPs dynamically. In these cases, WINS is a better solution.
WINS is a system to provide dynamic NetBIOS name registration and
resolution. When a WINS client comes online, it contacts the WINS Server
and registers its name and current IP. When a WINS client needs to
resolve a NetBIOS name to an IP, it contacts the WINS Server for the
current address associated with the name. If the WINS Server can't
resolve the name, the client will fall back on its lmhosts file, if it
exists (broadcasting may also be done, if the lmhosts fails).
If you are not using NetBEUI, then the NetBIOS bindings to NetBEUI are
irrelevant.
Install WINS on an NT Server with a static IP. Leave the WINS Server
entries in the WINS Server's TCP/IP settings blank.
On all WINS Clients, set the Primary WINS Server to your WINS Server's
IP. If you are using DHCP on the LAN, you can do this automatically
through DHCP.
As long as your LAN is routing TCP/IP correctly, that should be all
there is to it.
--
John R Buchan
j.buc...@worldnet.att.net
