Top-Themen

AppleEntwicklungHardwareInternetLinuxMicrosoftMultimediaNetzwerkeOff TopicSicherheitSonstige SystemeVirtualisierungWeiterbildungZusammenarbeit

Aktuelle Themen

Administrator.de FeedbackApache ServerAppleAssemblerAudioAusbildungAuslandBackupBasicBatch & ShellBenchmarksBibliotheken & ToolkitsBlogsCloud-DiensteClusterCMSCPU, RAM, MainboardsCSSC und C++DatenbankenDatenschutzDebianDigitiales FernsehenDNSDrucker und ScannerDSL, VDSLE-BooksE-BusinessE-MailEntwicklungErkennung und -AbwehrExchange ServerFestplatten, SSD, RaidFirewallFlatratesGoogle AndroidGrafikGrafikkarten & MonitoreGroupwareHardwareHosting & HousingHTMLHumor (lol)Hyper-VIconsIDE & EditorenInformationsdiensteInstallationInstant MessagingInternetInternet DomäneniOSISDN & AnaloganschlüsseiTunesJavaJavaScriptKiXtartKVMLAN, WAN, WirelessLinuxLinux DesktopLinux NetzwerkLinux ToolsLinux UserverwaltungLizenzierungMac OS XMicrosoftMicrosoft OfficeMikroTik RouterOSMonitoringMultimediaMultimedia & ZubehörNetzwerkeNetzwerkgrundlagenNetzwerkmanagementNetzwerkprotokolleNotebook & ZubehörNovell NetwareOff TopicOpenOffice, LibreOfficeOutlook & MailPapierkorbPascal und DelphiPeripheriegerätePerlPHPPythonRechtliche FragenRedHat, CentOS, FedoraRouter & RoutingSambaSAN, NAS, DASSchriftartenSchulung & TrainingSEOServerServer-HardwareSicherheitSicherheits-ToolsSicherheitsgrundlagenSolarisSonstige SystemeSoziale NetzwerkeSpeicherkartenStudentenjobs & PraktikumSuche ProjektpartnerSuseSwitche und HubsTipps & TricksTK-Netze & GeräteUbuntuUMTS, EDGE & GPRSUtilitiesVB for ApplicationsVerschlüsselung & ZertifikateVideo & StreamingViren und TrojanerVirtualisierungVisual StudioVmwareVoice over IPWebbrowserWebentwicklungWeiterbildungWindows 7Windows 8Windows 10Windows InstallationWindows MobileWindows NetzwerkWindows ServerWindows SystemdateienWindows ToolsWindows UpdateWindows UserverwaltungWindows VistaWindows XPXenserverXMLZusammenarbeit

Samba 3.5.6 PDC und Win7 wollen einfach nicht!

Frage Linux Samba

Mitglied: icewave

icewave (Level 1) - Jetzt verbinden

06.02.2012, aktualisiert 11:54 Uhr, 3451 Aufrufe, 3 Kommentare

Trotz sämtlicher Anleitungen und Tips will Win7 einfach nicht mit dem Samba verbinden.

Heyhu

Ich hab da ein Problem, was ich einfach nicht gelöst bekomme...

Ich habe einen Debian-Sqeeze-Server, auf welchem ich verschiedene Dienste am laufen habe. Darunter auch Samba und BIND9.

Nun habe ich schon länger Dateifreigaben über den Samba erledigt, was auch wunderbar funktionierte, doch trotz aller mühen mag der Win7 Client einfach nicht verbinden.
Es kommt immer die Fehlermeldung "Die angegebene Domäne ist nicht vorhanden, oder es konnte keine Verbindung hergestllt werden."

Hier einmal meine smb.conf
01.
#======================= Global Settings ======================= 
02.
 
03.
[global] 
04.
 
05.
## Browsing/Identification ### 
06.
 
07.
# Change this to the workgroup/NT-domain name your Samba server will part of 
08.
   workgroup = LXPDC 
09.
 
10.
# server string is the equivalent of the NT Description field 
11.
   server string = Samba (%h) 
12.
 
13.
# Windows Internet Name Serving Support Section: 
14.
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server 
15.
   wins support = no 
16.
 
17.
# WINS Server - Tells the NMBD components of Samba to be a WINS Client 
18.
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both 
19.
;   wins server = w.x.y.z 
20.
 
21.
# This will prevent nmbd to search for NetBIOS names through DNS. 
22.
   dns proxy = no 
23.
 
24.
# What naming service and in what order should we use to resolve host names 
25.
# to IP addresses 
26.
;   name resolve order = lmhosts host wins bcast 
27.
 
28.
#### Networking #### 
29.
 
