similar to: Samba4 Problem Rename

PDS is a typo - sorry! Should be PDC (primary domain controller) And thank you for your hints - I'll try them and will report results Regards Bernhard On Sun, 12 Feb 2017 13:32:32 +0100 Bernhard Blasen via samba <samba at lists.samba.org> wrote: > I've got a Problem using samba4 as PDS and Win7 Client. What is a 'PDS' ?? > > I'm not able to rename a file in

Thank you Rowland, your post was very helpful. In one of your links I found "Do not use the same user names in the local /etc/passwd file as in the domain" and this statement did the trick. In Samba3 I had the same usernames for linux users and for samba users. But now in Samba4 acting as an AD PDC you obviously need different usernames. Cheers Bernhard >On Sun, 12 Feb 2017

I have some identical windows 7 clients. All connected to Samba 3.5.4-1.1-2382-SUSE-SL11.0. If I'm the windows-owner of the file, swat shows me under "oplock" "exclusive+batch". Other users get: "none". What is the reason for this? ___________________________________________________________ Neu: WEB.DE De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt

I having difficulty getting browsing to fully work across two subnets. The subnets (having private addresses - 192.168.x.0) are connected by Linux boxes (RH6.1, one for each subnet) functioning as firewall, IP masquerade and router. On one subnet (call this one LEFT), there is an NT4.0 server as the PDC (also running WINS and DHCP) along with 50 or so clients and other servers (NT, Win9x) in

Hi, i upgrade to sles sp1 with sernet packages and get the following error after upgrade. Its looks like that port 135 will not reached. Anyone who have an information about that or a solution? Thanks Sven orion:~ # samba-tool drs showrepl Failed to connect host 192.168.24.2 on port 135 - NT_STATUS_CONNECTION_REFUSED Failed to connect host 192.168.24.2 (orion.domain.local) on port 135 -

Hi, I can't answer in a way it appears in the thread, sorry ... Examining the backtrace and these innermost frames: #0 smbd(log_stack_trace+0x1c) [0x5555557586cc] #1 smbd(smb_panic+0x43) [0x5555557587b3] #2 smbd [0x555555746b82] #3 /lib64/libpthread.so.0 [0x2aaaac259de0] #4 /lib64/libc.so.6(strlen+0x30) [0x2aaaad3c9510] #5 /lib64/libc.so.6(__strdup+0x16) [0x2aaaad3c9246]

Hello, I've set up Samba 3.0.22 on an Ubuntu box for testing purposes. Below is my smb.conf file. The Samba server, ubuntu, is on the other side of a Linksys WRTP54G router, serving NAT to my Windows XP clients on the inside. I've opened port 139 on the router, set up NetBEUI, placed entries in the clients' hosts & lmhosts files. For some reason, the clients can logon to

Hello. I have a Problem with creating a GPO on Samba. Each time I try to create a new one, it shows "The security id may not be assigned as the owner of this object". I've already checked the sysvol-folder and it seems to have the correct permissions. I also checked the Account-Permissions (I'm the build-in Administrator, when trying this) and I also checked the connection

John, The restrictanonymous setting was the primary culprit in Ash's issue. I think he's using basically the same setup as I am; no winbind/LDAP involved. I'm thinking there's some initial handshaking that requires an anonymous connection to PDC, and it's being blocked if the restrictanonymous setting is too high. I sent a note to Ash (& the list) asking for the

Hi, I've got a big problem since my new samba servers are in 3.0.23c version, no problems before. The server is only a file server and domain member in a Win2K Active Directory domain (4 replicated DC, 1 domain, no forest). My problem: Anytime I try to connect a share through any kind of client (MacOS cifs client, smbclient, windows win2K pro, ...) the client can't mount the

Hello. I have set up a new samba server here at work, and for most things it is working great -- but there is yet one major issue. It works fine for Windows and Dave clients, but the problem arises when I use smbmount. It is set up as a domain member of an ADS domain. For example, I have a public share that everyone in the office should be able to access, regardless of platform or even

Samba 3.0.1 on Mandrake 9.1ish Kerberos version seems to match latest stable MIT build. I can log in via Kerberos authentication and/or winbind. A couple of problems though. 1) telnet with the domain username and password and the telnet session doesn?t reader /etc/bashrc. Telnet with local username and it does. bash is the shell for both accounts. 2) The group account is ?Domain

Dear All I'm about migrating Samba 2.2.8 to 3.0.13 on Sparc, Solaris 8. Compilation and Installation without any problem. Runs fine with exception of 2.2.8-user validation in the domain (no problems with validation of WXP- and W2K-Client Machines, newly set users (./smbpasswd -a username) works perfectly ). I simply have copied smbpasswd 2.2.8 to the diferent directory of Samba 3.0.13.

Hi all, I got a problem while trying to set up a Samba 3.4 Server in hybrid-mode. After trying for some time I managed doing a merged-build of Samba3 and Samba4 and I can now start samba4 without getting errors. However, the same is not true for Samba3: starting it, I get the below error message. Has anyone an idea about what the reason could be? Did I miss anything during build/setup?

I'm running Suse 9.2 (kernel 2.6.8-24) with Samba 3.0.20b When I use security=user, my read/write performance is less than half the peformance with security=share. Why? There are no other changes, but performance is never better than half the speed. This happens with WinXP, Win2K and Win98 clients, so I don't think the client configuration is the problem. Network is gigabit, with

Hello everyone, I am a newbie to samba. I am trying to mount a Windows 2000 share directory on my linux box using smbmount. I am able to do so successfully. But I do see some errors pop up when I run the command. My mount seems to be stable and it is mounted as rw. # smbmount "//EngineerWKS85/My Drivers" /mnt/samba -o username=MyUsername,password=MyPassword,workgroup=MyWorkgroup

Hi I'm New comer in Samba I get a problem when try connecting from linux RH 7.2 to WIN NT using samba 2.2.1a. I try to share from /home/sudin in myhost RH I Used configuration in smb.conf workgroup = myworkgroup server string = my comment [sudin] comment = my sharing dir path = /home/sudin valid users = sudin public = no writable = yes create mask = 0765 from konsole I try to activate

The pds_core_logical_qtype enum and IFNAMSIZ are not needed in the common PDS header, only needed when working with the adminq, so move them to the adminq header. Note: This patch might conflict with pds_vfio patches that are in review, depending on which patchset gets pulled first. Signed-off-by: Shannon Nelson <shannon.nelson at amd.com> --- include/linux/pds/pds_adminq.h | 21

debugfs.h protects itself from an undefined DEBUG_FS, so it is not necessary to check it in the driver code or the Makefile. The driver code had been updated for this, but the Makefile had missed the update. Link: https://lore.kernel.org/linux-next/fec68c3c-8249-7af4-5390-0495386a76f9 at infradead.org/ Fixes: a16291b5bcbb ("pds_vdpa: Add new vDPA driver for AMD/Pensando DSC")

v2 for internal review - heavily reworked NET_F_MAC patch, matches recent PR-68875 - reordered to put "clean and reset vqs" before "alloc-irq" to make them slightly simpler patches - other minor cleanups for simpler patches These are some fixes for device providing a MAC address, for allocating irq resources later to support vhost use, and for properly cleaning vq info