name resolutions

[Jaco]

i'm having a problem with name resolution with WINS ,DNS etc.<br>all the pc's can connect through IP addresses but not through machine names.when i ping a machine name it gives me a reply from the loopback address (127.0.01)and not the IP address.<br>in which order does name resolution work?<br>cache, hosts files,wins, dns<br>for all the network software to work must i know change all machine names to IP addesses in their network configuration of the software.<br>

 

[voland]

Here's the sequence for resolving NetBIOS names under NT:<br><br>1. Cache<br>2. WINS<br>3. Broadcast<br>4. LMHOSTS<br>5. HOSTS<br>6. DNS<br><br>This is a NORMAL DEFAULT sequence, which can be modified through the registry to have the resolution go through - say, - Broadcats first, and WINS second.<br><br>If you'll give a little more info about your network configuration as well as check the entries in your LMHOSTS/HOSTS files I might be able to help you more.<br><br>Regards!

 

[dxd]

Are you actually running a Wins server? Either Wins or Lmhosts is responsible for Netbios / Machine Name resolution. DNS is used to resolve fully qualified domain names to an IP address or IP to FQDN. Can you ping the FQDN...i.e - computer.domain.com(or whatever root domain you are in)??<br><br>

 

[voland]

Actually, if we're talking about the MACHINE NAMES, FQDN concept is not applicable - it's used for host names only. Also, DNS and Hosts file - while used primarily for host name resolution, WILL be queried by NT machine if during steps 1-4 the machine name has not been resolved. In this case, if machine name (computer name) matches host name (assigned to network adapter in TCP/IP stack) it will be resolved by DNS/Hosts file.<br><br><br>Regards!