search for: wins1

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...

...wd length = 6 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 i...

...seen this before??? ( I can send to sample exe-file again if needed ). Our smb.conf file is as follows : workgroup = cos os level = 0 preferred master = no remote announce = cos server string = hpomega browse list = no domain master = no wins support = no wins server = wins1 guest account = ntguest security = server password server = ntfile4,ntprint1 preserve case = yes short preserve case = no guest ok = no read only = no create mask = 640 directory mask = 750 debug level = 1 socket options = TCP_NODELAY [homes] Eddy Reniers --...

...onfig issue or if it's the PDC. (win2k sp2, installed sp2 to see if it resolved the issue, but it didn't) Can anyone help or point me in the right direction. TIA Steve smb.conf : - # Global parameters [global] workgroup = TELETEQ.MINE.NU netbios name = AZTEQ-FS-WINS1 server string = Samba Server encrypt passwords = Yes obey pam restrictions = Yes pam password change = Yes passwd program = /usr/bin/passwd %u passwd chat = *New*password* %n\n *Retype*new*password* %n\n *passwd:*all*authentication*tokens*update...

...le. With log level 2 the PDC doesn't show any unusual messages. Again, I'll post a much bigger debug log if it can help. smb.conf of member server: [global] security = domain password server = 172.16.0.1 workgroup = BRGS server string = Gateway (samba %v) wins server = wins1 log level = 2 encrypt passwords = yes os level = 2 smb.conf of PDC: [global] workgroup = BRGS netbios name = ALDEBARAN server string = PDC (samba %v) encrypt passwords = Yes security = user log level = 5 log file = /var/log/samba/log.%m max log size = 50000 unix charset = CP85...

...string = 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...

...log level = 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