similar to: Samba 3 PDC > 3.3.4 broken with Win 7 RTM

Hi, I am running Samba 3.2.4 on a Solaris 10 SPARC machine. The config is pretty simple (see below). Security is set to 'domain'. The PDC and BDC are running 3.0.30 without problems. When joining the machine to the domain with 'net rpc join', it fails with: Could not connect to server 130.37.79.2 Connection failed: NT_STATUS_INVALID_PARAMETER when running the net command

Hello list! I'm trying to debug a problem that surfaced after a Samba upgrade from v3.5.x to v4.1.17. The problem is that Win7 workstations appear to randomly experience domain trust issues logging in, although they can log in some times, they are unsuccessful at other times. I cannot so far predict what would result in or influence this behaviour. These are workstations on which

Okay, here's another wrinkle: if I run 'net rpc testjoin' immediately after joining, it succeeds, but 'net rpc info' fails (see below for the -d10 output). 'net rpc testjoin' fails as described in my last message after a reboot. Looking at the output from the failures, I notice that 'net rpc' is looking for SRV records at '_ldap._tcp.pdc._msdcs.DOMAIN'

With samba 4 <-> win7 (* or win8-10) trust issues. Then you have a few things to check Start with checking if your time is in sync. Check the windows even log, for errors, look them up. If its a "bootcamp-ed" windows 7 install ( aka on a imac ), boot in apple, update bootcamp. Last, if you used an imaged windows 7, did you forgot to sysprep maybe? And correct, samba 3.x was

Hello Is there any hope one day a Samba PDC will work with NetAPP filer ??? I mean will it be possible to register a filer as a machine in a Samba PDC ? I fails since years and I never had any clear explainations about it. Couls someone ( Mr Bartlett ? ) tell me why it had never be possible ? Thanks a lot.

Hello, we are currently in the process of migrating Windows machines to Ubuntu 10.04. For now, these machines act as samba clients in a Windows domain (which is controlled also by a samba PDC), and are itself sharing files via SMB/CIFS. The clients are - from time to time and with no apparent reason - losing their domain membership. When this happens, access to shares on the PDC still seems to

Hi List! We've run into interesting problem with Samba and Vista. In short - there's a Samba server sharing NFS connection. What is shared is the NFS link mounted somewhere in root (say /nfspath) and [homes] which is in fact /nfspath/some/dir. And the problem is that Vista client can write a file onto the share using \\sambaserver\homes\dir notation, but cannot do it using

I am running Win2K (RTM build 2195) and ever since RC2 I have had problems copying files from my Win2K machine to my RedHat 6.1 Linux (stock kernel 2.2.12-20) box. The Linux box is running Samba 2.0.6. I either get: J:\mail\archive\todo\dingo>copy dmail-122499 \\alder\mikenel Access is denied. Or I get a file with a funny character created on the box: [...] -rwxr--r-- 1 mikenel mikenel

X86: expose HLE/RTM features to dom0 Intel recently release 2 new features, HLE and TRM. Refer to http://software.intel.com/file/41417. This patch expose them to dom0. Signed-off-by: Liu, Jinsong <jinsong.liu@intel.com> diff -r 92e03310878f xen/arch/x86/traps.c --- a/xen/arch/x86/traps.c Wed Feb 08 21:05:52 2012 +0800 +++ b/xen/arch/x86/traps.c Mon Feb 27 02:23:42 2012 +0800 @@ -857,9

Hi there, I have just purchased a new PC that came with Windows 8 Pro (Shudder...). I have been trying to add this machine to my Samba3 based domain. I'm getting the following error when doing so: The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "<blah>":

I'm sorry for the very long debug pasted below but I'm afraid lower debug levels would not give enough useful information about the problem. I've been investigating it for over two weeks with no result. Maybe developers can tell me where to search for the cause - browsing source code is very hard... I have a Samba PDC with LDAP backend. Configuration works fine on 3.0.x version but

Hi List, i'm trying to join a Windows 2000 SP4 Domain (Native mode). I'm getting the following error while joining: # net ads join -U 'Administrator%password' Using short domain name -- W2K Could not connect to server dc.w2k.bitebene.org Connection failed: NT_STATUS_NOLOGON_WORKSTATION_TRUST_ACCOUNT Failed to verify membership in domain:

Hi all, When moving between Samba 3.0.X revisions, I have been able to copy the secrets.tdb file and the trust relationships with foreign domains remain established. However, this does not appear to work when moving directly from 3.0.X to the 3.3.X branch. Is there a tool available that allows us to migrate - or can tdbdump (or similar) be used to dump out data from the 3.0.X format and then be

Listmates, On my Archlinux server with samba 3.3.4-1, I am getting a smbd error that is filling my logs and I'm not sure why. The box 'ripper.3111skyline.com' shown below is a dual boot box and spends most of its life and mom's XP box and masquerades as an openSuSE 10.3 box the rest of the time. There are seven other boxes on this lan with 5 others being dual boot XP/openSuSE

Guys, After upgrade to samba 3.3.4 on openSuSE 10.3, I'm getting: Jul 10 02:05:14 bonza smbd[31942]: [2009/07/10 02:05:14, 0] lib/util_sock.c:write_data(1136) Jul 10 02:05:14 bonza smbd[31942]: [2009/07/10 02:05:14, 0] lib/util_sock.c:get_peer_addr_internal(1676) Jul 10 02:05:14 bonza smbd[31942]: getpeername failed. Error was Transport endpoint is not connected Jul 10 02:05:14 bonza

Hi, I'm using Samba (currently samba-3.0.10-1.fc3) in an intranet environment under Fedora Core 3. I learned that I have to upgrade to Samba 3.3.4 or higher in order to join new Windows 7 clients to the domain. Hints to binaries for this setting would be greatly appreciated. Cheers, Jo

Greetings, all. I have a Samba 3.3.4 PDC up and running on my small home network, having migrated from an older 2.2.8 configuration. My XP Pro and Vista clients have remained as members of this migrated domain, logging with no problem. Client logins have worked precisely as expected. All seems to be happy - with one exception. My only problem, which I've spent the last two or three days

Hi, When I compile samba 3.3.4, I have this error : Using FLAGS = -O -O -D_SAMBA_BUILD_=3 -I/usr/local/include -I/root/samba-3.3.4/source/iniparser/src -Iinclude -I./include -I. -I. -I./lib/replace -I./lib/talloc -I./lib/tdb/include -I./libaddns -I./librpc -DHAVE_CONFIG_H -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -I/usr/local/include -Iinclude -I./include -I. -I.

Hi, Just trying to get a SLES10 machine running 3.3.4 to join a 2008 domain and getting this .... any ideas?? Running: net -d 3 -U admuser@DOM.REALM.CO.COM ads join createcomputer="REG/CN/OU/Services/" Error: [2009/05/15 13:42:13, 3] libads/sasl.c:ads_sasl_spnego_bind(780) ads_sasl_spnego_bind: got OID=1 3 6 1 4 1 311 2 2 10 [2009/05/15 13:42:13, 3]

Hi, I just upgraded from 3.0.32 to 3.3.4 on Aix 6.1, and noticed that a 'net view' command from a windows xp workstation fails with a system error 1745. The share works perfectly fine, just the net view command doesn't. This occurs when there is an umlaut in the comment line of the share. Is this WAD? here are the debug lines...from Samba 3.3.3, but it's the same error. Thanks,