|
Home > Archive > 70-216 > August 2002 > Wed 70-216 Question of the Day
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]
| Author |
Wed 70-216 Question of the Day
|
|
| wbafrank 2002-07-31, 3:16 pm |
|  And today's poser is ....
Q21. Upon arriving at work one morning, you find that some of your users are complaining about connectivity problems. It turns out that they can communicate fine with some of the other machines on their network segment, but are having trouble communicating with other machines on their network segment. Furthermore, they are unable to access any network resources on other segments. What is most likely the issue here and how would you best resolve it?
A. The switch that the computers are connected to has broken. Replace the switch and reconnect each system to the new switch.
B. Make sure that a WINS Server is available for all of the clients on the segment. Windows 2000 clients rely heavily on NetBIOS resolution and the lack of an available WINS Server could cause connectivity problems.
C. The machines are likely configured with static IP addresses. Change the machines over to DHCP clients to fix the problem.
D. Some machines may have received Automatic Private IP Addresses. Use the Ipconfig utility to determine what IP addresses they have been assigned and check to see if a functioning DHCP server is available for their segment.
Good Luck .... see you tomorrow for the answer!! | |
| buckwheat 2002-07-31, 3:27 pm |
| I'd have to go with D. The other three are either unlikely or invalid choices. | |
| Pavlov 2002-07-31, 3:51 pm |
| Gonna agree with D. | |
|
| How about "D"  | |
| unreal 2002-07-31, 7:00 pm |
| It should be 'D' | |
| River19 2002-08-01, 10:16 am |
| I'm gonna go with D also.
If the switch were bad, NONE of the computers would be able to connect to each other.
Windows 2000 relies heavily on DNS for name resolution, not WINS.
The static IP scenario theortically COULD cause those problems, but is highly unlikely in this situation.
D is the only logical choice. | |
| wbafrank 2002-08-01, 3:55 pm |
| quote:
Originally posted by wbafrank
And today's poser is ....
Q21. Upon arriving at work one morning, you find that some of your users are complaining about connectivity problems. It turns out that they can communicate fine with some of the other machines on their network segment, but are having trouble communicating with other machines on their network segment. Furthermore, they are unable to access any network resources on other segments. What is most likely the issue here and how would you best resolve it?
A. The switch that the computers are connected to has broken. Replace the switch and reconnect each system to the new switch.
B. Make sure that a WINS Server is available for all of the clients on the segment. Windows 2000 clients rely heavily on NetBIOS resolution and the lack of an available WINS Server could cause connectivity problems.
C. The machines are likely configured with static IP addresses. Change the machines over to DHCP clients to fix the problem.
D. Some machines may have received Automatic Private IP Addresses. Use the Ipconfig utility to determine what IP addresses they have been assigned and check to see if a functioning DHCP server is available for their segment.
And the answer is ....
Correct Answer: D
Automatic Private IP Addressing can assign a TCP/IP address to DHCP clients automatically. However, Automatic Private IP Addressing doesn't generate all the information that typically is provided by DHCP, such as the address of a default gateway.
Consequently, computers enabled with Automatic Private IP Addressing can communicate only with computers on the same subnet that also have addresses of the form 169.254.x.y (addresses that have also been assigned through Automatic Private IP Addressing).
If the switch was broken, they could not communicate with other systems on their subnet. |
|
|
|
|