When using TCP/IP as your protocol, there are two ways in which Microsoft resolves names to IP address. There is a Winsock name resolution process, which is used in cases like the PING command, DNS names (server.somedomain.com), and FTP. And there is NetBIOS name resolution, like when you use a NET command (\\servername\sharename) or FIND .
The Winsock resolution sequence is as follows:
1. Hosts file
2. DNS (it will only check DNS if you have enabled DNS lookup on the client, otherwise this step is skipped)
3. WINS (only if manually specified on the client or by a DHCP server, otherwise this is skipped)
4. Broadcast (I'm looking for \\computername, if you are \\computername, please respond with IP address)
5. LMHOSTS
6. Second DNS request
7. Resolution fails
NOTE: If at any time in this process the name is resolved, the process stops.
The NetBIOS resolution process is as follows (which is the process that occurs for resolving a computername):
1. WINS
2. Broadcast
3. LMHOSTS
4. DNS
5. HOSTS
6. Repeat steps 1-5 a second time
7. Fail
Since you are using WINS, you should see little delay in the resolution of the name. The fact that there is a noticeable delay may mean the WINS is not configured properly, either on the client or the WINS server itself, or the WINS server is very busy.