similar to: windows 2003 sp1 clients, security = server and use spnego

I was just playing with git 1.5.3.8 and btrfs 0.11, and I noticed something odd. If I prepare a very simple repository: $ mkdir foo $ cd foo $ git init Initialized empty Git repository in .git/ $ echo hi > blort $ git add . $ git commit -m create Created initial commit 4ae9415: create 1 files changed, 1 insertions(+), 0 deletions(-) create mode 100644 blort and then

When I made the move to 3.0, I noticed that smbclient no longer works with null passwords. Am I missing something? I read the FAQ, which suggests that the server is rejecting the null password. But I know that null passwords work fine for the 2.2.8a client, so the server is not the issue. The FAQ recommends "smbclient -L host -U%", but I don't want to set the username to null. I

When I made the move to 3.0, I noticed that smbclient no longer works with null passwords. Am I missing something? I read the FAQ, which suggests that the server is rejecting the null password. But I know that null passwords work fine for the 2.2.8a client, so the server is not the issue. The FAQ recommends "smbclient -L host -U%", but I don't want to set the username to null. I

I ran into this one as well. I had to set security = ADS and create an authorized user for winbind to use. # wbinfo -set-auth-user

Hi All, I am in no way a samba expert, but we recently joined a FC3 machine to a windows 2003 domain using ADS. Kerberos worked perfectly in both directions until we approved the windows 2003 server SP1 update. After this, we could still use wbinfo -g, wbinfo -u, wbinfo -t etc, but chowning files refused to work "invalid user". You also could not authenticate against the samba shares

[Accidentally sent to samba-technical --dave] Stubel Timo wrote: > Hello List, > > > > hope anybody can help me. We have problems with our squid porxy with userauthentication. > > > > The error is: > > authenticateNTLMHandleReply: Error validating user via NTLM. Error returned 'BH NT_STATUS_ACCESS_DENIED' > > > > We are using

Hi, Try that in smb.conf , global section Client schannel = no Server schannel = auto For me that works... Kind regards martin schreiber

Hi All, I'm running into some issues accessing a Samba server that's in turn authenticating against a Win2k3-SP1 domain controller (security=ads). I understand there were some known issues corrected in a patch, and I'm currently running 3.0.15pre2, which I understand includes that patch. (http://samba.org/~jerry/patches/post-3.0.13/winbindd_2k3sp1.patch) All was working fine

Hi, I've joined a Suse 9.1 Pro linux computer to a Windows 2003 SP1 ADS using: # kinit Administrator@DOMAIN # net ads join The computer account is created on the DC and wbinfo (-t -u -g) all work. Then I try getent passwd or getent group and nothing. This is with: #grep winbind /etc/nsswitch.conf passwd: compat winbind group: compat winbind # ps -ef | grep -E

Hi, O Wise Ones, I have a number of machines running samba on Fedora 3 as member servers of a windows domain. They authenticate with Active Directory on the Windows PDC (Windows Server 2003 as part of Small Business Server 2003) and provide file and print sharing services. All has been working perfectly for months. When I applied SP1 for Windows Server 2003, authentication stopped working.

Hi all: =20 As far as I know, win2k3 sp1 disable anonymous access by default. It = will remove user =A1=A7anonymous logon=A1=A8 from pre-windows 2000 = compatible access group. Under such circumstance, smbmount will not success because anonymous = access will be blocked. One way to solve the problem is to re-add = anonymous logon to pre-windows 2000 compatible access group. However, it = seems

Hi all This one has me baffled - leading me to beleive it could be a bug similar to https://bugzilla.samba.org/show_bug.cgi?id=2695 I am running samba 3.0.20b on debian unstable and am having problems with some users not resolving properly using winbind. wbinfo -u shows all users on the system, no problem wbinfo -a user%password works for any user getent passwd shows most but not all users

Hello : I tried to join to my active directory, i run the follow command, i read all hit into google about this and "all" howto on the google "how join a linux to a active directory"....and all possible combination of words about the last error, i found other people with the same error...but not solution. I tried into Debian (3.0.14a) and Centos(3.0.14a and 3.0.20 manual

Hi iam using 1.2.17 does any one have information meetme in realtime and store in mysql i dont see any document could some one help me is this possible ? ram -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070606/36d236c2/attachment.htm

https://bugzilla.samba.org/show_bug.cgi?id=3794 Basically spnego fails with vista and you have somehow force to downgrade to ntlmssp. To samba devels: I see the bug submitter sent 2 emails to samba-technical that went unanswered. I don't understand why, the issue is real and blocking. Maybe you have some info that there will be changes in vista final which will solve the issue

In the course of debugging my still-unsolved "smbclient tar starts throwing SMB signature errors after 750MB of data or so" error, I came across this apparent inconsistency... >From the smb.conf man page: "client use spnego (G) This variable controls controls whether samba clients will try to use Simple and Protected NEGOciation (as specified by rfc2478) with WindowsXP and

How will I disable SPNEGO in my linux pc (Fedora w/ Samba 3.0.26a version installed acting as a client)? I also don't know what settings should I change in the Linux server (Fedora). When I joined the linux server and client in windows server workgroup w/o spnego the result is there is no extended security at all. (I did this by changing smb.conf workgroup) I only want NTLMSSP(Extended

On 04/16/2015 12:53 AM, Mike wrote: > CentOS 7.1503 installed. > Installed Samba 4 from sernet: Version 4.1.17-SerNet-RedHat-11.el7 (to be > configured). > > The samba wiki Readme First page states, "Some distributions like . . . Red > Hat Enterprise Linux (and clones), ship BIND9 packages with disabled > GSS-SPNEGO option, which is required for signed DNS updates when

On Thu, Apr 16, 2015 at 6:03 PM, James Hogarth <james.hogarth at gmail.com> wrote: > This was required for kerberos secured updates prior to el7.1 and el6.6 ... > > The problem in the underlying kerberos libraries was resolved so that > kerberos based updates worked with gss again and spnego doesn't need to be > compiled in. >

On Fri, Apr 17, 2015 at 7:46 AM, James Hogarth <james.hogarth at gmail.com> wrote: > It wasn't the bind package directly but rather an issue with the libkrb5 > libraries. > > This is the specific bug that fixed the issue: > > https://bugzilla.redhat.com/show_bug.cgi?id=1087068 > > I'll get the samba wiki updated to make this clear. > Zoinks! I