wiki.smarken.dk

Nu har du sat Samba op på Linux-serveren samt besluttet dig for, om du vil benytte krypterede adgangskoder eller ej, så det eneste du mangler, er at få Windows-klienterne til at tilslutte sig domænet. I det følgende afsnit vil vi anvise en løsning på dette. Der knytter sig følgende forudsætninger til det efterfølgende eksempel:

Maskiner i vores netværk:

• test.domain.net; Linux-serveren
• router.domain.net; Router til internettet
• WS1.domain.net; Windows-klient

Indhold af filen/etc/hosts:

127.0.0.1 localhost.localdomain   localhost
192.168.1.1     test.domain.net         test
172.10.10.1     router.domain.net       router

Indhold af filen/etc/smb.conf:

[global]
   workgroup = testdomain

   printing = bsd
   printcap name = /etc/printcap
   load printers = yes

   log file = /var/log/samba-log.%m

   short preserve case = yes
   preserve case = yes

   lock directory = /var/lock/samba
   locking = yes
   strict locking = yes

   security = user

   socket options = TCP_NODELAY

   domain master = yes
   domain logons = yes

[homes]
   comment = Home Directories
   read only = no
   create mode = 0750

[deskjet870cxi]
   comment = All Printers
   path = /var/spool/samba
   browseable = yes
   printable = yes
; Set public = yes to allow user 'guest account' to print
   public = no
   writable = no
   create mode = 0700

For at kunne få forbindelse til Samba-serveren, kræves der en fungerende løsning på navneopslag. Det kan løses på 2 måder:

• Hosts og Lmhosts – netbios-way (har i øvrigt suffixet .sam): I disse filer skal samba-serveren være nævnt. Når du har foretaget ændringerne i filerne, skal deres navne ændres til Hosts og Lmhosts – efternavnene.samskal altså udelades. Se eksempel på disse filer senere.
• Sæt Linux-serveren til at køre named – TCP/IP-way, og fortæl Windows at den skal bruge Linux-serveren som navneserver (DNS). Åbn indstillinger→kontrolpanel→netværk. Åbn egenskaber for TCP/IP. Under fanebladet “Gateway” tilføjes 192.168.1.1. Under fanebladet “DNS-opsætning” aktiveres DNS, i “Vært” skrives maskinens navn WS1 (det skal være det samme navn som blev angivet som “Computernavn” i fanebladet “identifikation”: Indstillinger→kontrolpanel→netværk). “Domæne” sættes til testdomain. Feltet “Rækkefølge” til søgning efter navneserver tilføjes 192.168.1.1 (hvis den står som den første, går det hurtigere).

DOMÆNENAVN: Workgroup/domain-navn må ikke være sammenfaldende med host-navnet. Hvis samba, som i vores eksempel, kører på hosten test.domain.net, og har følgende stående i filen:/etc/hosts:

127.0.0.1 localhost.localdomain localhost
192.168.1.1 test.domain.net test
172.10.10.1 router.domain.net router

er følgende navne ikke tilladte for workgroup/domain:

• localhost.localdomain
• test.domain.net
• router.domain.net

Disse vil formentlig være ulovlige i sig selv, da de indeholder et forbudt tegn.

• localhost
• test
• router

I dette afsnit kommer så vores eksempel på, hvordan filerneHostsogLmhostsskal se ud.

For Windows 95/98 gemmes filen somc:\windows\Hosts.

For Windows NT gemmes filen somc:\winnt\system32\drivers\etc\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
192.168.1.1 test
172.10.10.1 router

For Windows 95/98 gemmes filen somc:\windows\Lmhosts.

For Windows NT gemmes filen somc:\winnt\system32\drivers\etc\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\nullsessionshares
# 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 theinclude
#
# #BEGIN_ALTERNATE
# #INCLUDE \\localsrv\public\lmhosts <file://\\localsrv\public\lmhosts>
# #INCLUDE \\rhino\public\lmhosts <file://\\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.

192.168.1.1 test #PRE #DOM:testdomain #net group's DC