72934
Dec 15, 2008, updated at Dec 16, 2008 (UTC)
4247
5
0
Keine Serverprofile mehr, XP-Client plötzlich Master
Seltsames Verhalten eines XPprof-Clients in einer Windows-Domain mit Samba als PDC.
Hallo,
ich habe in einem heterogenen Netzwerk mit einem Sambaserver (Samba 3.2.5) auf Debian/Linux (Lenny), das Problem, daß sich die WindowsXPProf-Clients von einem Tag auf den anderen nicht am dem Samba-Server, der als PDC konfiguriert ist, anmelden können. Das zeigt sich an den Clients so, daß sie die Serverprofile und das home-Share nicht verbinden können.
Die smb.conf sieht wie folgt aus:
[global]
netbios name = SAMBA
workgroup = GASPERSLOUIS-AG
server string = %h SAMBA (Samba-Server %v)
wins support = yes
dns proxy = no
name resolve order = lmhosts host wins bcast
interfaces = eth0
log file = /var/log/samba/log.%m
max log size = 1000
syslog = 0
panic action = /usr/share/samba/panic-action %d
security = user
encrypt passwords = true
passdb backend = tdbsam:/var/lib/samba/passdb.tdb guest
obey pam restrictions = yes
invalid users = root
unix password sync = no
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n *password\supdated\ssuccessf
ully* .
local master = yes
preferred master = yes
os level = 100
domain master = yes
domain logons = yes
admin users = @samba-admins,root
logon path = \\192.168.123.3\profiles\%U
;logon path = \\192.168.123.20\homes\%U
logon drive = h:
logon home = \\%N\%U
profile acls = yes
logon script = logon.cmd
add user script = /usr/sbin/useradd -m %u
delete user script = /usr/sbin/userdel -r %u
add group script = /usr/sbin/groupadd %g
delete group script = /usr/sbin/groupdel %g
add user to group script = /usr/sbin/usermod -G %g %u
printing = cups
socket options = TCP_NODELAY
[homes]
comment = Benutzer-Verzeichnisse
browseable = no
writable = yes
create mask = 0755
directory mask = 0755
[netlogon]
comment = Network Logon Service
path = /home/samba/netlogon
guest ok = yes
writable = no
share modes = no
[profiles]
comment = Users profiles
path = /home/samba/profiles
guest ok = no
browseable = yes
writable = yes
create mask = 0600
directory mask = 0700
[printers]
comment = All Printers
browseable = no
path = /var/spool/samba
printable = yes
public = no
writable = no
create mode = 0700
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = yes
read only = yes
guest ok = no
[cdrom]
comment = Samba server's CD-ROM
writable = no
locking = no
path = /cdrom
public = yes
[Gemeinsame Dateien]
writeable = yes
comment = Gemeinsame Dateien
create mode = 777
directory mode = 777
force create mode = 660
force directory mode = 660
public = yes
path = /home/Dokumente
[IMV]
readonly = no
comment = IMV-Daten
create mode = 777
directory mode = 777
force create mode = 660
force directory mode = 660
public = yes
path = /home/IMV
[K-TEL]
readonly = no
comment = KlickTel-Daten
create mode = 777
directory mode = 777
force create mode = 660
force directory mode = 660
public = yes
path = /home/KTEL
[Datensicherung]
readonly = yes
comment = Sicherungs-Index
create mode = 777
directory mode = 777
force create mode = 660
force directory mode = 660
public = yes
path = /var/log/archivelog
[makler2000]
readonly = no
comment = Makler2000-Dateien
create mode = 777
directory mode = 777
force create mode = 660
force directory mode = 660
public = yes
path = /home/makler2000
Um kurz zu machen, ich vermute, daß der XPprof-Client "MAKLER07" sich ungerechtfertig zum Master bzw. zum Server gemacht hat. Denn ein
"smbclient -L samba" liefert
Domain=[GASPERSLOUIS-AG] OS=[Unix] Server=[Samba 3.2.5]
Server Comment
--------- -------
MAKLER07
SAMBA samba SAMBA (Samba-Server 3.2.5)
Workgroup Master
--------- -------
GASPERSLOUIS-AG MAKLER07
Was muß ich eventuell am Client oder auch am Server einstellen, daß der Client seinen Master-Status verliert?
Vielen Dank,
Sambafreak
ich habe in einem heterogenen Netzwerk mit einem Sambaserver (Samba 3.2.5) auf Debian/Linux (Lenny), das Problem, daß sich die WindowsXPProf-Clients von einem Tag auf den anderen nicht am dem Samba-Server, der als PDC konfiguriert ist, anmelden können. Das zeigt sich an den Clients so, daß sie die Serverprofile und das home-Share nicht verbinden können.
Die smb.conf sieht wie folgt aus:
[global]
netbios name = SAMBA
workgroup = GASPERSLOUIS-AG
server string = %h SAMBA (Samba-Server %v)
wins support = yes
dns proxy = no
name resolve order = lmhosts host wins bcast
interfaces = eth0
log file = /var/log/samba/log.%m
max log size = 1000
syslog = 0
panic action = /usr/share/samba/panic-action %d
security = user
encrypt passwords = true
passdb backend = tdbsam:/var/lib/samba/passdb.tdb guest
obey pam restrictions = yes
invalid users = root
unix password sync = no
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n *password\supdated\ssuccessf
ully* .
local master = yes
preferred master = yes
os level = 100
domain master = yes
domain logons = yes
admin users = @samba-admins,root
logon path = \\192.168.123.3\profiles\%U
;logon path = \\192.168.123.20\homes\%U
logon drive = h:
logon home = \\%N\%U
profile acls = yes
logon script = logon.cmd
add user script = /usr/sbin/useradd -m %u
delete user script = /usr/sbin/userdel -r %u
add group script = /usr/sbin/groupadd %g
delete group script = /usr/sbin/groupdel %g
add user to group script = /usr/sbin/usermod -G %g %u
printing = cups
socket options = TCP_NODELAY
[homes]
comment = Benutzer-Verzeichnisse
browseable = no
writable = yes
create mask = 0755
directory mask = 0755
[netlogon]
comment = Network Logon Service
path = /home/samba/netlogon
guest ok = yes
writable = no
share modes = no
[profiles]
comment = Users profiles
path = /home/samba/profiles
guest ok = no
browseable = yes
writable = yes
create mask = 0600
directory mask = 0700
[printers]
comment = All Printers
browseable = no
path = /var/spool/samba
printable = yes
public = no
writable = no
create mode = 0700
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = yes
read only = yes
guest ok = no
[cdrom]
comment = Samba server's CD-ROM
writable = no
locking = no
path = /cdrom
public = yes
[Gemeinsame Dateien]
writeable = yes
comment = Gemeinsame Dateien
create mode = 777
directory mode = 777
force create mode = 660
force directory mode = 660
public = yes
path = /home/Dokumente
[IMV]
readonly = no
comment = IMV-Daten
create mode = 777
directory mode = 777
force create mode = 660
force directory mode = 660
public = yes
path = /home/IMV
[K-TEL]
readonly = no
comment = KlickTel-Daten
create mode = 777
directory mode = 777
force create mode = 660
force directory mode = 660
public = yes
path = /home/KTEL
[Datensicherung]
readonly = yes
comment = Sicherungs-Index
create mode = 777
directory mode = 777
force create mode = 660
force directory mode = 660
public = yes
path = /var/log/archivelog
[makler2000]
readonly = no
comment = Makler2000-Dateien
create mode = 777
directory mode = 777
force create mode = 660
force directory mode = 660
public = yes
path = /home/makler2000
Um kurz zu machen, ich vermute, daß der XPprof-Client "MAKLER07" sich ungerechtfertig zum Master bzw. zum Server gemacht hat. Denn ein
"smbclient -L samba" liefert
Domain=[GASPERSLOUIS-AG] OS=[Unix] Server=[Samba 3.2.5]
Server Comment
--------- -------
MAKLER07
SAMBA samba SAMBA (Samba-Server 3.2.5)
Workgroup Master
--------- -------
GASPERSLOUIS-AG MAKLER07
Was muß ich eventuell am Client oder auch am Server einstellen, daß der Client seinen Master-Status verliert?
Vielen Dank,
Sambafreak
Please also mark the comments that contributed to the solution of the article
Content-Key: 104076
Url: https://administrator.de/contentid/104076
Printed on: May 6, 2024 at 02:05 o'clock
5 Comments
Latest comment
Steht denn in der Samba-Log mehr ?
Ja, und ein Logon-Script wird auch nicht geladen ?
Wenn doch ,hast du das mal geprüft ?
Und mal ipconfig /all und die lmhost und host gecheckt ?
Fungiert der Server auch als DHCPD ?
Wenn doch ,hast du das mal geprüft ?
Und mal ipconfig /all und die lmhost und host gecheckt ?
Fungiert der Server auch als DHCPD ?
Aber an die Shares kommst du, wenn du dich lokal am Client anmeldest ?