[Samba] "smbd/session.c:111(session_claim) Re-using invalid record" in Samba logs

[David Harrison]

Hi,
Just recently the logs of a production Samba server are being populated by
the following message:

"smbd/session.c:111(session_claim) Re-using invalid record"

Does anyone have any tips for fixing this "invalid record"?
(I believe it is related to the utmp = yes option which is set in
/etc/samba/smb.conf).

I do not believe this log message is serious, but we are experiencing domain
login problems with some Windows 7 clients and it would be good to remove
this issue, even if it not the source of the Windows 7 login problems.

Regards,

David Harrison
StressFree Solutions <http://www.stress-free.co.nz/>
linkedin.com/in/dhharrison
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Re: [Samba] Youtube Video

[David Harrison]

For those interested, I found David's screencast on YouTube here:
http://www.youtube.com/watch?v=8tYnjp_BleI


David


On Mon, Aug 9, 2010 at 4:37 PM, David Gonzalez  wrote:

> Hi there,
>
> I've created a litle video explaining on how to setup some group policy to
> redirect folders using Active Directory Tools and Group Policy Management
> tools, it works and I've tested it so i decided to include it on my small
> youtube Linux collection.
>
> Hope you enjoy it and like; might be it can make it to the wiki video
> library.
>
> Thanks for Samba 4, it really _IS_ the thing.
>
> Bless
>
> ---
> David Gonzalez H.
> DGHVoIP - OPEN SOURCE TELEPHONY SOLUTIONS
> Phone Bogotá: +(57-1)289-1168
> Phone Medellin: +(57-4)247-0985
> Mobile: +(57)315-838-8326
> MSN: da...@planetaradio.net
> Skype: davidgonzalezh
> WEB: http://www.dghvoip.com/
> Proud Linux User #294661
> --
> 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

[Samba] Removing a Samba4 DC from a Samba4 domain

[David Harrison]

Hi,
I have followed the steps described on the Samba wiki to setup a Samba4
domain and have added a second Samba4 dc to it:
http://wiki.samba.org/index.php/Samba4/HOWTO/Join_a_domain_as_a_DC

I was wondering what the process was to remove this server from the domain?

Is there a Samba4 net command that should be used, or is it a case of
deleting the DC via Window's dsa.msc?


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

Re: [Samba] how to "Disable Samba Roaming profile"

[David Harrison]

On Fri, Jun 11, 2010 at 5:19 PM, Muqtadir Kamal wrote:

>  Hey all, please let's me know how to "Disable Samba Roaming profile" In
> OpenLDAP+SAMBA SERVER  Regards
> Kamal 


To disable roaming profiles set the 'logon path' parameter in your smb.conf
to nothing.
e.g.
[global]
logon path =
logon home =

('logon home' is the legacy Win9x/NT equivalent)


If you have Windows computers with roaming profiles installed you'll need to
convert them to be local, or the next time users login they may have their
profile reset. On each desktop with roaming profiles:
- Right click on My Computer and select Properties.
- Go to the Advanced tab in the User Profiles section press the Settings
button.
- Select the appropriate roaming profile, press the Change Type button and
select local.


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

Re: [Samba] Installation problem

[David Harrison]

On Sat, Jun 5, 2010 at 9:21 PM, Miha Krajnc wrote:

> I am using Ubuntu server. Here is what i get when installing samba with
> sudo
> aptitude install samba: LINK  Also, if i do
> /etc/init.d/samba start, it puts out "sudo: /etc/init.d/samba: command not
> found". No i have not installed swat yet, i first want to get just the
> samba
> part working. And dpkg -l samba puts this out...
>
> Any other ideas? I tried everything i know and i dont know what to do
> anymore...
>
>
The command you want is dpkg -L samba

You may have stumbled on this bug/feature:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/312449


I would run the following commands to clear everything out and start again:
sudo apt-get --purge remove samba-common
sudo apt-get install samba


Once complete go to the /etc/samba and check the relevant config file
exists.

I've just tested all of this now and it works, so it shouldn't be an Ubuntu
10.04 packaging problem.


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

Re: [Samba] samba 4 for new authentication domain?

[David Harrison]

On Tue, Apr 27, 2010 at 6:30 PM, Morty

> wrote:

> On Mon, Apr 26, 2010 at 09:59:02PM -0700, Kevin Keane wrote:
>
> > Exactly WHY do you need AD instead of NT domains? Without
> > understanding that, I don't think your question can be answered.
>
> I have some COTS Windows web apps that want to authenticate either
> using local accounts or against AD.
>

You should clarify what mechanisms those web apps use for authentication.
Generally most web apps use LDAP/NTML for authentication and LDAP for
pulling user information.
These two things you can achieve more reliably using Samba3 with an LDAP
backend compared to Samba 4 (at this stage).

