[SLUG] RH 7.1, Win 98, and Samba

From: SOTL (sotl155360@earthlink.net)
Date: Sat Aug 18 2001 - 13:32:58 EDT


I need a little help with the Win 98 side of Networking Samba on my RH 7.1
system.

If thinking of Win 98 offends you please delete the message now.

Anyway, the problem is I can not see the Linux server from Network
neighborhoods in the Win 98 box.
I have tracked part of the problem do to the fact that I do not have
C:\WINDOWS\lmhosts in the Win 98 box configured correctly.

The second following this is MS generatic lmhosts file and is included for
reference.
The first file is what I think it should be.

Problem here is two fold: First, I am not sure my idea of how the file should
read is correct.
Second, I am a coward with things I do not know about.
If I screw it up, I am not sure I know enough to straighten it up.
So I am requesting those who know of such things to review my perceived
lmhost file for stupid mistakes.
Please help I have no desires to reprogram this Win box. I do not like it
but I can not get rid of it.

Thanks
Frank
______________________________________________________

Frank's preceived C:\WINDOWS\lmhosts file

192.168.1.1 lan_sys_opt #PRE #DOM:office_lan
192.168.1.2 lan_user1 #PRE
#
#BEGIN_ALTERNATE
#INCLUDE \\lan_user1\public\lmhosts
#INCLUDE \\lan_sys_opt\public\lmhosts
#END_ALTERNATE
           ------------------------------
MS Generatic C:\WINDOWS\lmhosts file.

# Copyright (c) 1998 Microsoft Corp.
#
# This is a sample LMHOSTS file used by the Microsoft Wins Client (NetBios
# over TCP/IP) stack for Windows98
#
# This file contains the mappings of IP addresses to NT computernames
# (NetBIOS) names. Each entry should be kept on an individual line.
# The IP address should be placed in the first column followed by the
# corresponding computername. The address and the comptername
# should be separated by at least one space or tab. The "#" character
# is generally used to denote the start of a comment (see the exceptions
# below).
#
# This file is compatible with Microsoft LAN Manager 2.x TCP/IP lmhosts
# files and offers the following extensions:
#
# #PRE
# #DOM:<domain>
# #INCLUDE <filename>
# #BEGIN_ALTERNATE
# #END_ALTERNATE
# \0xnn (non-printing character support)
#
# Following any entry in the file with the characters "#PRE" will cause
# the entry to be preloaded into the name cache. By default, entries are
# not preloaded, but are parsed only after dynamic name resolution fails.
#
# Following an entry with the "#DOM:<domain>" tag will associate the
# entry with the domain specified by <domain>. This affects how the
# browser and logon services behave in TCP/IP environments. To preload
# the host name associated with #DOM entry, it is necessary to also add a
# #PRE to the line. The <domainis always preloaded although it will not
# be shown when the name cache is viewed.
#
# Specifying "#INCLUDE <filename>" will force the RFC NetBIOS (NBT)
# software to seek the specified <filenameand parse it as if it were
# local. <filenameis generally a UNC-based name, allowing a
# centralized lmhosts file to be maintained on a server.
# It is ALWAYS necessary to provide a mapping for the IP address of the
# server prior to the #INCLUDE. This mapping must use the #PRE directive.
# In addtion the share "public" in the example below must be in the
# LanManServer list of "NullSessionShares" in order for client machines to
# be able to read the lmhosts file successfully. This key is under
#
\machine\system\currentcontrolset\services\lanmanserver\parameters\nullsess
>ionshares # in the registry. Simply add "public" to the list found there.
#
# The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE
# statements to be grouped together. Any single successful include
# will cause the group to succeed.
#
# Finally, non-printing characters can be embedded in mappings by
# first surrounding the NetBIOS name in quotations, then using the
# \0xnn notation to specify a hex value for a non-printing character.
#
# The following example illustrates all of these extensions:
#
# 102.54.94.97 rhino #PRE #DOM:networking #net group's DC
# 102.54.94.102 "appname \0x14" #special app server
# 102.54.94.123 popular #PRE #source server
# 102.54.94.117 localsrv #PRE #needed for the
include #
# #BEGIN_ALTERNATE
# #INCLUDE \\localsrv\public\lmhosts
# #INCLUDE \\rhino\public\lmhosts
# #END_ALTERNATE
#
# In the above example, the "appname" server contains a special
# character in its name, the "popular" and "localsrv" server names are
# preloaded, and the "rhino" server name is specified so it can be used
# to later #INCLUDE a centrally maintained lmhosts file if the "localsrv"
# system is unavailable.
#
# Note that the whole file is parsed including comments on each lookup,
# so keeping the number of comments to a minimum will improve performance.
# Therefore it is not advisable to simply add lmhosts file entries onto the
# end of this file.



This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 19:37:30 EDT