Guy Recommends
A solution to monitor, manage and archive thousands of
events that are generated by devices across the entire network.
Download FREE
trial
WINS (Windows Internet Name Service) in Windows 2003
My mission in this section is to explain the purpose of WINS in Windows Server 2003 network. In particular, I have tutorials to show you, where and why you need to configure WINS. The first point
to remember about WINS is that only Microsoft clients use WINS servers for name resolution, whereas Linux, Unix and everyone else on the internet, use DNS exclusively. To keep matters in perspective,
Active Directory, Exchange and IIS also require DNS. 95% of the time modern Microsoft products prefer DNS, but just occasionally they need to find a NetBIOS resource name - come in WINS. The 'killer' reason for implementing WINS is that Exchange, even Exchange 2003, needs NetBIOS name resolution.
Topics for WINS Servers in Windows 2003
 Learn more about WINS. As an MCT trainer, I can thoroughly recommend TrainSignal
because they provide practical hands on training. In particular, I like the way TrainSignal cover all learning methods, instructor lead, video and of course text
material. With TrainSignal you can either take one module, for example WINS or go for a combination of modules.
See more about WINS here
It goes without saying that you have to implement DNS, but that's another story. In this section I want to concentrate on WINS for those few occasions where NetBIOS name resolution is vital. While both WINS and DNS deal
with mapping ComputerName to IP addresses, there are two important differences; DNS is hierarchical and can support up to 254 characters, WINS, on the other hand, is a flat-field database limited to 15 letters.
One of the few advantages that WINS formerly had over DNS was that WINS is dynamic. Well, starting with Windows 2000, DNS is also dynamic, so the only point of WINS in the 21st century is specifically for
NetBIOS name resolution.
Keep in mind, especially when troubleshooting, the reason why we need databases such as WINS or DNS. The answer is name resolution. We humans prefer to remember friendly names like BigServer, whereas computers prefer IP addresses in dot decimal notation for example, 192.168.0.23.
Name resolution started with two files called 'hosts' and LMHosts files. The hosts file evolved into DNS and WINS took over the name resolution provided by LMHosts. Every Microsoft machine is
born with these files in the folder: %systemroot%\system32\drivers\etc\. Here is a typical entry for LMHosts. 10.54.94.13 bigserver
WINS is a service and as with DNS and DHCP, you install WINS via the Control Panel, Add or Remove Programs, Windows Components, Networking Services, Details --> WINS. The wizard will now
prompt you for the Windows Server 2003 CD.  Once
installation completes, you can find the Windows Snap-in in the Administrative Tools folder. What you are looking for is to make sure that the WINS Status is 'Responding'. Trap. In order for
the clients to find their WINS server, you need to check to see that the very WINS server is registered in its own database.
See how WINS adds records.
 Guy
recommends: The SolarWinds ipMonitor
My attraction to
ipMonitor is
because it inhabits that zone of part work, part
play; Guy just could not put the dashboard away. This excellent performance
monitor will get you started in the quest to remove bottlenecks on your network. SolarWinds provides this fully-functioning product free for 21 days. So
download
and install ipMonitor, then start scrutinizing your computers CPU, memory and disk
performance. You can also select from zillions more performance counters such as
fan temperature and battery level.
Installing ipMonitor is a breeze, but learn from gung-ho Guy's mistake and install SNMP
on each computer that you wish to monitor. What sealed my unreserved
recommendation of SolarWinds is their support team, you will get expert help even
when you are evaluating the ipMonitor.
Download SolarWinds ipMonitor (21 days eval)
The key technical difference is that Microsoft WINS servers use NetBIOS names whereas DNS relies on hostname. For years I thought that NetBIOS and hostname were one and the same.
Then one day I had a bizarre naming problem.
A mystery machine called 'goofy' appeared on the network. You could see it when you typed 'net view' at the command prompt. I identified it's IP address with ping, and traced its hostname in DNS. For the solution, I launched regedit and and found two different name settings, hostname and computername. (Computername is an alias for NetBIOS name.) Well on this particular machine, the
'user from hell' had managed to set hostname = machinebythewall and computername =
goofy. Just to emphasise, I have never seen different names for computername and hostname before or since.
WINS is an alternative to DNS for name resolution. You only need WINS if you have old Microsoft clients such as Windows 98, or servers that use NetBIOS name services. DNS is an superior system, and
is required by Active Directory,
Related WINS topics
|
