| Author |
Saturday W2K Professional Question of the Day
|
|
| mrfixit 2002-04-13, 8:45 am |
| Okay boys and girls, step right up! 
Todays question:
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. 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.There is no default gateway available. Use the Ping and Tracert utilities to test connectivity. Make sure that the router for the segment is functioning properly.
B.The machines are likely configured with static IP addresses. Change the machines over to DHCP clients to fix the problem.
C.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.
D.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.
Good luck! See you tomorrow! | |
| bbraunstein 2002-04-13, 9:18 am |
| First of all, my hat goes off to you, Mr. F, for posting such great questions!
I'll be first this morning...
Answer is "C".
As much as I would love to explain why, I'll hold off and let others take a crack at it.
BB | |
| mrfixit 2002-04-13, 10:57 am |
| quote:
Originally posted by bbraunstein
First of all, my hat goes off to you, Mr. F, for posting such great questions!
I'll be first this morning...
Answer is "C".
As much as I would love to explain why, I'll hold off and let others take a crack at it.
BB
Thanks! But I really can't wait for Frank to get back and take over again! | |
| denis_baribeau 2002-04-13, 11:37 am |
| By process of elimination it leave (C) the most logical answer due to the some work fine and other not so fine.
Pick (C)
PS explanation of answer would be most wellcome if avail. | |
| mcdoud 2002-04-13, 11:54 am |
| A would affect communications to other segments only.
B should not cause a problem unless somebody been changing the address/parameters.
D would only affect communications to other segments as well
C sounds reasonable.
C is my final answer! | |
| NetChild1985 2002-04-13, 12:16 pm |
| agree with "C" | |
| Pavlov 2002-04-14, 8:58 am |
| Going with C - WHY? Because it mentions APIPA - a new technology for Win2k right? Gotta be the one then. Too early to think of a better reason.  | |
| mrfixit 2002-04-14, 9:40 am |
| quote:
Originally posted by mrfixit
Okay boys and girls, step right up!
Todays question:
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. 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.There is no default gateway available. Use the Ping and Tracert utilities to test connectivity. Make sure that the router for the segment is functioning properly.
B.The machines are likely configured with static IP addresses. Change the machines over to DHCP clients to fix the problem.
C.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.
D.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.
Good luck! See you tomorrow!
And the answer is:
C
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 APIPA 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 APIPA). |
|
|
|