Another pathway you should investigate is whether a single sign-on (SSO)
system is applicable/appropriate.
There are plenty of choices out there, but it does depend on what your COTS
applications are.
The benefit of SSO is that it abstracts web application authentication from
your underlying authentication service.
It is a bit more work, and not all web applications work with it, but once
in place the results are very good.


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

Re: [Samba] Snow Leopard and Samba

[David Harrison]

On Wed, Apr 21, 2010 at 6:22 AM, jjrowan  wrote:

> A customer has an expanding number of Mac computers.  Last Friday and
> existing machine started having problems writing files to a Samba share on a
> CentOS 5.x server.  They had no problems prior to Friday.
>
>
This issue is caused by the recent OSX 10.6.3 update not supporting wide
links (see the Samba wide links security problem:
secunia.com/advisories/38454/).
See here for a discussion:
splatdot.com/fixing-snow-leopard-10-6-3-samba-write-access


If you are running the latest versions of Samba you will not experience this
problem because wide links are disabled by default. If you are not running a
current version, you do not need to disable unix extensions entirely, simply
disable wide links in your Samba's smb.conf file:

wide links = no
getwd cache = yes

* Enabling the getwd cache is recommended here:
oreilly.com/catalog/samba/chapter/book/appb_02.html
But whether it is relevant in this day and age I don't know.


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

Re: [Samba] Samba / Lucid / Windows 7 problem

[David Harrison]

Here is my smbldap-tools configuration in smb.conf:

   add user script = /usr/sbin/smbldap-useradd -m "%u"
   ldap delete dn = Yes
   add machine script = /usr/sbin/smbldap-useradd -w "%u"
   add group script = /usr/sbin/smbldap-groupadd -p "%g"
   add user to group script = /usr/sbin/smbldap-groupmod -m "%u" "%g"
   delete user from group script = /usr/sbin/smbldap-groupmod -x "%u" "%g"
   set primary group script = /usr/sbin/smbldap-usermod -g "%g" "%u"
   ldap passwd sync = yes


Is your add machine script directive similar/the same?


David


On Tue, Mar 23, 2010 at 11:38 PM, Torkil Svensgaard  wrote:

