[Samba] broken printing 4.0.5

2013-05-04 Thread steve

Hi everyone
I'm still stuggling with this
https://bugzilla.samba.org/show_bug.cgi?id=9745

I've now reproduced the bug with openSUSE and Ubuntu DC's, on w7 and xp 
clients. It seems that Samba is not looking in the correct directory for 
the printer drivers, which windows has copied to the correct directory 
on the DC.


Does anyone have printing working on 4.0.5 using the method in the wiki? 
If so, could you share?

Cheers,
Steve
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba


Re: [Samba] [samba4] Build requires libncurses-dev

2013-05-04 Thread Rowland Penny

On 03/05/13 22:33, Ricky Nance wrote:

I'd like to get a dev's input as to why this is now required, I have no
problem adding it to the wiki as long as they expect it and it wasn't just
something that crept in. If Jeremy or Andrew (or any other dev that sees
this) would confirm this I will add it.

Ricky


On Fri, May 3, 2013 at 2:23 PM, Nick Semenkovich seme...@alum.mit.eduwrote:


+1 for this. Looks like a new dependency that just popped up in the
last few commits.

On Fri, May 3, 2013 at 6:02 AM, Michael De Groote
i...@sint-pietersschool.be wrote:

I tried building the latest master from git on debian wheezy.
It seems to require libncurses-dev.

I thought to add it into the wiki as a required package to install, but

it

seems one needs to ask for a login to the wiki. No prob ;)

Could someone add it to the wiki? Or is this an unintentional dependency
that will be removed?

--
Michael De Groote
ICT-coordinator Sint-Pietersschool Korbeek-Lo
ICT-support Sancta Maria Basisschool Leuven
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba


Hi,
It is probably down to the ncurses based regedit tool that Michael Adam 
added, something to do with last years GSoC students work, there was a 
post about it over on samba-technical.


Rowland


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba


Re: [Samba] nis homedir issue on samba- 3.6.9-151.el6 (CentOS 6.4 64bit)

2013-05-04 Thread Vincenzo De Sanctis
is winbind needed for nis homedir?


2013/5/1 Vincenzo De Sanctis vincenzo.desanc...@gmail.com

 can be a pam problem?

 [root@dork]# cat /etc/pam.d/samba
 #%PAM-1.0
 auth   required pam_nologin.so
 auth   include  password-auth
 accountinclude  password-auth
 sessioninclude  password-auth
 password   include  password-auth



 2013/5/1 Vincenzo De Sanctis vincenzo.desanc...@gmail.com

 maybe there is a bug regarding the use of nis to mount the user's home
 directory at the login or my misconfiguration.
 After the CentOS 6.4 (64bit) installation I checked for the latest samba
 version on the official repository using yum: the latest version (that was
 already installed) is samba- 3.6.9-151.el6.
 From man smb.conf I have seen that nis homedir is not yet deprecated,
 I used it a decade ago on samba-2.2.12 with successful.
 On CentOS 6.4 I don't use ldap, but only nis and the latter works without
 problem, I installed also autofs (auto.home).
 autofs+nis are simple and work great, I can 'su' home users on nfs
 without problem.


 [global]

workgroup = DORK   ;changed for privacy
netbios name = lince
server string = DMIT domain server
interfaces = eth0

 ;   smb ports = 445

hosts allow = 129.123.38., 139.123.39., 179.21.23., 127. ;changed for
 privacy
hosts deny = ALL

os level = 33
domain master = yes
local master = yes
preferred master = yes
domain logons = yes
security = user
guest accout = guest
encrypt passwords = yes
check password script = /usr/local/sbin/crackcheck -d
 /usr/share/cracklib/pw_dict

smb passwd file = /etc/samba/smbpasswd
passdb backend = smbpasswd
username map = /etc/samba/smbusers

time server = Yes

log file = /var/log/samba/pc/%m.log

nis homedir = yes
homedir map = auto.home

null passwords = yes
client lanman auth = no

logon script = logon.bat
logon path =
logon drive = M:
logon home = \\%N\%U

wins support = no
wins server = winsserver  ;changed for privacy

log level = 2
lock directory = /var/log/samba/locks/
state directory = /var/log/samba/state/
cache directory = /var/log/samba/cache/
pid directory = /var/log/samba/pid/
usershare path = /var/log/samba/usershare/
printjob username = %M\%U
hide dot files = No[netlogon]
path = /etc/samba/netlogon

 ;   max protocol = smb2

kernel oplocks = no
oplocks = no
level2 oplocks = no
posix locking = no

follow symlinks = yes
wide links = yes
unix extensions = no
nt acl support = no

printing = lprng
printcap name = /usr/local/samba/lib/printcap
load printers = yes
print command = /usr/bin/lpr -P%p %s; rm %s
lpq command = /usr/bin/lpq -P%p
lprm command = /usr/bin/lprm -P%p %j
printcap cache time = 0

 ### speed tuning
socket options = IPTOS_LOWDELAY TCP_NODELAY SO_KEEPALIVE
write raw = yes
read raw = no

 ###  for japanese font :(
dos charset = cp932
display charset = cp932
unix charset = cp932

 ;  profiles drammatically slow the logout so I disabled
 ;  [profiles]
 ;  comment = Network Profiles Share
 ;  path = /etc/samba/profiles
 ;  read only = No
 ;  store dos attribute = Yes
 ;  create mask = 0600
 ;  directory mask = 0700
 ;  browseable = no


 [netlogon]
