Re: [Samba] Fix the Issue Windows 8 cannot join if a example.com domain
Hi Daniel, Try modifying the Network Security: LAN Manager authorization Level. Run SecPol.msc SelectLocal PoliciesSecurity OptionsNetwork Security: LAN Manager authorization Level Double click and change to Send LM NTLM - use NTLMv2 session security if option in the combo box. I hope this could help. Sincerely, Carlos R. P. Evertsz Santo Domingo, Dominican Republic Correr el SecPol.msc y selecionar Local PoliciesSecurity OptionsNetwork Security: LAN Manager authorization Level Aqui seleccionar el Send LM NTLM - use NTLMv2 session security renegotiated On Jun/20/2013 2:25 AM, Daniel Müller wrote: Dear all, could anyone approve if the issue windows 8 could not join a samba3 old style dot domain, ex.: 'example.com' would not join-- but 'example' join well!, is solved in any hack? Greetings Daniel --- EDV Daniel Müller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 Tübingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: muel...@tropenklinik.de Internet: www.tropenklinik.de --- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Fix the Issue Windows 8 cannot join if a example.com domain
Ok Thank you Christophe On Jun/20/2013 2:38 PM, Christophe Dezé wrote: hi read this https://www.multifake.net/2013/01/windows-8-not-joining-certain-samba-domains/ Le 20/06/2013 16:25, Carlos R. Pena Evertsz a écrit : Hi Daniel, Try modifying the Network Security: LAN Manager authorization Level. Run SecPol.msc SelectLocal PoliciesSecurity OptionsNetwork Security: LAN Manager authorization Level Double click and change to Send LM NTLM - use NTLMv2 session security if option in the combo box. I hope this could help. Sincerely, Carlos R. P. Evertsz Santo Domingo, Dominican Republic Correr el SecPol.msc y selecionar Local PoliciesSecurity OptionsNetwork Security: LAN Manager authorization Level Aqui seleccionar el Send LM NTLM - use NTLMv2 session security renegotiated On Jun/20/2013 2:25 AM, Daniel Müller wrote: Dear all, could anyone approve if the issue windows 8 could not join a samba3 old style dot domain, ex.: 'example.com' would not join-- but 'example' join well!, is solved in any hack? Greetings Daniel --- EDV Daniel Müller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 Tübingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: muel...@tropenklinik.de Internet: www.tropenklinik.de --- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba3 joining W2k3 as member server
Hi Pieter,
I need to do the same, join a Ubuntu 12.04 samba server to an existing
Win2k3.
Could you post an example of the shares configuration (users and group
read and write permitions) to be used in your example of a samba server
as a domain member?
Thanks.
Carlos Pena
Santo Domingo, Dominican Republic
On 12/21/2012 5:36 PM, Pieter De Wit wrote:
On 18/12/2012 10:47, Andrew Bartlett wrote:
On Mon, 2012-12-17 at 17:00 +1300, Pieter De Wit wrote:
Hi list,
I have tried with all my might to get a samba3 server (Ubuntu
12.04.1 LTS) to join a Windows 2003 domain as a member server,
without any luck. I have used,from memory, the official way of doing
this (aka, from the samba.org website). No matter what settings I
use in smb.conf, the server always joins as a domain controller.
This doesn't seem to break the domain how ever. All I am after is
that my users do not need to enter a username/password for access
from a domain PC to shares on my Linux box.
Any pointers please or is this intended as the server does single sign?
If you can list exactly the steps you took, we might be able to help.
But to answer your question: Yes, Samba will happily join Windows 2003
as a domain member. The key command is 'net ads join'.
Andrew Bartlett
Hi Andrew,
Sorry for the delay in my reply, things has been hectic closing down
for the holidays. In a nut shell, there is what I do/did:
1) apt-get install samba winbindd krb5-user
2) Configure smb.conf as per :
[global]
workgroup = WORK
realm = WORK.LOCAL
preferred master = no
server string = Linux Test Machine
security = ADS
encrypt passwords = yes
log level = 3
log file = /var/log/samba/%m
max log size = 50
printcap name = cups
printing = cups
# winbind enum users = Yes
# winbind enum groups = Yes
# winbind use default domain = Yes
winbind nested groups = Yes
winbind separator = +
idmap uid = 2000-2
idmap gid = 2000-2
template shell = /bin/bash
veto files = lost+found
3) Configure krb5.conf:
[libdefaults]
default_realm = WORK.LOCAL
[realms]
YPG.LOCAL={
kdc=DC.WORK.LOCAL
}
[domain_realm]
.kerberos.server=WORK.LOCAL
4) Restart Samba/Winbind
5) In /etc/nsswitch.conf add winbind to passwd and group
5) Join the domain : net ads join -U my_admin_account
6) kinit my_admin_account
From then, users can connect to the shares on the server using Single
Sign On. The issue is that if I look under my Active Directory, the
server will state that it is a Domain Controller. Running the usual
DC Info tools they seem to think the domain is ok. I would prefer to
have the server say Member server, rather than DC :)
I would like to send you a screenshot of what Active Directory Users
and Computers shows but this will be hard to do remotely.
Thanks,
Pieter
P.S. Good work on the AD integration btw, I am using the above for
Squid aswell and it's pretty neat ! :)
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] access my created share in smb.conf Only by Ip
Hi Mohammad, I had the same problem like many others, so I think samba should include a note like mine in their documentation. This is the trick for successfully access the share with the hostname.. Be sure you have the following lines in the smb.conf: netbios name = yourhostname wins support = yes Find the name resolve order directive and be sure you have it in the following order. name resolve order = wins lmhosts hosts bcast Add the following line: hosts allow = the host ip / mask Where the host ip is your server ip. the mask is the mask you are using in all your windows clients. This is the most important thing. For example If you have in your server the mask 255.255.0.0 then all your clients must have the same network mask. Windows clients with the same mask of the server will see the server on the network with it hostname otherwise you need to access the server by its ip number. I think this is a Windows issue but they have left it in this way so we have to live with it. I hope this can help you. Carlos Santo Domingo, Dominican Republic On 10/17/2012 6:55 AM, Mohammad Ebrahim Abravi wrote: Hello samba4 rc3 *s4-ad - samba server Host name test.s4.com - domain name* *Dns Server - Samba Internal DNS server , Bind 9.9.1-P2* *win xp* have access to default share such as sysvol by dns name (\\test.s4.com \sysvol) but if created a share in smb.conf Only access by IP such as : \\test.s4.com\myshare - no access and ask me for user and password ! \\192.168.1.6\myshare - access If using *s4-ad.test.s4.com* my share accessible !!! \\test.s4.com\myshare - no access ! \\s4-ad.s4.com http://test.s4.com\myshare - access ! \\test.s4.com\sysvol - access ! \\*s4-ad* http://test.s4.com. http://test.s4.comtest.s4.com\sysvol - access ! Note: In *\\test.s4.com* seen all the shared directory, but not accessible in *samba alpha17* no need type *s4-ad* what happened ? This is Bug in samba4 rc3 ? Thanks -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] access my created share in smb.conf Only by Ip
Let Mohammad try my recommendations and them we will talk about it. On 10/17/2012 9:07 AM, Rowland Penny wrote: On 17/10/12 15:20, Carlos R. Pena Evertsz wrote: Hi Mohammad, I had the same problem like many others, so I think samba should include a note like mine in their documentation. This is the trick for successfully access the share with the hostname.. Be sure you have the following lines in the smb.conf: netbios name = yourhostname This is set by default wins support = yes This turns on the wins server, you should only turn this on if it is the only one. Find the name resolve order directive and be sure you have it in the following order. name resolve order = wins lmhosts hosts bcast Add the following line: hosts allow = the host ip / mask Where the host ip is your server ip. the mask is the mask you are using in all your windows clients. If you set it like this, the only machine that will be able to connect would be the server itself. It should be, from data supplied, 192.168.1.0/255.255.255.0 This would allow any computer on the subnet to connect. This is the most important thing. For example If you have in your server the mask 255.255.0.0 then all your clients must have the same network mask. Windows clients with the same mask of the server will see the server on the network with it hostname otherwise you need to access the server by its ip number. I think this is a Windows issue but they have left it in this way so we have to live with it. I hope this can help you. I doubt it. Rowland Carlos Santo Domingo, Dominican Republic On 10/17/2012 6:55 AM, Mohammad Ebrahim Abravi wrote: Hello samba4 rc3 *s4-ad - samba server Host name test.s4.com - domain name* *Dns Server - Samba Internal DNS server , Bind 9.9.1-P2* *win xp* have access to default share such as sysvol by dns name (\\test.s4.com \sysvol) but if created a share in smb.conf Only access by IP such as : \\test.s4.com\myshare - no access and ask me for user and password ! \\192.168.1.6\myshare - access If using *s4-ad.test.s4.com* my share accessible !!! \\test.s4.com\myshare - no access ! \\s4-ad.s4.com http://test.s4.com\myshare - access ! \\test.s4.com\sysvol - access ! \\*s4-ad* http://test.s4.com. http://test.s4.comtest.s4.com\sysvol - access ! Note: In *\\test.s4.com* seen all the shared directory, but not accessible in *samba alpha17* no need type *s4-ad* what happened ? This is Bug in samba4 rc3 ? Thanks -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba 3 printing and CUPS
Hi Kristofer, Have you tried adding the directive use client drivers = yes in the printers section of smb.conf? On 9/25/2012 3:55 PM, Kristofer wrote: I am trying to set up Samba 3 with CUPS printers, and installing the drivers to the server. I have been able to add drivers to the server just fine, but when a client connects to a printer and tries to set it up, Windows 7 is seeing a null printer type, so it is not finding the appropriate drivers. Windows 7 says The '' printer driver is not installed on this computer …. So it appears that the type of printer is null when it gets passed back to windows 7, and it doesn't know what kind of printer to search for drivers for. CUPS has the correct printer models listed in it. Am I missing something? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Share working with IP not with hostname
This is the trick for successfully access the share with the hostname.. Be sure you have the following lines in the smb.conf: netbios name = yourhostname wins support = yes The following line in this order. name resolve order = wins lmhosts hosts bcast Add the following line: hosts allow = the host ip / mask Where the host ip is your server ip. the mask is the mask you are using in all your windows clients. This is the most important thing. For example If you have in your server the mask 255.255.0.0 then all your clients must have the same network mask. Windows clients with the same mask of the server will see the server on the network with it hostname otherwise you need to access the server by its ip number. I hope this can help you. Carlos Santo Domingo, Dominican Republic On 9/12/2012 10:37 AM, Gaiseric Vandal wrote: On 09/10/12 13:52, Nitin Thakur wrote: hi guys I managed to setup the share. I am able to access the share with IP address, but as soon as I try to do it via hostname, I get a user name and password pop up, which always fail to authenticate. Any setting I am missing? Thanks nitin What version of Samba? My guess is there is some sort of name lookup mismatch.Are you using a domain or workgroup? Are you using WINS? Are you using DNS?If the samba server is the WINS server you should be able to cat wins.dat and tdbdump wins.tbd to verify that the names are the same. In smb.conf, does the samba server netbios name match the DNS name? What is the client OS? The only other thing that might be happening is that the client and server are mismatching on using NTLM vs NTLM v2. The samba logs should show that. I could NOT get NTLMv2 to work on my samba servers I had to explicitly disable it in smb.conf. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] samba4 installation Error and mount: unknown filesystem type 'smbfs'
From command line type: mount -t cifs//mybooklive/myfolder/media/smb -o username=user,password=userpassword; On 9/5/2012 1:37 PM, JIA Pei wrote: Hi, all: Two questions. Environment: Ubuntu 12.04 1) mount: unknown filesystem type 'smbfs' With default Samba 2:3.6.3-2ubuntu2.3 installed, all the following 3 commands failed: a) $ sudo mount -t *smbfs* -o username=MYNAME,password=MYPWD //mybooklive/myfolder /media/smb/ mount: unknown filesystem type 'smbfs' b) /media$ sudo mount -t *cifs* -o username=MYNAME,password=MYPWD //mybooklive/myfolder/ /media/smb/ mount: wrong fs type, bad option, bad superblock on //mybooklive/myfolder/, missing codepage or helper program, or other error (for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount.type helper program) In some cases useful info is found in syslog - try dmesg | tail or so c) $ sudo smbmount //192.168.1.82/myfolder/ /media/smb/ -o user=MYNAME sudo: smbmount: command not found 2) I have no idea whether 1) has something to do with samba version? So, i decided to replace current samba 2:3.6.3-2ubuntu2.3 with samba4 . However, I met exactly the same issue as described here, https://bugzilla.samba.org/show_bug.cgi?id=8633 http://ubuntuforums.org/showthread.php?t=1983830 namely: samba.provision.InvalidNetbiosName: The name ''AJIT-EXTENSA-4630Z'' is not a valid NetBIOS name And, unfortunately, Solution as smb.conf generated by s4 - upgrade from s3: - rename the old smb.conf.bak back to smb.conf - as far as I can see you have a malformed netbios name parameter in the smb.conf: hence I would shorten it to be at max. 16 characters long - invoke the samba-tool domain samba3upgrade command (instructions and problem resolutions are found in our samba-technical mailing list archives) doesn't work for me at all. It seems I have to downgrade to samba 2:3.6.3-2ubuntu2.3, in order to remove this* not a valid NetBIOS name* Did anybody really solve this problem??? Cheers Pei JIA Email: jp4w...@gmail.com cell:+1 604-362-5816 Welcome to Vision Open http://www.visionopen.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Problem in sharing printers
Be sure samba is starting after CUPS. Try restarting samba and see if printers are accessible after you restart it. sudo /etc/init.d/samba restart or sudo service smbd restart sudo service nmbd restart Sincerely, Carlos R. Pena Santo Domingo, Dominican Republic I had the same problem, because in the Ubuntu Server On 8/6/2012 10:09 AM, Lorenzo Milesi wrote: Hi. I've configured a Samba PDC controller on which I've configured a couple of printers using Cups. I've set up the relevant config according to the documentation, so: load printers = Yes printing = cups printcap name = cups [print$] comment = Printer Drivers path = /dati/samba/drivers browseable = yes guest ok = no read only = yes write list = root,administrator,@Domain Admins directory mask = 0775 create mask = 0775 directory mask = 0775 create mask = 0775 force create mode = 0775 force directory mode = 6775 [printers] comment = All Printers path = /var/spool/samba browseable = Yes public = Yes guest ok = Yes writable = No printable = Yes write list = root,administrator,@Domain Admins The problem is that if I browse \\server I get the list of shares, including the two cups printers. If I go into the printer subfolder I see two printers with no name, so when I try to edit properties to upload drivers it complains printer has no name. Same happens if I go back to server shares' root and I try to add the printer, I get asked for the drivers, provide them, then when finishes copyin it complains the printer has no name or it's not on the server anymore. What could be the problem? thanks -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