30.
# The specific set of interfaces / networks to bind to 
31.
# This can be either the interface name or an IP address/netmask; 
32.
# interface names are normally preferred 
33.
   interfaces = 127.0.0.0/8 eth1 
34.
 
35.
# Only bind to the named interfaces and/or networks; you must use the 
36.
# 'interfaces' option above to use this. 
37.
# It is recommended that you enable this feature if your Samba machine is 
38.
# not protected by a firewall or is a firewall itself.  However, this 
39.
# option cannot handle dynamic or non-broadcast interfaces correctly. 
40.
   bind interfaces only = yes 
41.
 
42.
 
43.
 
44.
#### Debugging/Accounting #### 
45.
 
46.
# This tells Samba to use a separate log file for each machine 
47.
# that connects 
48.
   log file = /var/log/samba/%m.log 
49.
   log level = 20 
50.
 
51.
# Cap the size of the individual log files (in KiB). 
52.
   max log size = 1000 
53.
 
54.
# If you want Samba to only log through syslog then set the following 
55.
# parameter to 'yes'. 
56.
   syslog only = no 
57.
 
58.
# We want Samba to log a minimum amount of information to syslog. Everything 
59.
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log 
60.
# through syslog you should set the following parameter to something higher. 
61.
   syslog = 0 
62.
 
63.
# Do something sensible when Samba crashes: mail the admin a backtrace 
64.
   panic action = /usr/share/samba/panic-action %d 
65.
 
66.
 
67.
####### Authentication ####### 
68.
 
69.
# "security = user" is always a good idea. This will require a Unix account 
70.
# in this server for every user accessing the server. See 
71.
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html 
72.
# in the samba-doc package for details. 
73.
   security = user 
74.
 
75.
# You may wish to use password encryption.  See the section on 
76.
# 'encrypt passwords' in the smb.conf(5) manpage before enabling. 
77.
   encrypt passwords = true 
78.
 
79.
# If you are using encrypted passwords, Samba will need to know what 
80.
# password database type you are using.   
81.
   passdb backend = tdbsam 
82.
 
83.
   obey pam restrictions = yes 
84.
 
85.
# This boolean parameter controls whether Samba attempts to sync the Unix 
86.
# password with the SMB password when the encrypted SMB password in the 
87.
# passdb is changed. 
88.
   unix password sync = yes 
89.
 
90.
# For Unix password sync to work on a Debian GNU/Linux system, the following 
91.
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for 
92.
# sending the correct chat script for the passwd program in Debian Sarge). 
93.
   passwd program = /usr/bin/passwd %u 
94.
   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . 
95.
 
96.
# This boolean controls whether PAM will be used for password changes 
97.
# when requested by an SMB client instead of the program listed in 
98.
# 'passwd program'. The default is 'no'. 
99.
   pam password change = yes 
100.
 
101.
########## Domains ########### 
102.
 
103.
# Is this machine able to authenticate users. Both PDC and BDC 
104.
# must have this setting enabled. If you are the BDC you must 
105.
# change the 'domain master' setting to no 
106.
107.
   domain logons = yes 
108.
109.
# The following setting only takes effect if 'domain logons' is set 
110.
# It specifies the location of the user's profile directory 
111.
# from the client point of view) 
112.
# The following required a [profiles] share to be setup on the 
113.
# samba server (see below) 
114.
;   logon path = \\%N\profiles\%U 
115.
# Another common choice is storing the profile in the user's home directory 
116.
# (this is Samba's default) 
117.
   logon path = \\shares.intern\%U\profile 
118.
 
119.
# The following setting only takes effect if 'domain logons' is set 
120.
# It specifies the location of a user's home directory (from the client 
121.
# point of view) 
122.
   logon drive = H: 
123.
   logon home = \\shares.intern\%U 
124.
 
125.
# The following setting only takes effect if 'domain logons' is set 
126.
# It specifies the script to run during logon. The script must be stored 
127.
# in the [netlogon] share 
128.
# NOTE: Must be store in 'DOS' file format convention 
129.
;   logon script = logon.cmd 
130.
 
131.
# This allows Unix users to be created on the domain controller via the SAMR 
132.
# RPC pipe.  The example command creates a user account with a disabled Unix 
133.
# password; please adapt to your needs 
134.
 add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u 
135.
 
136.
# This allows machine accounts to be created on the domain controller via the  
137.
# SAMR RPC pipe.   
138.
# The following assumes a "machines" group exists on the system 
139.
 add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u 
140.
 
141.
# This allows Unix groups to be created on the domain controller via the SAMR 
142.
# RPC pipe.   
143.
 add group script = /usr/sbin/addgroup --force-badname %g 
144.
 
145.
########## Printing ########## 
146.
 
