Be aware of the differences between DNS and WINS, and when to use either (or both). Make sure that you can properly configure one or more DNS, WINS and DHCP servers on one or more physical subnets. Brush up on your binary and be able to calculate subnet masks based on various customer requirements. [You're allowed to use the Windows calculator during the exam, but the Exclusively Online sidebar "Breeze Through Subnet Masking" suggests a better and faster method for calculating subnet masks.&emdash;Ed.] What are the differences between a HOSTS file and a LMHOSTS file? Last, know how to set up SNMP and TCP/IP-based printing in a mixed environment of both NT and Unix-based computers.
Tip: DNS is static, for "Internet-style" domain names such as www.microsoft.com; WINS is dynamic, for NetBIOS names like SERVER1. You do know that Windows NT 4.0 allows you to configure DNS to use WINS, don't you? Know the characteristics of primary, secondary and caching-only name servers.
Tip: You can use the broadcast method for name resolution only when both of the computers are on the same physical network, since broadcast messages are not usually passed by routers. WINS or DNS can both be used in routed environments.
One of the new features in NT Server 4.0 is the Network Monitor, which is used to determine problems during session initialization and broadcast storms. It also troubleshoots packets for transmission problems between computers. Know how to use Network Monitor, its limitations, and how it differs from Performance Monitor. (Performance Monitor measures your computer's efficiency, identifies and troubleshoots possible problems, and plans for additional hardware needs.)
Tip: You can only use Network Monitor to look at network traffic that your server generates or that is directed towards it. Also, make sure that you know the difference between the Network Monitor Agent and the Network Monitor Program.
Be aware of how to resolve various configuration problems bad IP addresses, bad subnet addresses, and bad default gateway addresses. Remember that your subnet mask determines when you'll use your default gateway (router) and when you'll attempt to establish a direct connection to another computer. Bad gateway addresses will keep you from communicating with other physical subnets but will have no affect on your ability to communicate with other computers on your physical subnet.
Know how to use the various diagnostic routines that are included with NT&emdash;IPCONFIG, NBTSTAT, NETSTAT, PING, ROUTE, and TRACERT. Unlike the current exam, the new version doesn't rely on trick questions about the various options of these diagnostic routines but is concerned with whether you know how to use each to solve different types of problems. Be able to calculate static routing tables and to diagnose name resolution problems.
Tip: Know the different methods that Windows NT uses for name resolution. For NetBIOS name resolution, a helpful mnemonic is: "No Where But LA Has Diversity" (NetBIOS name cache, WINS, Broadcast, LMHOSTS, HOSTS, NS).
For host name resolution, try: "Large Hard Drives Never Wear Black Lace" (LocalHostName, HOSTS, DNS, NetBIOS name cache, WINS, Broadcast, LMHOSTS). Know how the various node types change the default methods.
I'd have to say that I agree with Ryan Culloty, an MCP who also took the TCP/IP beta: "All in all, I thought the exam was pertinent to the knowledge necessary to be a successful Windows NT 4.0 TCP/IP administrator."