|
Home > Archive > 70-216 > February 2002 > WINS Question
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]
|
|
|
| I know this question has been posted before, but I just want to confirm my answer?
You are the administrator of your company's network. The network consists of Windows 2000 Server computers, Windows NT Workstation client computers, and Windows for Workgroups 3.11 client computers distributed across three subnets. All client computers are configured as DHCP client computers to automate TCP/IP configuration. You install a WINS server on one subnet on your network. You also define a DHCP scope option to include the WINS server's address. Users report that they can access resources on servers on their own subnet, but they cannot access resources on other subnets.
What should you do to resolve this problem?
A. Use the ipconfig /renew command to refresh the client computers configuration
B. Use the ipconfig /release command to refresh the client computers configuration
C. Install a WINS proxy agent on the subnet that hosts the WINS server
D. Install a WINS proxy agent on the subnets that do not host the WINS
server
E. Enable dynamic updates on the wins server
Answer: A ? | |
| merav21 2002-02-21, 6:23 pm |
| yes i would have to agree with your answer, A.
the question is kind of vague, if they specified that some of the machines on each subnet are b-node or broadcast nodes i would say the answer would be putting a wins proxy on all the subnets- but thats not the case.
also they didn't say whether you had made the changes on the dhcp scope before the workday/or booted up. since i am assuming the changes were just made- i would agree with A. | |
| jeff_j_black 2002-02-21, 6:41 pm |
| This is a perfect example of some questions where none of the answers are the complete solution and you just have to pick the best one.
IPCONFIG /RELEASE would not fix the problem.
Nor would adding WINS proxies anywhere.
They toss WINS Proxies into alot of questions, trying to trip you up on your understanding of DHCP proxies.
WINS Proxies register with the WINS server on behalf of clients that don't register with WINS. (Examples: OS/2 or Unix clients) This is not related to what subnet they are on.
So the remaining answer, IPCONFIG /RENEW is the best answer, even tough you might be accustomed to seeing this only in conjunction with the IPCONFIG /RELEASE command being issued first. | |
| Zaraspook 2002-02-21, 7:49 pm |
| How about A.
Ipconfig /renew would force the clients to renew their DHCP lease and acquire the new WINS address from the newly configured scope option. | |
| trogers5 2002-02-22, 6:46 am |
| I agree with the other posts, the answer has to be "A". Its a IP configuration issue. B would not solve the problem releasing IP info.
Options C and D Wins Proxies are only used for non.wins clients. I agree with the earlier post that Wins proxies are there to confuse you. You only need them with clients that do not support Wins, OS2, Unix, Lan Manager.
E,is wrong you cannot enable dynamic updates on a Wins server. | |
| Djalminha 2002-02-22, 11:55 am |
| Me and my shadow go with D,
There are only legacy client computers (Windows 3.11 and Windows NT), on each subnet. Note that the client computers trying to resolve a computer name, will first check its cache to see if the name is listed there, next, the name server is queried. If WINS can’t resolve it, or don’t exist, a broadcast is made. Most routers are not configured to forward broadcasts.
A WINS proxy listens for b-node broadcasts, and attempts to use its cache to resolve name queries for computers that are not located on the local subnet. If the WINS proxy cannot resolve a query using its cache, then it forwards the query to a WINS server for resolution.
Because WINS servers do not recognize broadcasts, WINS proxies should be installed both on subnets that do not include WINS serves and on subnet that include WINS server, and contains b-node clients.
reference:
Windows 2000 help, key words: "networking, wins, understanding wins, wins proxies"
Windows 2000 Resource Kit, k w "Microsoft WINS Servers, WINS proxy"
Sorry about my english
{}'s Kenji | |
|
| I'll have to disagree with you Djalminha...
Djalminha said: quote:
Me and my shadow go with D,
There are only legacy client computers (Windows 3.11 and Windows NT), on each subnet. Note that the client computers trying to resolve a computer name, will first check its cache to see if the name is listed there, next, the name server is queried.
I still think A
A WINS Proxy will intercept NetBIOS name resolution requests, and forward them to a WINS server. WINS Proxy agents are normally used to provide the name resolution (via a WINS server), for non-WINS enabled clients. Windows 3.11, 95/98, NT, and Windows 2000 are all able to use WINS hence D being the wrong answer (in my opinion).
For example, if the network had Unix workstations, they would require a WINS client to act as a WINS Proxy in order to provide the name resolution.
Does everyone else agree? | |
| trogers5 2002-02-22, 3:06 pm |
| I agree with you. Bottom line all the operating systems in the scenario support WINS. Thus, a WINS Proxy would not apply in this case.
Yes! Win3.1 is compatible with WINS. You can not use WINS Proxy with WIN 3.1 | |
|
|
|
|  Good link Frank!
I think that's enough to keep me happy with my choice A. The fact the scope has been changed to contain an additional WINS server address gives away the answer and the rest of the question is trying to confuse the core problem at hand. Obviously the existing computers haven't received the new addition to the WINS scope as they haven't renewed yet.
Frank: Got any good teaser's on DNS? |
|
|
|
|