147.
# If you want to automatically load your printer list rather 
148.
# than setting them up individually then you'll need this 
149.
#   load printers = yes 
150.
 
151.
# lpr(ng) printing. You may wish to override the location of the 
152.
# printcap file 
153.
;   printing = bsd 
154.
;   printcap name = /etc/printcap 
155.
 
156.
# CUPS printing.  See also the cupsaddsmb(8) manpage in the 
157.
# cupsys-client package. 
158.
;   printing = cups 
159.
;   printcap name = cups 
160.
 
161.
############ Misc ############ 
162.
 
163.
# Using the following line enables you to customise your configuration 
164.
# on a per machine basis. The %m gets replaced with the netbios name 
165.
# of the machine that is connecting 
166.
;   include = /home/samba/etc/smb.conf.%m 
167.
 
168.
# Most people will find that this option gives better performance. 
169.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html 
170.
# for details 
171.
# You may want to add the following on a Linux system: 
172.
   SO_RCVBUF=8192 SO_SNDBUF=8192 
173.
   socket options = TCP_NODELAY 
174.
 
175.
# The following parameter is useful only if you have the linpopup package 
176.
# installed. The samba maintainer and the linpopup maintainer are 
177.
# working to ease installation and configuration of linpopup and samba. 
178.
;   message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' & 
179.
 
180.
# Domain Master specifies Samba to be the Domain Master Browser. If this 
181.
# machine will be configured as a BDC (a secondary logon server), you 
182.
# must set this to 'no'; otherwise, the default behavior is recommended. 
183.
   domain master = auto 
184.
 
185.
# Some defaults for winbind (make sure you're not using the ranges 
186.
# for something else.) 
187.
   idmap uid = 10000-20000 
188.
   idmap gid = 10000-20000 
189.
   template shell = /bin/bash 
190.
 
191.
# The following was the default behaviour in sarge, 
192.
# but samba upstream reverted the default because it might induce 
193.
# performance issues in large organizations. 
194.
# See Debian bug #368251 for some of the consequences of *not* 
195.
# having this setting and smb.conf(5) for details. 
196.
;   winbind enum groups = yes 
197.
;   winbind enum users = yes 
198.
 
199.
# Setup usershare options to enable non-root users to share folders 
200.
# with the net usershare command. 
201.
 
202.
# Maximum number of usershare. 0 (default) means that usershare is disabled. 
203.
   usershare max shares = 100 
204.
 
205.
#======================= Share Definitions ======================= 
206.
 
207.
[homes] 
208.
	browseable = no 
209.
	comment = Home Directories 
210.
	valid users = @users 
211.
	writeable = yes 
212.
	create mode = 0777 
213.
	directory mode = 0777 
214.
	 
215.
[netlogon] 
216.
	browseable = no 
217.
	comment = Netlogon-Scripts 
218.
	writeable = no 
219.
 
220.
#weitere Shares für Dateifreigaben
Ich habe ebenfalls im Win7 Client die Registry-Einträge und Sicherheitsrichtlinien wie in den Tutorials angegeben geändert.

Trotzdem bringt das nichts - ioch finde weder eine Fehlermeldung bei Samba, bei Win7 weiß ich nicht wo ich so etwas finden könnte.


Hatte vielleicht jemand schon einmal dieses Problem oder kann mir helfen?



Liebe Grüße,

icewave
Mitglied: Wombie
24.06.2012 um 17:36 Uhr
Hi!

Ich stehe aktuell vor dem gleichen Problem.
Konntest du denn mittlerweile eine Lösung dafür finden?

Danke!
Bitte warten ..
Mitglied: holli.zimmi
26.05.2015 um 13:58 Uhr
Hi,

hast Du User angelegt in Linux?

Gruss

Holli
Bitte warten ..
Mitglied: icewave
26.05.2015 um 14:54 Uhr
Hey,

Ich hab den PDC leider nicht mehr im Betrieb und kann deshalb leider nichts dazu sagen.

Liebe Grüße,

icewave
Bitte warten ..
Neuester Wissensbeitrag
Microsoft

Lizenzwiederverkauf und seine Tücken

(5)

Erfahrungsbericht von DerWoWusste zum Thema Microsoft ...

Ähnliche Inhalte
Heiß diskutierte Inhalte
Windows Netzwerk
Windows 10 RDP geht nicht (16)

Frage von Fiasko zum Thema Windows Netzwerk ...

Windows Server
Outlook Verbindungsversuch mit Exchange (15)

Frage von xbast1x zum Thema Windows Server ...

Microsoft Office
Keine Updates für Office 2016 (13)

Frage von Motte990 zum Thema Microsoft Office ...