Subject: 70-59 TCP/IP in NT 4.0

Many thanks,

I have a lot of experience in TCP/IP in NT 4.0 but braindumps really zeroedin on the tricky stuff, so pay attention to this site.

Most of the stuff here are correct, but I got 2 incorrect answers and I think this is about the:

(1) WINS replication between Dallas and Seattle, I think that only the primary result was served and none of the optional results. There's something about a push replication when Dallas (or Seattle) hits 50,000 changes; while 50,000 changes for a 1,000 node network seems big, this is still undeterministic. And so a once every 24 hours replication (an optional result) will not be met.

(2) The scenario of three segments and two NT servers, you have to choose the right "route" commands, I got cross-eyed with this one. You can readily eliminate two choices by knowing the proper "route" options.

Other stuff:

1. Use Perfmon for gathering stats and exporting to excel
2. Use Netmon for real-time stats
3. Use netstat to get Ethernet stats since last boot-up
4. Lots of WINS stuff
5. TCP, IP, ICMP are added to Perfmon when SNMP is installed
6. Hybrid node uses WINS first before broadcast, Mixed node uses broadcast first before WINS, B-node uses brodcast only, P-node uses WINS only.
7. Brodcast only works in its own network segment, cannot traverse routers.
8. LPQ - to monitor printer queue
9. LPR - to let NT print to a Unix printer (or any printer w/ builtin LPD)
10. TCP/IP Printer services - to let Unix print to printer connected to NT
11. Lmhosts - know its syntax
12. Hosts - multiple names are ok in a single line
    Sample:
    1.1.1.1 ns devp
    2.2.2.2 devp ntsrv
    -> if you ping devp, you'll get 1.1.1.1 instead of 2.2.2.2
13. There is only one primary DNS server, several secondary servers are OK, a caching only server does just like that, a forwarder receives requests from DNS servers that cannot resolve queries.
14. Know what PPTP is, (and versus NT authentication)
15. WINS Proxy - queries a WINS server to respond to broadcasts by workstations not configured to use a WINS server.
16. You can use one WINS server to serve multi-segment networks
17. several questions on bad subnet masks