similar to: smbclient & server list

1. First of all, source/include/includes.h file contains wrong refence to file popt.h. In supposed to be "popt/popt.h" instead of "popt.h". After this correction source compiles OK. 2.After the installation on new alpha19 (I used alpha17 before) swat stopped authenticating (I use same credentials for Samba 2.2.5 and samba 3 swat). 3. Samba-3 shares are accessible through

Hi there, I have searched the rsync website, as well as an extensive search on google, but have been unable to come up with a definitive answer regarding whether rsync will synchronise files and directories which have Japanese characters in them. I am using an English language version of Linux, which has some directories shared via samba. Both English and Japanese language windows clients

Has anyone added windows 2000 computers to Samba3.0a20 PDC, I have been trying to do that and I always get "Incorrect Parameter" message on windows 2000 client, the same problem occured with alpha19, but joining alpha18 PDC used to work fine with me. Any suggestions? My smb.conf file [global] workgroup = ZSQUID netbios name = hsalin server string = Samba

Hi, I'm using SAMBA 3.0 alpha19 to try the trust relationship between an NT 4.0 domain and the samba domain. The command I used was "net rpc trusdom", but it did'nt work, also the other "net" commands worked bad ( Segmentation Fault or return -1 ecc.). Could you kindly to tell me how to do to set the trust relationship with the SAMBA 3.0, or if there is any docs for

Hi I try to compile samba-3.0-alpha19 on my Linux-Box (SuSE 8.0, Kernel 2.4.18, cc 2.95.3, make 3.79.1). After "make" I got this errors: Linking bin/smbd /usr/src/krb5-1.2.5/src/lib/libgssapi_krb5.a(accept_sec_context.o): In function `rd_and_store_for_creds': accept_sec_context.o(.text+0x7b): undefined reference to `krb5_rd_cred' accept_sec_context.o(.text+0xdb): undefined

i'm trying to get samba 3.0 alpha 19 runing on OS X 10.2 working as a PDC with Win XP clients using an LDAP passdb backend i've managed to get it so i can connect to shares with smbclient but whenever i try to join one of the XP machine to the domain Windows tells give me the message "the specified network name no longer exists". when i check the logfile the last thing in it is

Hi all, To start I am still very new to samba and this is my first attempt to build RPMS from the CVS source. I am trying to use the script you have in /packaging/Redhat. I keep getting an error that samba-PVERSION cant be found, see below: [root@LSALNXS01 RedHat]# pwd /usr/src/samba/packaging/RedHat [root@LSALNXS01 RedHat]# sh makerpms.sh chown: getting attributes of `samba-PVERSION': No

We are proud to a announce another alpha release of Samba 4.0, alpha 20 THIS IS A SECURITY RELEASE for CVE-2012-2111, which impacts on users running the smbd file server from Samba4 alpha releases, but not users running the AD Domain Controller. What's new in Samba 4 alpha20 ============================= Samba 4.0 will be the next version of the Samba suite and incorporates all the

Hello, I am using samba-3.0alpha21 on a out of the box debian-3.0 box trying to join a native windows 2000 (active directory) domain. I have used alpha18,19,and 20 in the past with alot of success on red hat and linux from scratch systems with minimum challenges. However I cannot seem join the domain in this instance. I am using openldap 2.1.8 and mit kerberos 1.2.7. The result of "net ads

---------- Original Message ---------------------------------- From: "Errol Neal" <eneal@bnbtv.com> Reply-To: <eneal@bnbtv.com> Date: Fri, 29 Nov 2002 17:13:39 -0800 Hello, In my further investigation, it seems that winbindd cannot locate my kerberos ticket. Or, at least this is what this log output from winbindd >[2002/11/29 07:04:17, 1]

We are proud to a announce another alpha release of Samba 4.0, alpha 19 THIS IS A SECURITY RELEASE for CVE-2012-1182, which impacted on Samba4 as well. What's new in Samba 4 alpha19 ============================= Samba 4.0 will be the next version of the Samba suite and incorporates all the technology found in both the Samba4 alpha series and the stable 3.x series. The primary additional

Hi all, we've been running a Samba4 domain with alpha17 for a few months now without any problems. However, a few days ago, something happened and now winbind can't authenticate against the domain any more. Strangely, logging into (at least one) Windows box still works, even with a user that was never used on this particular box before, and therefore can't have any cached

Hello everyone I have a quite weird problem, and I've try a lot of possibility without any success. It's about file transfert beetween a Windows 2000/98/ME and a Samba PDC. I've made some tests with a Win 2K PDC too. Oh yes, English isn't my native language, so please excuse me in advance for my *bad* english. I'll try to be the most complete I can, so this post may be a

I'm running samba 2.2.3a-6 under Debian (testing) and I am having a heck of a time getting Windows 2000 to print to my printer. I keep getting that "Access denied, unable to connect" message. At one point I had it so you could print test pages, but as soon as you tried to print from an application, it would break. However, that doesn't even work anymore. I've been reading

Hi, My apologies if this is a FAQ that I missed. This is my first attempt at setting up samba4. Following the howto instructions: kinit administrator seems to work fine. samba is latest git (alpha19). however the join fails (as below): [root at ads bin]# ./samba-tool domain join tribalnova.local DC -Uadministrator --realm=tribalnova.local -d4 GENSEC backend 'gssapi_spnego'

Hi Mathias and all. Am Donnerstag, 24. März 2016, 13:26:12 CEST schrieb mathias dufresne: > Hi, > > I'm glad that helped you : ) > > About SPN, I found that link few days ago: > https://adsecurity.org/?page_id=183 > It tries to list the string values available usable for SPN. > > And it gives also that link: >

I'm not an expert, especially when it comes to servicePrincipalName which I haven't understood until now but I think it is safe to give an object the right to modify itself. If securing is one of your main concern, you could try to remove the possibility to that account to modify itself, once the servicePrincipalName is created. Doing that SPN should NOT be removed (no right to remove it)