> My initial assumption about Windows XP was wrong, I can't join with that
> either, it just seemed that way. I failed to notice that removing the
> machine from the domain from within XP didn't actually remove it from the
> LDAP server and thus when I rejoined it apparently used the existing account
> instead of creating a new one through smdldap-useradd.
>
> The problem lies elsewhere, one of the lines in smbldap-useradd that fails
> looks like this:
>
> chomp( $pass =  );
>
> I presume an autogenerated password shold be passed to the script through
> some sort of STDIN redirection but that fails.
>
> Thanks,
>
> Torkil
>
>
> On 2010-03-23 10:42, David Harrison wrote:
>
>> You could try turning up the log level in smb.conf so that you can see
>> what
>> Windows 7 is passing to Samba, and in turn what it is sending to
>> smbldap-tools (sorry I don't know what level this will require).
>>
>> For reference, at one site with quite a few Windows 7 clients I am running
>> Ubuntu Server 9.10 with the Samba 3.3 packages from Sernet and
>> smbldap-tools.
>> I had some initial issues with Windows registry settings, but never any
>> issue with smbldap-tools and Windows 7.
>>
>>
>> David
>>
>>
>> On Tue, Mar 23, 2010 at 10:37 PM, Torkil Svensgaard
>>  wrote:
>>
>>  No, I'm not sure, but given that Windows XP machines can join with no
>>> problems (and thus smdldap-useradd is working, in this case), at the very
>>> least Windows 7 is doing something differently.
>>>
>>> The Windows 7 machine actually does end up on the LDAP server, as
>>> subsequent attempts to join complain about "The specified account already
>>> exists". In this case there are no errors from smbldap-useradd in the
>>> log.
>>>
>>> Thanks,
>>>
>>> Torkil
>>>
>>>
>>> On 2010-03-23 10:22, David Harrison wrote:
>>>
>>>  Are you sure this is a Windows 7 fault?
>>>>
>>>> By the looks of the Samba log smbldap-tools is causing the grief.
>>>> Have you confirmed smbldap-useradd is working from the terminal?
>>>>
>>>> You could also try adding the machine account to your LDAP server prior
>>>> to
>>>> joining it to the domain from the desktop.
>>>>
>>>>
>>>> David
>>>>
>>>>
>>>> On Tue, Mar 23, 2010 at 9:32 PM, Torkil Svensgaard
>>>>  wrote:
>>>>
>>>>  Hi list
>>>>
>>>>>
>>>>> I'm running a Samba PDC on Ubuntu Lucid (3.4.7) and am unable to join
>>>>> Windows 7 machines to the domain. I have applied the registry changes
>>>>> described at http://wiki.samba.org/index.php/Windows7
>>>>>
>>>>> Windows XP machines can join with no problems.
>>>>>
>>>>> Samba log:
>>>>>
>>>>> stty: standard input: Inappropriate ioctl for device
>>>>> Use of uninitialized value $pass in chomp at /usr/sbin/smbldap-useradd
>>>>> line
>>>>> 324.
>>>>> stty: standard input: Inappropriate ioctl for device
>>>>> stty: standard input: Inappropriate ioctl for device
>>>>> Use of uninitialized value $pass2 in chomp at /usr/sbin/smbldap-useradd
>>>>> line 330.
>>>>> stty: standard input: Inappropriate ioctl for device
>>>>> Use of uninitialized value $pass in string ne at
>>>>> /usr/sbin/smbldap-useradd
>>>>> line 334.
>>>>> Use of uninitialized value $pass2 in string ne at
>>>>> /usr/sbin/smbldap-useradd
>>>>> line 334.
>>>>>
>>>>> Windows 7 reports: A device attached to the system is not functioning.
>>>>>
>>>>> Any ideas?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Torkil
>>>>>
>>>>> --
>>>>> 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
>>>
>>>
>
> --
> 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

Re: [Samba] Samba / Lucid / Windows 7 problem

[David Harrison]

You could try turning up the log level in smb.conf so that you can see what
Windows 7 is passing to Samba, and in turn what it is sending to
smbldap-tools (sorry I don't know what level this will require).

For reference, at one site with quite a few Windows 7 clients I am running
Ubuntu Server 9.10 with the Samba 3.3 packages from Sernet and
smbldap-tools.
I had some initial issues with Windows registry settings, but never any
issue with smbldap-tools and Windows 7.


David


On Tue, Mar 23, 2010 at 10:37 PM, Torkil Svensgaard  wrote:

> No, I'm not sure, but given that Windows XP machines can join with no
> problems (and thus smdldap-useradd is working, in this case), at the very
> least Windows 7 is doing something differently.
>
> The Windows 7 machine actually does end up on the LDAP server, as
> subsequent attempts to join complain about "The specified account already
> exists". In this case there are no errors from smbldap-useradd in the log.
>
> Thanks,
>
> Torkil
>
>
> On 2010-03-23 10:22, David Harrison wrote:
>
>> Are you sure this is a Windows 7 fault?
>>
>> By the looks of the Samba log smbldap-tools is causing the grief.
>> Have you confirmed smbldap-useradd is working from the terminal?
>>
>> You could also try adding the machine account to your LDAP server prior to
>> joining it to the domain from the desktop.
>>
>>
>> David
>>
>>
>> On Tue, Mar 23, 2010 at 9:32 PM, Torkil Svensgaard
>>  wrote:
>>
>>  Hi list
>>>
>>> I'm running a Samba PDC on Ubuntu Lucid (3.4.7) and am unable to join
>>> Windows 7 machines to the domain. I have applied the registry changes
>>> described at http://wiki.samba.org/index.php/Windows7
>>>
>>> Windows XP machines can join with no problems.
>>>
>>> Samba log:
>>>
>>> stty: standard input: Inappropriate ioctl for device
>>> Use of uninitialized value $pass in chomp at /usr/sbin/smbldap-useradd
>>> line
>>> 324.
>>> stty: standard input: Inappropriate ioctl for device
>>> stty: standard input: Inappropriate ioctl for device
>>> Use of uninitialized value $pass2 in chomp at /usr/sbin/smbldap-useradd
>>> line 330.
>>> stty: standard input: Inappropriate ioctl for device
>>> Use of uninitialized value $pass in string ne at
>>> /usr/sbin/smbldap-useradd
>>> line 334.
>>> Use of uninitialized value $pass2 in string ne at
>>> /usr/sbin/smbldap-useradd
>>> line 334.
>>>
>>> Windows 7 reports: A device attached to the system is not functioning.
>>>
>>> Any ideas?
>>>
>>> Thanks,
>>>
>>> Torkil
>>>
>>> --
>>> 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
>
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Re: [Samba] Samba / Lucid / Windows 7 problem

[David Harrison]

Are you sure this is a Windows 7 fault?

By the looks of the Samba log smbldap-tools is causing the grief.
Have you confirmed smbldap-useradd is working from the terminal?

You could also try adding the machine account to your LDAP server prior to
joining it to the domain from the desktop.


David


On Tue, Mar 23, 2010 at 9:32 PM, Torkil Svensgaard  wrote:

> Hi list
>
> I'm running a Samba PDC on Ubuntu Lucid (3.4.7) and am unable to join
> Windows 7 machines to the domain. I have applied the registry changes
> described at http://wiki.samba.org/index.php/Windows7
>
> Windows XP machines can join with no problems.
>
> Samba log:
>
> stty: standard input: Inappropriate ioctl for device
> Use of uninitialized value $pass in chomp at /usr/sbin/smbldap-useradd line
> 324.
> stty: standard input: Inappropriate ioctl for device
> stty: standard input: Inappropriate ioctl for device
> Use of uninitialized value $pass2 in chomp at /usr/sbin/smbldap-useradd
> line 330.
> stty: standard input: Inappropriate ioctl for device
> Use of uninitialized value $pass in string ne at /usr/sbin/smbldap-useradd
> line 334.
> Use of uninitialized value $pass2 in string ne at /usr/sbin/smbldap-useradd
> line 334.
>
> Windows 7 reports: A device attached to the system is not functioning.
>
> Any ideas?
>
> Thanks,
>
> Torkil
>
> --
> 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

[Samba] Windows clients forget the name of a Samba network drive (e.g. "Network Drive P:")

[David Harrison]

Every so often Windows XP clients seem to forget the name of the network
drives on a Samba server.

For example, in Windows Explorer instead of seeing "Projects P:", users are
presented with "Network Drive P:".


Does anyone know if this is anything to do with Samba or just a strange
Windows quirk?
Samba seems to be operating without any issues and there isn't anything
untoward in the logs that would suggest a problem.


Note: This wouldn't be a problem except for the fact it seems to cause
issues with Retrospect's automated backup routine.


Regards,


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

Re: [Samba] Samba multi-site advice request please

[David Harrison]

I am doing pretty much the same thing for a client right now.

A few things I'm doing that have made my life easier:

- Use the Samba 3.3.10 packages from Sernet to avoid any unwelcome printer
issues:
  http://enterprisesamba.org/

- Use a central puppet server to store/distribute your system
configurations:
  http://reductivelabs.com/trac/puppet/wiki/AboutPuppet

- This Samba/LDAP guide from Ubuntu is pretty good:
  https://help.ubuntu.com/9.04/serverguide/C/samba-ldap.html
  https://help.ubuntu.com/9.04/serverguide/C/openldap-server.html

- If you don't need full DNS checkout dnsmasq, it is ideal
for satellite offices:
  http://www.thekelleys.org.uk/dnsmasq/doc.html

- Disable roaming profiles because they are a world of hurt.


A few pain points:
- Windows 7: it seems to be a bit of a lottery whether it joins the domain
or not (even with registry tweaks).

- OpenLDAP 2.4 multi-master replication: the instructions from the Ubuntu
and OpenLDAP guys are pretty straightforward, but when it breaks, or doesn't
quite work right, your head starts to hurt.


Apart from that everything has gone very smoothly.
Server and network utilisation is low, and even better, it has meant two
Windows 2003 servers have been put out to pasture.


David


On Mon, Feb 1, 2010 at 1:00 PM, Julian Pilfold-Bagwell <
j...@bordengrammar.kent.sch.uk> wrote:

> Hi all,
>
> I am looking at setting up a multi-site office and need to put a plan
> forward.  The site consists of one head office and several branch office
> and my plan so far is this:
>
> In head office, one Samba PDC.  Each branch office will have a local BDC
> that also stores files local to the branch, hopefully cutting down the
> day to day traffic across the VPN.  The VPN I plan to use is OpenVPN in
> bridge mode in order to allow broadcasts e.g. WINS etc., to traverse the
> connections.  All the servers will have their own LDAP server and all
> will be synced to keep the authentication consistent and reduce VPN
> traffic.  Each site will have it's own DNS,  the PDC being the master
> and the BDCs slaves. The low number of machines involved mean I can set
> the clients to use their local DNS.
>
> The whole plot will be required to run across 2mb SDSL as this is all
> the budget will stretch to.
>
> Every other proposal has involved server 2008 and terminal services but
> I really want to go down the Linux/Samba route.
>
> Is there anyone out there that has successfully pulled this off and can
> give me some advice?  I've spent a few hours searching Google but their
> doesn't seem to be any definite info/howtos.
>
> thanks,
>
> Julian PB
>
>
> --
> 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

Re: [Samba] Error when trying to print with point and print installed drivers

[David Harrison]

 2010/1/30 

> I have an Ubuntu Sever 9.10 setup running Samba as a PDC for a bunch of

Windows clients.

Everything is functioning perfectly except for the point and print delivery

of printer drivers.


> I have tested this with Ubuntu 9.10's Samba (3.4.0) and two of the Debian

Samba packages (3.4.3 and 3.4.5). All seem to demonstrate the same problem.


>
> *What works:*

Adding a printer and manually installing the drivers to the client works

perfectly.


> Installing drivers and associating them to printers shared by Samba works

fine via the Windows GUI and the rpcclient tool. Adding the printer to a

Windows client also appears to work, i.e. the driver downloads, installs and

the printer is visible.


> *What doesn't:*

Unfortunately when trying to print using the point and print configured

printer a generic 'failed to print' message is returned by Windows.




Just a follow up - based on Jeremy's response to the 64bit Windows printing
question:
http://lists.samba.org/archive/samba/2010-January/153456.html

I have 'downgraded' to the Samba 3.3.10 packages provided by SerNet:
http://enterprisesamba.org/

Point and print works without any issues with this version and we don't have
to jump through hoops to get printers on the 64bit machines working.
The only downer is one of the Windows 7 desktops is refusing to join the
domain, but I'm hoping one of the many registry tweaks around should fix
that...


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

[Samba] Error when trying to print with point and print installed drivers

[David Harrison]

I have an Ubuntu Sever 9.10 setup running Samba as a PDC for a bunch of
Windows clients.
Everything is functioning perfectly except for the point and print delivery
of printer drivers.

I have tested this with Ubuntu 9.10's Samba (3.4.0) and two of the Debian
Samba packages (3.4.3 and 3.4.5). All seem to demonstrate the same problem.


*What works:*
Adding a printer and manually installing the drivers to the client works
perfectly.

Installing drivers and associating them to printers shared by Samba works
fine via the Windows GUI and the rpcclient tool. Adding the printer to a
Windows client also appears to work, i.e. the driver downloads, installs and
the printer is visible.

*What doesn't:*
Unfortunately when trying to print using the point and print configured
printer a generic 'failed to print' message is returned by Windows.


In the Samba logs there is the following error (this occurs when opening
preferences and trying to print):


[2010/01/29 22:00:25,  1] smbd/service.c:1047(make_connection_snum)
  snowball (192.168.2.30) connect to service print$ initially as user david
(uid=1021, gid=513) (pid 2214)
[2010/01/29 22:00:31,  0] lib/fault.c:46(fault_report)
  ===
[2010/01/29 22:00:31,  0] lib/fault.c:47(fault_report)
  INTERNAL ERROR: Signal 11 in pid 2214 (3.4.5)
  Please read the Trouble-Shooting section of the Samba3-HOWTO
[2010/01/29 22:00:31,  0] lib/fault.c:49(fault_report)

  From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2010/01/29 22:00:31,  0] lib/fault.c:50(fault_report)
  ===
[2010/01/29 22:00:31,  0] lib/util.c:1480(smb_panic)
  PANIC (pid 2214): internal error
[2010/01/29 22:00:31,  0] lib/util.c:1584(log_stack_trace)
  BACKTRACE: 25 stack frames:
   #0 /usr/sbin/smbd(log_stack_trace+0x2d) [0x836632d]
   #1 /usr/sbin/smbd(smb_panic+0x2d) [0x836644d]
   #2 /usr/sbin/smbd [0x8353c3e]
   #3 [0xb77a7400]
   #4 /usr/lib/libtalloc.so.2(_talloc_free+0x1d5) [0xb746e915]
   #5 /usr/sbin/smbd [0x82a67cb]
   #6 /usr/sbin/smbd [0x82e8f09]
   #7 /usr/sbin/smbd(api_pipe_request+0x192) [0x82e9752]
   #8 /usr/sbin/smbd [0x82e25fa]
   #9 /usr/sbin/smbd(np_write_send+0x637) [0x82e2c97]
   #10 /usr/sbin/smbd [0x80e3d06]
   #11 /usr/sbin/smbd [0x80e430b]
   #12 /usr/sbin/smbd(reply_trans+0x686) [0x80e4e26]
   #13 /usr/sbin/smbd [0x81496de]
   #14 /usr/sbin/smbd [0x8149b4d]
   #15 /usr/sbin/smbd [0x814a3ad]
   #16 /usr/sbin/smbd(run_events+0x12e) [0x837745e]
   #17 /usr/sbin/smbd(smbd_process+0x827) [0x8148e37]
   #18 /usr/sbin/smbd [0x8646695]
   #19 /usr/sbin/smbd(run_events+0x12e) [0x837745e]
   #20 /usr/sbin/smbd [0x83776ff]
   #21 /usr/sbin/smbd(_tevent_loop_once+0x98) [0x8377d48]
   #22 /usr/sbin/smbd(main+0xc92) [0x86473c2]
   #23 /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe6) [0xb7332b56]
   #24 /usr/sbin/smbd [0x80c3eb1]
[2010/01/29 22:00:31,  0] lib/util.c:1485(smb_panic)
  smb_panic(): calling panic action [/usr/share/samba/panic-action 2214]
[2010/01/29 22:00:31,  0] lib/util.c:1493(smb_panic)
  smb_panic(): action returned status 0
[2010/01/29 22:00:31,  0] lib/fault.c:326(dump_core)
  dumping core in /var/log/samba/cores/smbd
[2010/01/29 22:00:41,  1] smbd/service.c:1047(make_connection_snum)
  snowball (192.168.2.30) connect to service print$ initially as user david
(uid=1021, gid=513) (pid 2271)




Here is the output of the rpcclient's enumprinters, The first printer
doesn't have the driver installed (and works) whilst the second has the
driver installed (and doesn't):

rpcclient $> enumprinters 2
servername:[\\fissionator]
printername:[\\fissionator\Ricoh]
sharename:[Ricoh]
portname:[Samba Printer Port]
drivername:[]
comment:[Ricoh 3245C MFD]
location:[]
sepfile:[]
printprocessor:[winprint]
datatype:[RAW]
parameters:[]
attributes:[0x1048]
priority:[0x1]
defaultpriority:[0x1]
starttime:[0x0]
untiltime:[0x0]
status:[0x0]
cjobs:[0x0]
averageppm:[0x0]



servername:[\\fissionator]
printername:[\\fissionator\RICOH Aficio 3245C PCL 6]
sharename:[RicohTest]
portname:[Samba Printer Port]
drivername:[RICOH Aficio 3245C PCL 6]
comment:[Ricoh 3245C test]
location:[]
sepfile:[]
printprocessor:[winprint]
datatype:[RAW]
parameters:[]
attributes:[0x1848]
priority:[0x1]
defaultpriority:[0x1]
starttime:[0x0]
untiltime:[0x0]
status:[0x0]
cjobs:[0x0]
averageppm:[0x0]


Here is the output of rpcclient's enumdrivers:
rpcclient $> enumdrivers 3
[Windows NT x86]
Printer Driver Info 3:
Version: [3]
Driver Name: [RICOH Aficio 3245C PCL 6]
Architecture: [Windows NT x86]
   

Re: [Samba] AutoCad and ArcView

[David Harrison]

On 17/11/2006, at 4:42 AM, James McLaughlin wrote:


Thanks for all the replies yesterday.

Back to the initial question -- does anyone else have more  
references or

a working .conf file that is designed, tested and working in an
environment where large files (40-200MB) are being R/W constantly.


I am using Samba (on top of reiserfs/ext3) in a couple of  
architecture workplaces similar to yours (5-10 users).
No errors like yours are experienced and the only non-standard  
smb.conf settings I use are:


(In the [global] section)
strict locking  = no
socket options  = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192  
IPTOS_LOWDELAY


In a couple of other places I am using Samba as a media server for  
500meg-2gig file sizes and have experienced no problems there either.
In these situations I am using an underlying XFS file system and the  
majority of tasks are intensive reads rather than read/write.


It would be very strange for Samba to be destroying your disks but I  
can understand file corruption and locking problems because of the  
size and nature of the files (AutoCAD seems to try its best to  
corrupt files on a good day).


I've found most problems like you describe eventually lead their way  
back to a misbehaving RAID card or driver issue.
Either way its not a good position to be in, best of luck and when in  
doubt simplify :-)



David



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

Re: [Samba] Weird Samba upload performance on Gigabit network - resolved with new NIC

[David Harrison]

On 13/11/2006, at 8:23 AM, David Harrison wrote:

Here's a weird one that may have nothing to do with Samba and  
more to do with network frame sizes.
I have recently upgraded the network infrastructure to support  
gigabit speeds.

- OSX Tiger to OSX Tiger file transfers operate at gigabit speeds.
- Samba 3.0.23C (Suse 10) to OSX Tiger file transfers operate at  
gigabit speeds.
- BUT OSX Tiger to Samba 3.0.23C (Suse 10) file transfers operate  
at 1-2meg/second which is well down from expected performance.
The strange thing is if I begin a file transfer from OSX Tiger to  
Samba and in a terminal window on OSX begin an SCP copy operation  
to the same Suse server the file transfer speed of Samba jumps up  
to gigabit level speeds. As soon as the SCP copy operation is  
stopped the Samba file transfer process drops to 1-2meg/second  
again.


Yes I am running 10.4.8 on the clients.
Just as a test I have mounted the Samba volume from the command  
line (with mount.cifs and mount.smbfs) and received the same  
performance as through the Finder so if the problem is with 10.4.8  
its at a fairly low level.


I replaced the network card on the Suse box from the Netgear card  
(r8169 driver) to a HP NC1020 (tg3 driver).
Samba performance is now at gigabit levels and is very consistent  
with multiple Linux (Suse) and OSX (10.4.8) clients.
The Netgear card appears to operate okay as a Samba client on another  
machine but still performs poorly when the Samba process is receiving  
large quantities of uploaded data.



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

Re: [Samba] Checklist for eDirectory back-end?

[David Harrison]

On 14/11/2006, at 11:24 AM, David Harrison wrote:


On 11/11/2006, at 1:10 PM, Patricio A. Bruna wrote:


You have to look in Novell site.
maybe start in:
http://www.novell.com/coolsolutions/appnote/11788.html


You may run into trouble as you follow this document through as it  
assumes you have a Novell Open Enterprize Server in the directory  
tree.
The process of adding an OES system to the tree extends the schema  
in a number of not clearly documented ways.
If you are not running OES then extending the schema to work with  
correctly with Linux User Manager as described is a very difficult  
task, I could not get it to work on a vanilla eDirectory install  
with all the relevant schema extensions applied (that is the  
extensions I could identify through trial and error).


If you do get Samba/eDirectory authentication working by following  
this article without resorting to adding OES to the tree I would  
like to hear how.
Considering the power of Samba and Novell's financial interest in  
it you would assume getting eDirectory to work with it cleanly  
would be a much simpler task than what is described above.


Sorry I was mistaken the Novell document I was referring to which  
references Linux User Manager and OES is this one:

http://wiki.novell.com/index.php/OES_as_PDC

The document referenced above (http://www.novell.com/coolsolutions/ 
appnote/11788.html) does not utilise Universal Password or provide  
any identification functionality above basic user access. This maybe  
what you are after but personally I would prefer something that did  
not require users to maintain multiple passwords, integrates with  
other Windows/Samba servers more closely and provided the smooth  
administration experience of the iManager LUM plug-in.


Regards,


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

Re: [Samba] Checklist for eDirectory back-end?

[David Harrison]

On 11/11/2006, at 1:10 PM, Patricio A. Bruna wrote:


You have to look in Novell site.
maybe start in:
http://www.novell.com/coolsolutions/appnote/11788.html


You may run into trouble as you follow this document through as it  
assumes you have a Novell Open Enterprize Server in the directory tree.
The process of adding an OES system to the tree extends the schema in  
a number of not clearly documented ways.
If you are not running OES then extending the schema to work with  
correctly with Linux User Manager as described is a very difficult  
task, I could not get it to work on a vanilla eDirectory install with  
all the relevant schema extensions applied (that is the extensions I  
could identify through trial and error).


If you do get Samba/eDirectory authentication working by following  
this article without resorting to adding OES to the tree I would like  
to hear how.
Considering the power of Samba and Novell's financial interest in it  
you would assume getting eDirectory to work with it cleanly would be  
a much simpler task than what is described above.


Regards,


David

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

Re: [Samba] Weird Samba upload performance on Gigabit network

[David Harrison]

On 13/11/2006, at 2:00 AM, Michael Gasch wrote:


are you by any chance running OSX 10.4.8?
we had the same problem and it was related to samba & OSX (10.4.8).  
OSX to an W2k3-Server was fine. so we thought it might be samba.  
but after downgrading OSX to 10.4.7 everything was fine again. so  
the apple update must have changed/ broken something. we did not  
look deeper into it. on google groups we found one posting with the  
same problem but between OSX and W2k. ftp, etc. was fine on OSX,  
only smb/ cifs was slow


David Harrison wrote:
Here's a weird one that may have nothing to do with Samba and more  
to do with network frame sizes.
I have recently upgraded the network infrastructure to support  
gigabit speeds.

- OSX Tiger to OSX Tiger file transfers operate at gigabit speeds.
- Samba 3.0.23C (Suse 10) to OSX Tiger file transfers operate at  
gigabit speeds.
- BUT OSX Tiger to Samba 3.0.23C (Suse 10) file transfers operate  
at 1-2meg/second which is well down from expected performance.
The strange thing is if I begin a file transfer from OSX Tiger to  
Samba and in a terminal window on OSX begin an SCP copy operation  
to the same Suse server the file transfer speed of Samba jumps up  
to gigabit level speeds. As soon as the SCP copy operation is  
stopped the Samba file transfer process drops to 1-2meg/second again.


Yes I am running 10.4.8 on the clients.
Just as a test I have mounted the Samba volume from the command line  
(with mount.cifs and mount.smbfs) and received the same performance  
as through the Finder so if the problem is with 10.4.8 its at a  
fairly low level.


My money's still on the gigabit network card on the Samba machine,  
once the new card arrives I'll not only be able to test it with  
10.4.8 but also run some gigabit transfer tests from Linux machine to  
Linux machine which should clearly identify where the problem lies.



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

Re: [Samba] Weird Samba upload performance on Gigabit network

[David Harrison]

On 11/11/2006, at 6:04 AM, Andrew Morgan wrote:


On Fri, 10 Nov 2006, David Harrison wrote:


On 10/11/2006, at 12:22 PM, John Drescher wrote:


On 11/9/06, David Harrison <[EMAIL PROTECTED]> wrote:
- BUT OSX Tiger to Samba 3.0.23C (Suse 10) file transfers operate at
1-2meg/second which is well down from expected performance.
The strange thing is if I begin a file transfer from OSX Tiger to
Samba and in a terminal window on OSX begin an SCP copy operation to
the same Suse server the file transfer speed of Samba jumps up to
gigabit level speeds. As soon as the SCP copy operation is stopped
the Samba file transfer process drops to 1-2meg/second again.
Looking at your numbers I believe that you have both network and  
samba problems.

Can you run netperf or do some nfs testing?
Today I ran it and found out a few of my servers (using nvidia  
mobo adapters) although the gigabit light was on the nic and the  
switch the adapter was not transfering at gigabit speeds.  I did  
a nfs test like the following:

dd if=/dev/zero of=/mnt/remoteserver/test.dat bs=16k count=16k
and got around 10MB/s which is only 100mbit speeds. On netperf I  
verified that my maximum transfer rate was around 94mbit/s so I  
googled a bit and then ended up upgrading my kernel to 2.6.18 and  
then did the same test and I got 109 MB/s on netperf and on the  
nfs test above I got 43MB/s and after setting nfs to asynchronous  
mode I got 57MB/s.

John


I've updated the Suse box to the 2.6.18.2 kernel with no effect.
I'm not in a position to run NFS tests on the machine but I'm  
guessing it is the network card (low-end Netgear with the r8169  
driver).
To (hopefully) fix the problem for good I've ordered a decent  
gigabit card that by the looks of it has good Linux support.
I'd rather spend the money than continue messing with a card/ 
driver that according to Google has some underlying performance  
issues :-)


