search for: wins2

Here is my scenario when a client wants to resolve a name on my local network: CLIENT --> VPN --> SAMBA --> DNS The client is set up like so: DNS1 = ISP DNS1 (204.26.64.1) DNS2 = ISP DNS2 (204.26.80.3) WINS1 = my samba1 (10.10.1.5) WINS2 = my samba2 (10.10.1.8) This all _seemed_ to have worked 3 days ago for roughly 6 months but stopped suddenly without me doing anything. When the client requests a name on my local network like atlas (10.10.1.8), there is no resolution at all. My first reaction was there was a firewall change or...

...password server = <pdc> <bdc> username map = /usr/local/samba/lib/users.map #loglevel = 2 log file = /var/opt/samba/log/%m name resolve order = host wins bcast time server = Yes deadtime = 10 wins server = <wins1> <wins2> kernel oplocks = No host msdfs = Yes invalid users = smsclitoknacct& smsclisvcacct& create mask = 0644 inherit acls = Yes Samba is compiled with acl support. ACL are used in the ufs filesystem and works. This is slowly driving me insane..... TI...

...slog = 0 max log size = 50000 unix charset = "CP850" logon script = netlogon.bat logon path = \\einstein\profiles\%U logon drive = h: logon home = \\sirius\%U domain logons = Yes os level = 32 preferred master = yes domain master = yes local master = yes wins support = yes wins partners = wins2.brgs.org passdb backend = ldapsam_nua:ldap://ldap1.brgs.org ldap ssl = no ldap admin dn = "cn=root,dc=brgs,dc=org" ldap suffix = dc=brgs,dc=org ldap user suffix = ou=People ldap machine suffix = ou=Machines non unix account range = 8000-8999 ldap trust ids = yes ldap passwd sync = yes uni...

...log.%m max log size = 50000 unix charset = CP850 logon path = \\einstein\profiles\%U logon script = sonstige.bat logon drive = h: logon home = \\sirius\%U domain logons = Yes os level = 32 preferred master = yes domain master = yes local master = yes wins support = yes #wins partners = wins2.brgs.org passdb backend = ldapsam_nua:ldap://ldap1.brgs.org ldap ssl = no ldap admin dn = "cn=root,dc=brgs,dc=org" ldap suffix = dc=brgs,dc=org ldap user suffix = ou=People ldap machine suffix = ou=Machines non unix account range = 8000-8999 ldap trust ids = yes ldap passwd sync...

...= Micro Strategy Dev Samba Server 3.0.21a interfaces = 127.0.0.1, r10dev01/255.255.255.0 security = DOMAIN log file = /opt/samba/logs/log.%m preferred master = No local master = No domain master = No dns proxy = No wins server = WINS1, WINS2 ldap ssl = no passdb expand explicit = No admin users = is81301, ds066 [/dano] path = /tmp guest ok = Yes When I do a netstat -a, I do not see ports 137 or 139 listed: tcp4 0 0 *.daytime *.* LISTEN tcp...

...evel = 3 > log file = /var/log/samba/%m > max log size = 100 > preferred master = No > dns proxy = No > wins server = WINS1 WINS2 > > ; Winbind Settings > winbind cache time = 0 > winbind nested groups = yes > allow trusted domains = No > idmap backend = idmap_rid:DOMAIN=500-100000000 > idmap uid...

I've been using samba for some time and have always had a good experience. I decided to try and configure my home network to let all my computers talk to the samba share. I'm stuck on one part where my OSX client, when creating new files/directories, won't create them writeable by the group. I've tried what seems like every combination of directory mask, force directory