search for: mywg

...erver where this does not happen. What causes this? Here's the smb.conf from the "bad" server. It's pretty much the same as the "good" server. #======================= Global Settings===================================== [global] unix charset = LOCALE workgroup = MYWG netbios name = APP2 realm = MYWG.MD server string = Linux Server security = ADS allow trusted domains = No username map = /etc/samba/smbusers log level = 2 syslog = 0 log file = /var/log/samba/%m.log max log size = 50 printcap name = /etc/printcap ldap ssl = no...

...*always* happen. Also, I have another samba 3.0.28-0.el4.9 server where this does not happen at all. What the heck causes this? Here's the smb.conf from the "bad" server. It's pretty much the same as the "good" server. [global] unix charset = LOCALE workgroup = MYWG netbios name = APP2 realm = MYWG.MD server string = Linux Server security = ADS allow trusted domains = No username map = /etc/samba/smbusers log level = 2 syslog = 0 log file = /var/log/samba/%m.log max log size = 50 printcap name = /etc/printcap ldap ssl = no...

...t does not always happen. Also, I have another samba 3.0.28-0.el4.9 server where this does not happen at all. What causes this? Here's the smb.conf from the "bad" server. It's pretty much the same as the "good" server. [global] unix charset = LOCALE workgroup = MYWG netbios name = APP2 realm = MYWG.MD server string = Linux Server security = ADS allow trusted domains = No username map = /etc/samba/smbusers log level = 2 syslog = 0 log file = /var/log/samba/%m.log max log size = 50 printcap name = /etc/printcap ldap ssl = no...

....domain/share_name Her Domain password is correct and working. We tested it out on a PC. Samba server details: client is on different subnet from samba server no evidence on samba logs of connection attempt by client # smbd -V Version 3.0.24-SerNet-RedHat smb.conf: [global] workgroup = MYWG realm = MY.DOMAIN netbios aliases = SERVER server string = SPH IIS File Server interfaces = eth2:1, lo, 127.0.0.1 bind interfaces only = Yes security = ADS password server = x.x.x.x log level = 0 passdb:3 auth:3 syslog = 0...

...10/18 13:42:32.424051, 0] ../source3/lib/util.c:822(smb_panic_s3) Oct 18 13:42:32 pdc smbd[27384]: smb_panic(): calling panic action [/bin/sleep 999999999] Restarting the samba daemon solves the problem and then it happens again randomly. Following is my smb.conf: [global] workgroup = MYWG realm = mywg.my.realm netbios name = PDC server role = active directory domain controller dns forwarder = 10.0.0.1 [netlogon] path = /usr/local/samba/var/locks/sysvol/mywg.my.realm/scripts read only = No [sysvol] path = /usr/local/samba/var/...

...4 and ... idem. This is not my first install, on my other servers they're only 2 nmbd. With this install, after one day, I have more than 250 daemons, it is the hell ! What que c'est que ?a ? Do you know this problem ? Merci, Bruno Here is my conf : [global] workgroup = MYWG server string = xxxxxx map to guest = Bad User passdb backend = ldapsam:ldap://myserver.ges-sa.fr username map = /etc/samba/smbusers log level = 10 log file = /var/log/samba/%m.log max log size = 50 socket options = TCP_NODELAY...

Hello, I have tried to find that info, but couldn't yet find it in TOSHARG or "Samba-3 By Example" : A client has one NT-PDC running without WINS-service and a Samba-Domain-Member-Server that is currently the WINS-Server. I have > [global] > workgroup = MYWG > netbios name = MAIL > interfaces = eth* lo > map to guest = Bad User > security = domain > password server = NTSERVER > encrypt passwords = yes > passdb backend = tdbsam > server string = Samba > add machine script = /usr/sbin/useradd -c Mach...

...all the domain groups. I am also able to view all the users using the -u switch. We are running Windows Server 2003 R2, I would post log files but I am not exactly sure where or what to look for. Here is the copy of the article as promised: /Listing One: smb.conf options for Winbind workgroup= MYWG security= Domain encrypt passwords= Yes password server= 192.168.1.1 winbind use default domain= Yes idmap uid= 2000-25000 idmap gid= 2000-25000 template shell= /bin/bash template homedir= /home/% U The first four lines in Listing One are fairly straightforward, and might appear on any Sa...

...ble to view all the users using > the -u switch. We are running Windows Server 2003 R2, I would post > log files but I am not exactly sure where or what to look for. > Here is the copy of the article as promised: > > /Listing One: smb.conf options for Winbind > > workgroup= MYWG > > security= Domain > > encrypt passwords= Yes > > password server= 192.168.1.1 > > winbind use default domain= Yes > > idmap uid= 2000-25000 > > idmap gid= 2000-25000 > > template shell= /bin/bash > > template homedir= /home/% U > > The first...

...> > the -u switch. We are running Windows Server 2003 R2, I would post > > log files but I am not exactly sure where or what to look for. > > Here is the copy of the article as promised: > > > > /Listing One: smb.conf options for Winbind > > > > workgroup= MYWG > > > > security= Domain > > > > encrypt passwords= Yes > > > > password server= 192.168.1.1 > > > > winbind use default domain= Yes > > > > idmap uid= 2000-25000 > > > > idmap gid= 2000-25000 > > > > template shell...