path = /etc/samba/netlogon
writeable = no
public = yes

 [root]
comment = Root di %h
path = /
read only = yes
public = no
locking = no

 [printers]
printable = yes
public = yes
writable = no
guest ok = yes

#create mode = 0700

 [homes]
comment = Users Home Directories
read only = No
create mask = 0644
directory mask = 0711
browseable = No
valid users = %S
 ;  %S = the name of the current service, if any. service = map name,
 ;  so map name A-USER can only be connected by A-USER, %S = %u
 ;
 ;  By default, \\server\username shares can be connected to by anyone
 ;  with access to the samba server. This parameter make sure that only
 ;  username can connect to \\server\username

 [project]
comment = Group project directories
path = /usr/local/samba/lib/prj  ;this path contains several links to
 nfs
read only = no
writable = yes
create mode = 0775
force create mode = 0775
directory mode = 02775
force directory mode = 02775
public = no
oplocks = no
  continues but not important!



 As you can see in the smb.conf  I added 'nis homedir = yes' and 'homedir
 map = auto.home'
 Samba- 3.6.9-151.el6 is included in CentOS 6.4 so to check if has been
 compiled with configure --with-automount I used the command 'smbd -b|grep
 -i automount':

   [root@dork]#smbd -b| grep -i automount
 WITH_AUTOMOUNT
 WITH_AUTOMOUNT

 this is a piece of my /etc/auto.home:

 pippo  server1:/dati3/export/home/
 pluto server2:/iscsi/home/
 #paperino 

[Samba] Hello a query to relieve some confusion about samba

2013-05-04 Thread CCOR58

Hi
I am new today here and have a couple of confusing items I hope someone 
here o the list can straighten out for me.


1. The definitions of the served usershares apprears in more than one 
location; in ubutu 12.04 LTS there appears to be a set of defined shares 
in the /etc/samba/smb.conf file near the bottom, the second location 
appears to be located in the file structure at /var/lib/samba/usershares 
and a possible third area it seems is /srv/samba/sharename.


Which one is affected when sitting it up appears to be related to which 
program one uses to set the shares and/or the server up to begin with; 
if a terminal net command set is used, the /var/lib/samba locations 
appear to be used; if any of the other config programs or right-click 
share in nautilus etc then the share seems to be defined in the smb.conf 
file and seems to be located either in a specified mount location or 
else the /srv/samba/ locations.


What is confusing is how it gets this way, and how either duplicate 
shares are created or no change is seen when one follows any one of a 
number of the online guides, forums or tutorials. Again each tutorial is 
written based on one's successful attempt to set samba up and of course 
will cause that tutorial to lean one way or the other. Hence if one is 
having trouble and follows one tutorial then sees in the network browser 
either no change or now duplicate shares it would be frustrating to say 
the least.


What isn't obvious is it appears samba server automatically serves up 
whatever shares have been defined regardless of their location which 
tends to make sense if all is defined in the smb.conf file. But if one 
method has set up the shares in /var/lib/samba/usershares and a noobie 
isn't aware of same one begins to wonder how the server knows to serve 
both locations when all instructions seem to indicate all is defined in 
the smb.conf file. How does the server get the info on these shares when 
although they are defined in that location they are not referred to in 
the smb.conf file? and no ref in the smb.conf file seems to indicate 
that samba server is to look anywhere else for a database or registry to 
find the data?


2. I am able to see workstations in the workgroup of the network 
browser, and when I attempt to see the shares sometimes, depending on 
the machine, I get a network path error not found or unable to 
download master list and no real clear indication of why or where to 
troubleshoot this problem; on other machines it will show the w/s's and 
give a login splashscreen but will not allow a succesful login with a 
samba defined userID and password or any linux desktop userID's  PW's 
existing on all machines with the linux-samba password sync enabled. It 
simply doesn't allow a login.


I use 7 pc's  [ 1 boots win7 or win xp pro-sp3; 2nd boots win7, xp 
pro-sp3, mint 14; 1 boots mint 14, 1 boots ubuntu studio 12.04 or 
centos6.3; laptop boots win7 or ubuntu studio 12.04; 1 boots ubuntu 
studio 12.04]. all linux are set to use NFS and samba is to play nice 
with the two win boxes and laptop.


Each flavor of linux, as well as version seems to use slightly different 
configuring methods for samba; hence the need to clearly understand it 
so that I can arrive at a more or less common single smb.conf method for 
shares.



Whatever info anyone can provide will be very much appreciated.

Thanks

Flaggmann
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba


Re: [Samba] [samba4] Build requires libncurses-dev

2013-05-04 Thread Andrew Bartlett
On Fri, 2013-05-03 at 16:33 -0500, Ricky Nance wrote:
 I'd like to get a dev's input as to why this is now required, I have
 no problem adding it to the wiki as long as they expect it and it
 wasn't just something that crept in. If Jeremy or Andrew (or any other
 dev that sees this) would confirm this I will add it.


That would be the new registry editor we just got, I think.  If this
causes a great problem, it could be made optional I suppose, but it
should go on the list for platforms that have it.

Andrew Bartlett

-- 
Andrew Bartletthttp://samba.org/~abartlet/
Authentication Developer, Samba Team   http://samba.org


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba