Subject: 70-059 TCP IP 4.0
We passed this exam some days ago with a 982 (Carmen) and a 913 (Thomas), respectively. For preparation we mainly used the MOCs NT 4.0 and on TCP/IP.
We did the test the same time (4. 3.) and at the same testing centre. It seems,our tests were quite similar. Here are the questions we're able to remember:
1.) There were three scenario questions based on the same scenario:
Network with 100 workstations and 20 UNIX computers. UNIX computers never move,each Unix-hostname consists of no more than 15 characters, TCP/IP is protocol used. DHCP configured with one scope for each subnet. All Windows based computers are set up as DHCP clients.
Required results:
1) Every Windows based computer on each subnet must be able to access the Windows NT Server computers by computer name.
2) Every Windows based computer on each subnet must also be able to receive its IP address from the DHCP server.
Optional:
1) All UNIX systems should access by hostname any Windows NT Server computer that is set up as an FTP server.
2) All Windows based computers should access by hostname any UNIX computer that is set up as an TELNET or FTP server.
Scenario 1:
Proposed solution:
1) Set up network routers and forward DHCP broadcasts to all subnets
2) Install Wins server on the network
3) Install DNS server and configure it for name resolution
4) something else that is meaningless for the problem
Scenario 2:
Proposed solution:
1) Set up network routers and forward DHCP broadcasts to all subnets
2) Install Wins server on the network
3) Install DNS server and configure it for name resolution
4) Set up DHCP server to supply all DHCP clients with the IP address of both the WINS sever and the DNS server.
5) something else that does not meet the problem
Proposed Solution:
Like Scenario 1, additional
2) On the WINS server, make static mapping entries for UNIX computers.
3) On the DHCP server, exclude the UNIX computers' IP addresses from the
Scenario 3
Proposed solution:
1) Set up network routers and forward DHCP broadcasts to all subnets
2) Install Wins server on the network
3) Install DNS server and configure it for name resolution
4) Set up DHCP server to supply all DHCP clients with the IP address of both the WINS sever and the DNS server.
5) On the DHCP server, exclude the UNIX computers' IP addresses from the scope.
6) On the WINS server, make static mapping entries for UNIX computers
2.) Following entries in a HOSTS-file:
192.168.5.7 UNIX developer #ftp server
192.170.8.15 developer #server
With 'ftp developer' you can connect to the ftp server but not with 'ftp192.168.8.15'. Why?
3.) Similar to question 2.)
192.168.5.7 UNIX developer # server
192.170.8.15 developer #ftp server
Able to connect with '192.168.8.15' but not with 'ftp-server'. Why?
4.) LMHOSTS - file with '#' in front of the names. -> does not work
5.) How to configure a RAS - server that directly accesses the internet and uses PPTP. Clients access the RAS server via an ISP that is accessed with a modem.
-> PPTP filter
6.) 'netstat' analyses cumulatively
7.) Collect data packets to analyse them with a spreadsheet application -> performance monitor
8.) Clear the NETBIOS - cache -> NBTSTAT -R
9.) Show the NETBIOS - Cache -> NBTSTAT -c
8.) & 9.) (You need not know the switches)
10.) There is a net with the address 171.10.2.0
Remote clients cannot access a server in this net. You run IPCONFIG and
read:
IP address 171.10.2.223
Default Gateway 171.10.2.1
subnet mask 255.255.0.0
NETBIOS node type h
NETBIOS scope-ID (i.e. none)
WINS Client enabled
DHCP Client (we forgot)
...
Why does this configuration not work?
11.) Client A ------ router ------- Client B
routers left IP-address is 200.64.64.1, its right IP-address is 200.64.32.1.
Why can Client A not access client B? Its DG was 200.64.64.1
12.) Host ------- router ------ server
Class B net
host's IP : ...82.2
routers left IP-address is ...64.1, its right IP-address is ...32.1.
SM 255.255.240.0
Why can the host not access the server -> With this SM the host is in a different subnet than it's DG.
13.) DNS entry for a mail server -> MX
14.) Be aware of questions like: Which SM to use if you have 30 subnets and want to maximize the numbers of hosts per SM in a given net ID. Or the other way. You want to have a given # of hosts per subnet. Which SM would you use.
15.) You plan a internetwork. How many NET-Ids do you need? (Choose two)
one for each subnet
one for each host
one for each host' s NIC
one for each router' s interface
one for each WAN - link
16.) Two scenarios, where you want to enable a server to work as a router.
required result: routing must be possible
optional results: dynamical routing enabled
SNMP traps are to be sent to a SNMP - manager
16 a) Activate IP-forwarding
-> produces just the required result
16 b) activate IP-forwarding
-> produces the required result and one optional
17.) You want to audit a SNMP-Client by a UNIX host. What do you need. (choose two)
-> community name
-> IP - address of UNIX-hosts, that the traps have to be sent to
18.) What do you need to audit a printer connected to a UNIX - host ->
19.)You have a NT-Server, Windows-Clients and a printer connected to a UNIX-host. What do you need.
20.) What does an NT - client need to print op a printing device connected to aUnix host
21.) A PDC and several BDCs in different subnets must be able to 'see' each other without using wins. -> adequate #PRE and #DOM - entries in their LMHOSTS -files.
22.) You can ping a remote - client by using its IP-address but not by using its name, whereas you can ping all the other hosts in the remote subnet by IP-address as well as name. -> client is neither WINS-enabled nor does he have an entry of your computer in its LMHOSTS - file.
23.) UNIX - hosts must be made able to use wins for name resolution. DNS is already installed.
-> Use WINS resolution in DNS. (Be careful: They asked for WINS reverse lookup in this context, which is wrong)
24.) A client broadcasts to much to connect to other clients on the same subnet.
-> wrong subnet mask
25.) There are two subnets, each having a WINS-server. How do you configure the WINS-servers.
-> replication <--
-> make the other WINS-server a secundary WINS server
-> make entries in the LMHOSTS - files
26.) There are several subnets, each having its own DHCP-Server.
Required result: Each client receives its unique IP-address automatically
Optional result: DHCP - server must work even if one of them is down
26. a) Proposed solution:
Configure each DHCP-server to use the scope of another server as well
-> does not work; double IP-addresses possible
26. b) Proposed solution:
Install a DHCP-server that covers all the IP-scopes of all subnets. Do the same with all the other DHCP-servers
-> does not work, double IP-addresses possible
It proved very useful to write down a list with subnet masks, numbers of clients per subnet, etc. before you start the test. Each of us had about 4 - 5 questions on subnetting and this helps to save time.
Carmen & Thomas