similar to: Windows 7 Pro/64 unable to contact domain controller

Hi Louis, I tried restarting samba on the server already. I also tried rebooting the client pc a number of times. The folders are mounted via GPO's. I assume rebooting the pc should have the same effect as remounting the shares? I also had a look at the permissions from Windows. When I look at the permissions of the new folder I managed to create I see there is a strange user with only

Hello List, Im running an network with five samba 4 addc, all on debian wheezy with the sernet packages. Recently an replication error showed up for an single Computer (WIN7-M-ADMIN) record. So I unjoined the pc from the domain deleted it's record from dc1 manually on the other dc's it had been removed automaticaly during unjoin. Now I get the following error [2015/07/21

Please forgive any stupidity in the following question. The admin who maintained samba left recently and we (a bunch of programmers) are trying to fix it. We had a Solaris box called svr2, it provided samba and nfs services. We bought a new computer called originally newsvr2. We ported the samba settings across to newsvr2 - everything worked. We swapped the hostname and IP addresses of svr2 and

Thanks Louis, it seems the DNS updates were working even with the nsswitch.conf I had, but only for machines that I manually joined to the new AD Domain. I checked the ones I didn't join manually and they aren't proper members of the domain anymore. If I try to logon with anything but the last (cached) user account on a Win7 machine I get: "The trust relationship between this

Hello everybody. since this morning I've got a massive problem. My fileserver (Debian wheezy, Samba 3, everything up-to-date) is an ADS member server and was running flawlessly for two weeks. Since a few days I began to move users to this server from an old one, and since this morning nothing works anymore. The symptoms are: User get "wrong password" when trying to mount

On Fri, 21 Apr 2017 12:00:59 -0400 Eleuterio Contracampo via samba <samba at lists.samba.org> wrote: > [2017/04/21 12:47:55.219297, 0] > ../auth/gensec/gensec.c:257(gensec_verify_dcerpc_auth_level) > > Did not manage to negotiate mandetory feature SIGN for dcerpc > auth_level 6 > I think you may be running into an artefact of the badlock patches, for which Win7 will

I have a storage server running samba 3.6.6 on Debian. Unfortunately I cannot easily upgrade samba as this is a production server. The server is a member of a Samba-based domain, unix users are still handled by NIS. When I logon to a Windows 7 pc (also part of the domain) with my own user my homedirectory is automatically available as H:\. I can see the content of the directory but when I try to

Hello again List, Marc, and Louis! I'm afraid my message from yesterday may have been TL;DR. The short version is as follows: Following the wiki's for AD member server (building from source on Debian Wheezy) and Setting up shares with Windows acls did not give the expected results First, I needed to link libnss_winbind.so to /usr/lib/x86_64-linux-gnu for winbind to work. Marc - may I

After upgrading Win7 and W2K8 R2 clients to service pack 1 it is no longer possible to log in to domain(before the upgrade the clients can log in into domain). Clean installation of Win7/W2K8 R2 with integrated sp1 has the same effect. Our domain PDC is running on samba 3.3.7. I'm curious if anyone else has seen this already. Thank you Mikhail Zuskov

Hai, ? Just a tip for the people reading the list. ? if you see Failed DNS update - NT_STATUS_IO_TIMEOUT? or messages : ?RPC unavailable if you connect from windows client to the samba AD DC server ? Read this. ? I have a "test' AD DC on a XEN server running and this DC does nothing. 1 pc ( win7) is joined, some dns recored are set, nothing special.. ? today i checked the logs, and

Just a follow-up. Still, no resolution. I've tried different combinations with "client ipc signing" without luck. A traffic dump shows the problem as: i) windows XP client sends a DCE/RPC SAMR command GetDomPwInfo ii) samba DC responds with DCE/RPC Fault nca_proto_error I've also tried fiddling with Local Security Policy registry values at the Win XP machine, but got nothing

Hello List! I have a Samba AD domain with two virtualized DC's running 4.1.15 and 4.1.17. I have had two member file servers with odd permissions problems that I've now given up on, and decided to start fresh. I have created a File server (FS3) with Debian wheezy, built samba 4.1.17 from source, with configure options of : --with-ads --with-shared-modules=idmap_ad ... and placed the

Hello all, Sorry about the top-posting. I have added the bit about the linking (YAY!, I'm helping!). Now if we can clear up the ACL issue, this will be a great day! Summary: To edit ACL's from Windows on a Debian Member server, we need to either 1) map the domain admin to root OR 2) give explicit permissions to Domain Admins with a chmod 0755 and chgrp "MYDOM\Domain Admins"

Rowland, you are correct. I remember now. When we started using XenServer, Wheezy would not work under it. This is a Squeeze installation, not Wheezy. Will Samba no longer work with Squeeze? If so it may be an excuse to upgrade the domain after all these years. On 06/05/2015 11:23 AM, Rowland Penny wrote: > On 05/06/15 16:07, Ryan Ashley wrote: >> I noticed something different on the

Out of the blue, after working flawlessly for years, I suddenly cannot log on to my samba 3.5.6 domain with one particular Win7 Pro workstation. Nothing has apparently changed - Win7 updates applied recently, but I was able to successfully log on after that. Nothing has changed on the DC. Error message is that the trust relationship between the workstation and the primary domain failed. I'm

I am running Samba 3.0.7 on Gentoo Linux. The server is configured for domain logins and roaming profiles, and there are about 40 Windows XP Pro SP2 clients that login to the domain. This has been setup and working perfectly since October, until this morning. Now, anytime a client tries to login, they get this error: "windows cannot connect to the domain, either because the domain

Hi Rowland, Chown to Administrator seems less flexible than Chgrp to Domain Admins on the face of it. You could add/remove users from the Domain Admins group, which allows/denies them the ability to change the permissions on the share. By changing the owner to Administrator, only those credentials would have that ability, no? What advantages do you predict with the change owner approach? What

Hi! We want to replace an old Win2000 Server (PDC). As we've already some Samba4 AD-Controllers up and running we would like to migrate to that setup. Unfortunatly we're not really good at Windows-Stuff - our main Focus ist Linux. So perhaps someone could point as to a good (and ideally painless :-)) way to migrate. So the current setup is: A single Win2000 PDC used mainly as

Louis, 4.2.2 (git clone method for 4-2-stable branch) is what I am running. I will NOT be using Debian 8 due to systemd. If I have to do this, we're going to plan a down-time for the client, zero everything, do a fresh XenServer install and install Gentoo 64bit under XS. If that is what must be done, so be it. I can do that. I'll simply have one VM on each physical server which builds the

Ok, so if i understand right, your sysvol is on a shared folder which is a debian squeeze server. i think you problem is that the needed acl cant be set on the queeze server. and why not systemd, since gentoo also does systemd https://wiki.gentoo.org/wiki/Systemd and if you really want, just run your install with preseed/late_command="in-target apt-get install -y sysvinit-core"