Source code of Windows XP (NT5)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

71 lines
2.9 KiB

  1. # Copyright (c) 1994 Microsoft Corp.
  2. #
  3. # This is a sample LMHOSTS file used by the Microsoft TCP/IP-32 for
  4. # Windows for Workgroups 3.11
  5. #
  6. # TO USE THIS FILE, YOU WILL NEED TO RENAME IT TO "LMHOSTS" FROM
  7. # "LMHOSTS.SAM". THE SAMPLE FILE IS INTENTIONALLY NAMED "LMHOSTS.SAM"
  8. # SO THAT IT WOULD NOT CONFLICT WITH AN EXISTING "LMHOSTS" FILE.
  9. #
  10. # This file contains the mappings of IP addresses to computernames
  11. # (NetBIOS) names. Each entry should be kept on an individual line.
  12. # The IP address should be placed in the first column followed by the
  13. # corresponding computername. The address and the comptername
  14. # should be separated by at least one space or tab. The "#" character
  15. # is generally used to denote the start of a comment (see the exceptions
  16. # below).
  17. #
  18. # This file is compatible with Microsoft LAN Manager 2.x TCP/IP lmhosts
  19. # files and offers the following extensions:
  20. #
  21. # #PRE
  22. # #DOM:<domain>
  23. # #INCLUDE <filename>
  24. # #BEGIN_INCLUDE
  25. # #END_INCLUDE
  26. # \0xnn (non-printing character support)
  27. #
  28. # Following any entry in the file with the characters "#PRE" will cause
  29. # the entry to be preloaded into the name cache. By default, entries are
  30. # not preloaded, but are parsed only after dynamic name resolution fails.
  31. #
  32. # Following an entry with the "#DOM:<domain>" tag will associate the
  33. # entry with the domain specified by <domain>. This affects how the
  34. # browser and logon services behave in TCP/IP environments. To preload
  35. # a #DOM entry, it is necessary to also add a #PRE to the line.
  36. #
  37. # Specifying "#INCLUDE <filename>" will force the RFC NetBIOS (NBT)
  38. # software to seek the specified <filename> and parse it as if it were
  39. # local. <filename> is generally a UNC-based name, allowing a
  40. # centralized lmhosts file to be maintained on a server. If the server
  41. # is located outside of the local broadcast area, it will probably be
  42. # necessary to provide a mapping for the server prior to the #INCLUDE.
  43. #
  44. # The #BEGIN_ and #END_INCLUDE keywords allow multiple #INCLUDE
  45. # statements to be grouped together. Any single successful include
  46. # will cause the group to succeed.
  47. #
  48. # Finally, non-printing characters can be embedded in mappings by
  49. # first surrounding the NetBIOS name in quotations, then using the
  50. # \0xnn notation to specify a hex value for a non-printing character.
  51. #
  52. # The following example illustrates all of these extensions:
  53. #
  54. # 102.54.94.97 rhino #DOM:networking #net group's DC
  55. # 102.54.94.102 "appname \0x14" #special app server
  56. # 102.54.94.123 popular #PRE #source server
  57. #
  58. # #BEGIN_INCLUDE
  59. # #INCLUDE \\localsrv\public\lmhosts
  60. # #INCLUDE \\rhino\public\lmhosts
  61. # #END_INCLUDE
  62. #
  63. # In the above example, the "appname" server contains a special
  64. # character in its name, the "popular" servername is preloaded, and
  65. # the "rhino" servername is specified so it can be used to later
  66. # #INCLUDE a centrally maintained lmhosts file if the "localsrv"
  67. # system is unavailable.
  68. #
  69.