R: R: [Pluto-help] (R)e: Rete casalinga multiOS - LINUX STUFF

[Leonardo Boselli]

Segui le istruzioni, ossia cnacelli tutti i commenti e metti nomi e 
numeri giusti, delle macchine della tua rete, su ambedue i file .
quyello che chi hai mandato è lmhosts.sam , che contiene gli 
esempi, quello che devi avere è lmhosts , senza estensione.
con win me e win 2000 dovrebbe bastare anche hosts e basta, ma 
a mettere troppi di file non fai altro che accelerare la risoluzione.

On 4 Jan 2003, at 20:57, Bonzo wrote:

> Leonardo Boselli wrote:
> 
> >On 4 Jan 2003, at 17:28, Luciano Lucini wrote:
> >  
> >
> >>3)Condivizione file estampanti pre reti micr**** Cliccando poi
> >>sull'icona di rete dovresti vedre i pc presenti in rete.(potrebbe
> >>essere necessario a volte usare il comando trova computer(digitando
> >>l'ip di quello che cerchi o con il nome se specificato nel file
> >>"c:\windows\hosts"(senza estensione editato con EDIT in finestra
> >>dos)
> >>    
> >>
> questo è il mio file \hosts:
> 
> # Copyright (c) 1998 Microsoft Corp.
> #
> # This is a sample HOSTS file used by Microsoft TCP/IP stack for
> # Windows98
> #
> # This file contains the mappings of IP addresses to host names. Each
> # entry should be kept on an individual line. The IP address should be
> # placed in the first column followed by the corresponding host name.
> # The IP address and the host name should be separated by at least one
> # space.
> #
> # Additionally, comments (such as these) may be inserted on individual
> # lines or following the machine name denoted by a '#' symbol.
> #
> # For example:
> #
> #      102.54.94.97     rhino.acme.com          # source server
> #       38.25.63.10     x.acme.com              # x client host
> 
> 127.0.0.1       localhost
> 
> >lmhosts
> >
> e questo è \lmhosts:
> 
> # 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 <domain> is 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 <filename> and parse it as if it were
> # local. <filename> is 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\nul
> lsessionshares # 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.
> 
> vi dicono qualcosa?
> che ci faccio?
> come vi ho precedentemente scritto l'IP del mio PC (presunto server?)
> è 1.255.103.193 mentre quello del portatile è 1.255.103.194
> 
> a presto
> Lorenzo
> 
> 
> -- 
> Tou wa ichiji no haji,          Chiedere è la vergogna di un momento,
> towanu wa matsudae no haji.     non chiedere è la vergogna di tutta la
> vita. 
> 
> 
> 
> 
> _______________________________________________
> pluto-help mailing list
> pluto-help a lists.pluto.linux.it
> http://lists.pluto.linux.it/mailman/listinfo/pluto-help


--
Leonardo Boselli
Nucleo Informatico e Telematico del Dipartimento Ingegneria Civile
Universita` di Firenze , V. S. Marta 3 - I-50139 Firenze
tel +39 0554796431 cell +39 3488605348 fax +39 055495333
http://www.dicea.unifi.it/~leo