Discussion Locked

wins(network) ip address

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi,
I have a windows nt4.0 environment.
I noticed that most computers on the network when they use an ip address they connect very quickly. When they try connecting by computer name it takes time to connect.
I do have wins running on the pdc..Is there a reason for an ip address to connect over the network quicker than by computer name?
Any help would be appreciated.

7 replies

by greybeard770

Name resolution. When you connect by name, some source (WINS in this case) has to resolve that name to an IP address before it connects. But before it gets to WINS, it will try DNS and a few other sources before it gets down to WINS. No, there isno way to change the search order.

At one time we had to add the Exchange server IP address to a local hosts file to speed up resolution. Even though it wasn't listed on the DNS server it had to look there anyway. By the time it worked its way down to WINS, it would have timed out.

I have been searching for a long time for a utility that would resolve names to IP addresses and give the source of the information. That way you would know where to direct your name resolution trouble shooting.

by emeraldway tech

If you are using DHCP make sure the WINS server is identified. If your are not using DHCP make sure that you have manually entered the information into the network settings. If this information is not populated the computers will not reference nor update the WINS server. Anytime you connect to machine via IP address you are going directory to it. When there is no ip to name resolution, the only way to find a machine is via broadcast. Which can be much slower in larger network. WINS creates a database to store this name to IP resolution reducing the broadcast needed to identify the machine.

by nettek

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.

This discussion is closed to new replies.