from
http://www.svrops.com/svrops/documents/hostsdoc.htm#Setting%20Up%20LMHOSTS%20Files
====================
The following example shows how all of these keywords are used:
102.54.94.98 localsrv #PRE
102.54.94.97 trey #PRE #DOM:networking #net group's PDC
102.54.94.102 "appname \0x14" #special app server
102.54.94.123 popular #PRE #source server
#BEGIN_ALTERNATE
#INCLUDE \\localsrv\public\lmhosts #adds LMHOSTS from this server
#INCLUDE \\trey\public\lmhosts #adds LMHOSTS from this server
#END_ALTERNATE
In the preceding example:
The servers named localsrv and trey are preloaded so they can be used later in an #INCLUDE statement in a centrally maintained LMHOSTS file.
The server named "appname \0x14" contains a special character after the 15 characters in its name (including blanks), so its name is enclosed in quotation marks.
The server named popular is preloaded, based on the #PRE keyword.
Additional Comments
LMHOSTS example:
IP Address PDCName #PRE #DOM:domainname
IP Address "domainname,,,,,\0x1b" #PRE
Where IP Address is the address of your PDC.
PDCName is the name of your PDC
domainname is the name of your Domain
and
domainname,,,,, is also the name of your Domain. However, the commas represent spaces, and in this line, your domainname must be 15 characters. If it isn't, pad it with the appropriate number of spaces to reach 15 characters.
And...use the quotes
Your PDC acts as the Domain Master Browser, and as such, should have the browse lists of all Segment Master Browsers (if you have a multi-segment network), thus a list of all network devices.
The above LMHosts file tells your PC the name of the logon domain controller (your PDC), and the second line says use the PDC as your browse master.
If you can ping your PDC and net use a share to the PDC, then the above should work.
Saturday, December 15, 2007
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment