"Yba" <> wrote in message news:1584E3AC-C10A-4202-A3D3-...
> 
> Not really. I was just trying to put pieces together for me to understand
> how IP resolving operates.
>
> Thanks a lot, you have answered my question and curiosity, and I hope I have
> answered yours 
>
> Yba
You are welcome. And yes, it does answer my question. I would hate to see you try to use a hosts file.
If your question was based on the resolution process, you should have said so. My following blog should help...
================================================== ================================================== ==
DNS & WINS Resolution Process
Keep in mind, Win2000 and newer machines uses the DNS process FIRST. If it does not get resolved using the DNS process, then it uses theh NetBIOS process. Legacy clients use the NetBIOS process FIRST, and if it doesn't get resolved using NetBIOS, it uses the DNS process.
If you are using an NBNS (NetBIOS Nameserver, such as WINS), that changes it a bit, and it also depends on what Node it's in. H-Node is default, but can be changed. There are four NetBIOS Nodes:
B-Node - Broadcast ONLY
P-Node - NBNS (Netbios Nameserver) or WINS ONLY
M-Node- Mixed NBNS and Broadcast, but uses Broadcast FIRST.
H-Node - Mixed NBNS and Broadcast, but uses WINS FIRST.
E.g. If you ping "machinename" on a Win2000 or newer machine, it will attempt to use DNS FIRST:
1. Checks it's own name.
2. Local cache.
3. HOSTS file
4. It will then suffix the Search Suffix configured on the machine, then query DNS
5. WINS
6. Broadcast
7. LMHOSTS
Legacy machines (pre-Windows 2000) use NetBIOS first.
NetBIOS and Hostname resolution for Microsoft Client and LAN Manager 2.2c Client:
http://support.microsoft.com/kb/169141/EN-US/
Name Resolution Process in detail:
http://www.comptechdoc.org/os/window.../wtcpname.html
================================================== ================================================== ==
Ace