|
Home > Archive > 70-210 > October 2002 > Spid's Mon (10/7) Win2K Pro. QoD
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 |
Spid's Mon (10/7) Win2K Pro. QoD
|
|
|
| Hope everyone had a good weekend.
Continuing with the overlapping of subject material theme.....
Robertmiller has just been hired in to administer a network that includes 100 Windows 2000 Professional computers, 5 Windows 2000 servers and 2 NetWare servers.
The Windows 2000 Professional computers are configured with both TCP/IP and NWLink.
Several of the users are complaining that their response time when accessing resources on the Windows 2000 servers is very slow, but when they access resources on the NetWare servers, the response time is quite snappy. The users consistently access more resources from the Windows 2000 servers more frequently.
What should robertmiller do to improve performance of connections made to the Windows 2000 servers?
A. Move TCP/IP to the bottom of the network binding order on the Windows 2000 servers.
B. Move TCP/IP to the top of the netowrk binding order on the Windows 2000 servers.
C. Move TCP/IP to the top of the network binding order on the Windows 2000 Professional client computers.
D. Move TCP/IP to the bottom if the network binding order on the Windows 2000 Professional client computers.
Good luck and see you tomorrow for the answer. | |
| twister166 2002-10-07, 7:28 am |
| C.
This is a "TRUE" M$ solution, as long as mine works...  | |
|
|
| Slinky 2002-10-07, 8:33 am |
| C. | |
| denis_baribeau 2002-10-07, 8:34 am |
| Oui Oui
C it is. | |
| Deja-vue 2002-10-07, 9:59 am |
| C | |
| NetChild1985 2002-10-07, 10:10 am |
| Move TCP/IP to the top of the network binding order on the Windows 2000 Professional client computers | |
| tweetgirl 2002-10-07, 10:43 am |
| The answer is C. | |
| aklab 2002-10-07, 12:00 pm |
| C | |
| namrak 2002-10-07, 8:55 pm |
| Going with answer (C) as well. | |
| mcorpuz 2002-10-07, 9:12 pm |
| C looks correct to me. | |
|
| quote:
Originally posted by Spid
Hope everyone had a good weekend.
Continuing with the overlapping of subject material theme.....
Robertmiller has just been hired in to administer a network that includes 100 Windows 2000 Professional computers, 5 Windows 2000 servers and 2 NetWare servers.
The Windows 2000 Professional computers are configured with both TCP/IP and NWLink.
Several of the users are complaining that their response time when accessing resources on the Windows 2000 servers is very slow, but when they access resources on the NetWare servers, the response time is quite snappy. The users consistently access more resources from the Windows 2000 servers more frequently.
What should robertmiller do to improve performance of connections made to the Windows 2000 servers?
A. Move TCP/IP to the bottom of the network binding order on the Windows 2000 servers.
B. Move TCP/IP to the top of the netowrk binding order on the Windows 2000 servers.
C. Move TCP/IP to the top of the network binding order on the Windows 2000 Professional client computers.
D. Move TCP/IP to the bottom if the network binding order on the Windows 2000 Professional client computers.
Good luck and see you tomorrow for the answer.
And the answer is.....C
From the question we can determine that TCP/IP is the more frequently used protocol, and since communication is initiated from the clients to the servers, the binding order on the client computers will effect performance (or is it affect, I always mix the two up)
If NWLink appears at the top of the binding order and the client attempts to communicate with one of the Windows 2000 servers, it will attempt to communicate using NWLink first. The request will time out, because NWLink is not installed on the Windows 2000 servers, and the client will then attempt to communicate via TCP/IP.
Also remember, that unless specified, assume the defaults are in place. In this case, TCP/IP is the default protocol for Windows 2000, and no mention was made that NWLink was installed on the Windows 2000 servers. |
|
|
|
|