[aclug-L] Re: Whining and bickering--and assistance to newbies

[John Alexander <johnalexander@xxxxxxxxxxx>]

Actually, the lm on lmhosts is shorthand for lan manager. It is capable of
holding some configuration tags that are not typically used on bsd style
networking systems, such as:

#pre            pre-loads the entry into the arp cache
#domain         name of the authenticating NT or Lan Manager domain
#wins           entry for Windows Internet Name Server

I think it's interesting that they use the #, which is typically reserved for
comments in the hosts file, so you could probably take the lmhosts file that
you have developed, and use it on the BSD boxes with minimal editing.

ja

On Sun, 16 Apr 2000, you
wrote: > On Sun, 16 Apr 2000, you wrote: > > Michael Holmes wrote: > >>I still
have to > > > figure out how to put a linux workstation on a NT network! > > 
> > About the only thing I did was to put all of the local machines IP addresses
> > and names into the hosts files. For Linux this is /etc/hosts. For Windows 
> > NT,
> > look for hosts or hosts.sam somewhere under C:\winnt. hosts.sam is a sample
> > of what a hosts file might look like. This should be enough to let you ping
> > both ways, and to run ftp/telnet on NT and connect to the Linux box. (You 
> > may
> > also have to work with /etc/hosts.allow and /etc/hosts.deny, depending on 
> > how
> > security is set up on the Linux box.)
> 
> On the NT side, it's: bootdrive:\winnt\system32\drivers\etc\hosts  and/or
> lmhosts. I'm still not clear when lmhosts gets used. I think it has something
> to do with whether you're using standard network utilities, or using the
> networking calls in the RTL. I always set them the same and it seemed to take
> care of any issues. Of course, on most networks, you can use DNS take care of
> name resolution and forget the files.
> 
> Now, if you're plugging your Linux machine into an established NT network, you
> probably won't find anything in the files to help you set up your Linux hosts
> file. I've never tried to set one up on a larger network that didn't have a 
> DNS
> server.
> 
> > Of course, there's much more that _could_ be done, but that's as far as I've
> > pushed it. I don't use NT, and my NT user is happy just having telnet/ftp.
> 
> For a start, you'd probably want to use Samba to let you mount the NT shared
> directories. Beyond that, I guess it'd depend on what you wanted to do.
> 
> Greg
> 
> -- This is the discussion@xxxxxxxxx list.  To unsubscribe,
> visit http://tmp2.complete.org/cgi-bin/listargate-aclug.cgi

-- This is the discussion@xxxxxxxxx list.  To unsubscribe,
visit http://tmp2.complete.org/cgi-bin/listargate-aclug.cgi