Have you verified that the duplex settings on the network switch  
and the Suse server are the same?  If you have half duplex on the  
Suse server and full duplex on the network switch, you could get  
the behavior you describe.


Andy


No the network checks out, all interfaces are running at 1000baseT  
full duplex.
Network performance in general is good for other services, it seems  
the only issue is with client upload rates to the Samba server.


It would appear to be very similar to this issue in terms of the  
hardware and symptoms:

http://lists.samba.org/archive/samba/2004-February/081668.html

Changing the NIC should resolve the problem and it will give me an  
opportunity to test the card on another system.



David








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

Re: [Samba] Weird Samba upload performance on Gigabit network

[David Harrison]

On 10/11/2006, at 12:22 PM, John Drescher wrote:


On 11/9/06, David Harrison <[EMAIL PROTECTED]> wrote:
- BUT OSX Tiger to Samba 3.0.23C (Suse 10) file transfers operate at
1-2meg/second which is well down from expected performance.

The strange thing is if I begin a file transfer from OSX Tiger to
Samba and in a terminal window on OSX begin an SCP copy operation to
the same Suse server the file transfer speed of Samba jumps up to
gigabit level speeds. As soon as the SCP copy operation is stopped
the Samba file transfer process drops to 1-2meg/second again.

Looking at your numbers I believe that you have both network and  
samba problems.


