譯文：
問題.我閱讀了許多關於windows 2000 不再需求WINS服務器的文檔，因爲windows 2000服務器使用DNS代替了WINS。聽起來感覺我不再需要一個WINS服務器，我可以使用DNS代替WINS的一切功能。這是真的嗎？
回答.這個問題說簡單很簡單，說複雜也很複雜。簡單的回答是“是的”，你可以運行一個沒有WINS服務器的Windows 2000的網絡作爲遠程NetBIOS名稱解析的解決方案。但是說起來簡單，做起來卻不容易。
運行一個沒有WINS的網絡，你應該將所有的機器升級爲Windows 2000的計算機。尤其是你不能在這個網絡裏擁有任何低級別的Windows 操作系統。因爲這些低級別客戶端是依賴於NetBIOS作爲重要域關係激活的，例如登陸驗證和本地服務。
你還必須確定在你的網絡裏運行的系統沒有任何依賴於NetBIOS服務的機器，不管機器系統是否爲Windows 2000.如果在你的網絡裏有機器運行的程序和服務依賴於NetBIOS名稱解析，那麼你在你的網絡裏保留WINS服務器。
由於低級別windows操作系統可以使用DNS解析NetBIOS名稱，所以你可以在這些情況下可以運行一個沒有WINS服務器的網絡。但是這裏有一些與之有關的困難：
1. 低級別的操作系統不能像windows 2000那樣自動的使用DNS服務進行名稱註冊。
2.名稱解析速度也許變得讓人無法接受的慢。記住NetBIOS名稱解析的順序：
NetBIOS Remote Name Cache
WINS
Broadcast
LMHOSTS
HOSTS
DNS
正如你看到的，DNS查詢將在其他方法進行之後被執行。並且，在任何適當大小的網絡裏，使用靜態文件，例如HOSTS或者LMHOSTS成爲一種簡潔管理的辦法。
你可以在DNS服務器上使用DHCP動態註冊低級別客戶端名稱，並且你可以通過使低級別系統稱爲B節點客戶端來解決第二個問題，以便他們不需要花時間去宣召WINS服務器。
然後，你最好的做法是等待直到你得網絡裏使用的全部是windows 2000系統的計算機，並且你已經消除網絡中所有依賴於NetBIOS的應用程序。在那時，你可以讓你的WINS服務器退役了，然後禁用網絡裏所有客戶端的NetBIOS接口。當你那麼做的時候，真正的好事情發生了，例如Browser服務成了不在需要的功能了。
原文：
Q. I've been reading a lot about how Windows 2000 no longer requires a WINS Server because the operating system now uses DNS instead of WINS. This sounds like I don't need to use a WINS Server anymore, and can just use DNS for everything that I used WINS for. Is that true?
A. This question is both a simple one and a complex one! The simple answer is "Yes", you can run a Windows 2000 network without using a WINS Server for remote NetBIOS name resolution. However, this is a lot easier said than done.
To run a WINS-less network, you should have all the machines be Windows 2000 computers. Specifically, you should not have any downlevel Windows operating systems on the network. This is because the downlevel clients are dependent on NetBIOS for important domain related activities such as log on authentication and service location.
You must also be sure not to have any NetBIOS dependent services running on the machines on your network, whether the host operating systems are Windows 2000 or not. If you have machines that run programs and services that are dependent on NetBIOS name resolution, then your best bet is to keep a WINS Server on the network.
You could run without a WINS Server in these situations, because downlevel Windows operating systems are able to use DNS to resolve NetBIOS names. However, there are some difficulties associated with this:
1.The downlevel operating systems are not able to register themselves dynamically with DNS like the Windows 2000 computers are able.
2.Name resolution may become unacceptably slow. Remember the NetBIOS name resolution sequence:
NetBIOS Remote Name Cache
WINS
Broadcast
LMHOSTS
HOSTS
DNS
As you can see, DNS lookups are performed last, after other methods are employed. Also, in any reasonably sized network, using static files such as HOSTS or LMHOSTS becomes an administrative straitjacket.
You could solve the first problem by using DHCP to dynamically register the names of the downlevel clients in the DNS Server, and you could help with the second problem by making the downlevel systems b-node clients, so that they don't spend time looking for a WINS Server.
However, your best bet is to wait until you have all Windows 2000 computers on your network, and that you have also eliminated all NetBIOS dependent application on your network. At that point, you can decommission your WINS Server, and then disable the NetBIOS interface on all your network clients. When you do that, really good things happen, like the Browser Service no longer functions!
****不足之處，請多多指教****