|
Home > Archive > Windows 2000 track general > May 2001 > Lmhosts
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| fessy86 2001-05-30, 3:53 pm |
| Can someone please explain to me why one would want to edit the LMHOSTS file? I am not quite understanding it. Like what is the purpose of it? Any feedback is mucho appreciated.
jesse | |
| SasiSan 2001-05-30, 8:21 pm |
| Use it to preload into the machine netbios names and to register domains (#PRE and #Dom:xxx)...
Scenario: Medium size network -- PDC is also the WINS server. BDC is Exchange server. Situation works fine except for 8:00 - 8:30 in the morning when everyone logging on and opening mail. Outlook configured to connect to a computer named XXX_Mail -- default timeout is 30 seconds. Clients WINS enabled.
Here is what happens. WINS doesn't respond to the first two queries because it is busy validating logins... 3 tries at 15 secs each -- causes the machine to timeout. Clients get a message saying that server XXX_Mail not found, Retry? or Abort? -- contact you system admin because the server might be down. Common sense says click retry and you will get in...
By preloading the name of the PDC and BDC (XXX_MAIL) the WINS query never executes because the resolution is already sitting in the local cache (nbtstat)... Network traffic reduced, everyone works faster...
-- this is just one scenario -- also load in addresses of servers in other subnets so that your clients can find them...
I have had good luck with LMHOST on slower networks where other solutions were not practible...
Hope this helps... | |
| freak 2001-05-31, 10:42 am |
| quote:
Originally posted by SasiSan
Use it to preload into the machine netbios names and to register domains (#PRE and #Dom:xxx)...
Scenario: Medium size network -- PDC is also the WINS server. BDC is Exchange server. Situation works fine except for 8:00 - 8:30 in the morning when everyone logging on and opening mail. Outlook configured to connect to a computer named XXX_Mail -- default timeout is 30 seconds. Clients WINS enabled.
Here is what happens. WINS doesn't respond to the first two queries because it is busy validating logins... 3 tries at 15 secs each -- causes the machine to timeout. Clients get a message saying that server XXX_Mail not found, Retry? or Abort? -- contact you system admin because the server might be down. Common sense says click retry and you will get in...
By preloading the name of the PDC and BDC (XXX_MAIL) the WINS query never executes because the resolution is already sitting in the local cache (nbtstat)... Network traffic reduced, everyone works faster...
-- this is just one scenario -- also load in addresses of servers in other subnets so that your clients can find them...
I have had good luck with LMHOST on slower networks where other solutions were not practible...
Hope this helps...
I have a full study guide on my site on name resolution. Download for free if you want, it also incorporates LMHOSTS info in it, and it is only 3 pages long. That is what I use to teach all the MCSE classes...
Let me know if you need more help  | |
| Tekmazter 2001-05-31, 3:26 pm |
| Just a quick note. Many networks now don't use the LMHOSTS file to its full extent. However, if you are having a NETBIOS name resolution problem say with your WINS server, you can use the LMHOSTS file as a workaround until you get the chance to dig deeper into what the problem may be. By manually mapping the IP to NETBIOS computer name, you can really get out of a bind in a hurry if it's an isolated incident, say 3 or 4 machines. This may be one reason to edit the file. |
|
|
|
|