Can you run netperf or do some nfs testing?

Today I ran it and found out a few of my servers (using nvidia mobo  
adapters) although the gigabit light was on the nic and the switch  
the adapter was not transfering at gigabit speeds.  I did a nfs  
test like the following:


dd if=/dev/zero of=/mnt/remoteserver/test.dat bs=16k count=16k

and got around 10MB/s which is only 100mbit speeds. On netperf I  
verified that my maximum transfer rate was around 94mbit/s so I  
googled a bit and then ended up upgrading my kernel to 2.6.18 and  
then did the same test and I got 109 MB/s on netperf and on the nfs  
test above I got 43MB/s and after setting nfs to asynchronous mode  
I got 57MB/s.


John


I've updated the Suse box to the 2.6.18.2 kernel with no effect.
I'm not in a position to run NFS tests on the machine but I'm  
guessing it is the network card (low-end Netgear with the r8169 driver).
To (hopefully) fix the problem for good I've ordered a decent gigabit  
card that by the looks of it has good Linux support.
I'd rather spend the money than continue messing with a card/driver  
that according to Google has some underlying performance issues :-)


Regards,


David

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

[Samba] Weird Samba upload performance on Gigabit network

[David Harrison]

Here's a weird one that may have nothing to do with Samba and more to  
do with network frame sizes.


