On 1/6/12 3:31 PM, "Jeremy Allison" wrote:
>
>The problem I can see from the pastebin is an authentication
>issue. The client is trying to connect via a machine account.
>
>If you don't allow the machine account access to the print
>share then it'll get access denied.
>
>The error above is the m
On Fri, Jan 06, 2012 at 02:06:26PM -0600, Dale Schroeder wrote:
> On 01/05/2012 9:23 AM, Tom Ryan wrote:
> >On 1/5/12 9:31 AM, "Tom Ryan" wrote:
> >
> >>[2012/01/05 09:18:54.928729, 3] auth/auth_util.c:1028(check_account)
> >> Failed to find authenticated user DOMAIN\machinename$ via getpwnam(),
On Fri, Jan 6, 2012 at 3:06 PM, Dale Schroeder
wrote:
> Samba 3.6 had a rewrite of the printing code. If you haven't already, you
> can read about it here:
> http://www.samba.org/samba/history/samba-3.6.0.html
With the winbind and printing issues I've seen with 3.6 my take is
that it isn't quite
On 01/05/2012 9:23 AM, Tom Ryan wrote:
On 1/5/12 9:31 AM, "Tom Ryan" wrote:
[2012/01/05 09:18:54.928729, 3] auth/auth_util.c:1028(check_account)
Failed to find authenticated user DOMAIN\machinename$ via getpwnam(),
denying access.
[2012/01/05 09:18:54.929709, 2] auth/auth.c:319(check_ntlm_
On 1/5/12 9:31 AM, "Tom Ryan" wrote:
>
>[2012/01/05 09:18:54.928729, 3] auth/auth_util.c:1028(check_account)
> Failed to find authenticated user DOMAIN\machinename$ via getpwnam(),
>denying access.
>[2012/01/05 09:18:54.929709, 2] auth/auth.c:319(check_ntlm_password)
> check_ntlm_password:
On 1/4/12 5:44 PM, "Tom Ryan" wrote:
>>
>>I've included a full log from a failed print session here:
>>
>>http://pastebin.com/WBA4PEnG
Ok, I've managed to determine that every user who is having an issue
printing has an error message like
[2012/01/05 09:18:54.928729, 3] auth/auth_util.c:1028(
On 1/4/12 9:57 AM, "Tom Ryan" wrote:
>
>I've included a full log from a failed print session here:
>
>http://pastebin.com/WBA4PEnG
Some additional info..
On one of our interim firewalls, we're noticing various dropped
connections from our client hosts to this particular samba server's port
13
On 1/4/12 9:13 AM, "Tom Ryan" wrote:
>We have recently started having an odd problem with printing via samba
>(3.6.1). Samba is joined via security = ads to our domain. We do not use
>winbind on this system. Our account usernames are provided via openldap.
>
>User starts system (generally windo
We have recently started having an odd problem with printing via samba (3.6.1).
Samba is joined via security = ads to our domain. We do not use winbind on this
system. Our account usernames are provided via openldap.
User starts system (generally windows 7 64bit, but we've seen it on 32bit
wind
