person one:
Here s what I can remember: 1. Your company has two WINS servers already installed. You need to install a new WINS server to connect to the internet. How will you configure it?
a. Primary WINS
b. Secondary WINS
c. Caching only
d. Forwarder
(I guessed c. But again I guessed , so be sure to check the answer)
2. Which of the following are valid IP addresses, and which are not? (A drag and drop problem, Cute!)
203.122.153.1 (Valid)
127.96.185.20 (Invalid...Starting octet cannot be 127)
150.206.256.3 (Invalid...An octet cannot exceed from the value 255)
175.207.180.6 (Valid)
3. Your company s subnet mask is 255.255.248.0. Your subnet contains a blend of Windows NT and UNIX machines. You have already assigned them IP addresses from 175.60.8.21 to 175.60.8.49. You want all your Windows NT machines to be assigned IP addresses automatically. Create a scope that consumes all the IP addresses in this subnet. (Another drag and drop situation, where you have to drop the IP addresses in the DHCP scope properties screen)
Include range
From 175.60.8.1 ( 10101111.00111100.00001000.00000001 )
To 175.60.15.254 ( 10101111.00111100.00001111.11111110 )
Exclude range
From 175.60.8.21 To 175.60.8.49
(Make good use of the calculator, or your bust)
4. There were two questions from the transcenders, that a computer person two:
I used no books recommended by other members. Just the brain dumps to help me focus on what I ought to know.I used general networking with UNIX TCP/IP knowledge with some NT utilities and that was all.In my thoughts I think TCP/IP is TCP/IP no matter waich Operating system.
Here we go
1)A lot of command line utilities: ARP, NETSTAT, NBTSTAT, NSLOOKUP (know these) as well as PERFOMANCE MONITOR and NETWORK MONITOR. In my test mostly I answered NETSTAT when it appeared.