I have recently upgraded the network infrastructure to support  
gigabit speeds.


- OSX Tiger to OSX Tiger file transfers operate at gigabit speeds.
- Samba 3.0.23C (Suse 10) to OSX Tiger file transfers operate at  
gigabit speeds.
- BUT OSX Tiger to Samba 3.0.23C (Suse 10) file transfers operate at  
1-2meg/second which is well down from expected performance.


The strange thing is if I begin a file transfer from OSX Tiger to  
Samba and in a terminal window on OSX begin an SCP copy operation to  
the same Suse server the file transfer speed of Samba jumps up to  
gigabit level speeds. As soon as the SCP copy operation is stopped  
the Samba file transfer process drops to 1-2meg/second again.


My guess is this has something to do with network frame sizes but I  
don't really know.


The gigabit card on the Suse box is a low-end model but the fact that  
downloads and non-Samba related uploads appear to work fine (with low  
CPU usage in all cases) suggests this is more to do with inbound SMB  
packets rather than the hardware itself.


Any hints/pointers would be appreciated.

Regards,


David


P.S. Sorry I thankfully do not have any 'real' Windows machines to  
test performance on.




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

[Samba] Problem with length of share names

[David Harrison]

Hi all,
I'm wondering if there is some restriction on the length of share names 
that prevents shares with names over 12 characters being browsed to ?

I have a share with a name that is 14 characters, and I'm able to 
connect to it if I type in the name by hand, but I can't browse to it 
from either Windows or MacOSX boxes (`smbclient -L host` also won't see it).

I'm using Debian sarge with package version 3.0.10-1
I've been searching around and I have only found one or two references 
to this problem, both of which are about 4 years old.

Is this actually a limitation ? a bug in my config ?  a known bug ?
Any help is appreciated
Cheers
Dave
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba