|
Home > Archive > 70-210 > May 2003 > Network...TCP/IP
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
|
| Question:
You are the Windows 2000 Professional Administrator for your company. You configure all the Windows 2000 Pro computers to use TCP/IP as the only protocol for communication. One of the computers consistently gets into errors when communicating with other network hosts. Which of the following tools / commands can provide you with a detail way to identify TCP/IP configuration problems?
A) ping
B) tracert
C) netstat
D) application log
E) system log
F) None of the choices.
Answer: E
According to Microsoft: When you use TCP/IP as your network protocol, an incorrect TCP/IP setting (such as an incorrect IP address or an incorrect subnet mask) can cause communication problems. To determine whether Windows NT or 2000 has recorded an error due to an incorrect TCP/IP setting, examine the Event Viewer system log and look for any entry with TCP/IP or DHCP as the source. To read an Event Viewer entry, double-click the entry.
Why not B & E
Dose the tracert is wrong as another answer to this question? Why?
Thanks | |
| DaPunisher 2003-05-15, 9:41 am |
| Tracert is used to find bottlenecks in a network. Unfortunately, thats about it. The System log will go into great detail as to why a certain error occured, which is what the question is asking for.
I hope this helps. |
|
|
|
|