similar to: big share problem

On 25/11/2019 18:12, Tom via samba wrote: > Hi, > > I've a big problem with my shares on a domain AD member server. > > On this server there is severals shares directories : > > - \data\dir1 [share_one] > - \data\dir2 [share_two] > - \data\dir3 [share_three] > > \data is a mounted partition > > when I browse one of my share in windows,

(resend 3 !) Am 27.11.19 um 14:28 schrieb L.P.H. van Belle via samba: > Hai, > > DM, right.. > > (short version) > Just install/setup a the new DM. Add it to the domain. > Transfer all data and correct rights where needed. can't: data is on SAN ... will get "plugged in" via FibreChannel tmrw > Test it, all ok, poweroff the old server, > Remove the

Hello at all after a classicupgrade from samba 3.6 to samba 4.9.1 at first tests i found many error in log.smbd like these : [2018/10/31 15:26:51.317398,  0] ../source3/smbd/uid.c:386(change_to_user_internal)   change_to_user_internal: chdir_current_service() failed! [2018/10/31 15:26:51.317567,  0] ../source3/smbd/process.c:1627(switch_message)   Error: Could not change to user. Removing

Hi, I am trying to address some error messages that are hitting the log files for two 4.9.5-Debian file servers in our all-Samba AD domain. Most prominently "connect to service Profiles initially as user MYDOMAIN\tc-mj00y2ps$ (uid=11128, gid=10515) (pid 1634)" "../source3/smbd/uid.c:453(change_to_user_internal)" "change_to_user_internal: chdir_current_service()

Hello $list, i can't access the netlogon share on the second dc. I got this error: Mai 04 22:13:53 dc02 smbd[3321]: [2020/05/04 22:13:53.035964, 0] ../../source3/smbd/uid.c:448(change_to_user_internal) Mai 04 22:13:53 dc02 smbd[3321]: change_to_user_internal: chdir_current_service() failed! Mai 04 22:13:53 dc02 smbd[3321]: [2020/05/04 22:13:53.037230, 0]

Il 31/10/2018 17:18, Rowland Penny via samba ha scritto: >> ok, this smb.conf is default from classicupgrade > I am fairly sure it isn't. ok, i did many changes and cut&paste. You are the expert !! :-) > >> i take out they >>> Do you really need an insecure auth method ? >> why ?? > You have set 'ntlm auth = yes', this allows you to use an

On Mon, 5 Nov 2018 11:51:00 +0100 Corrado Ravinetto via samba <samba at lists.samba.org> wrote: > > > Il 05/11/2018 11:41, Rowland Penny via samba ha scritto: > > You might as well remove the line 'winbind use default domain = > > Yes', it does nothing on a DC. > > I would also add 'idmap_ldb:use rfc2307 = yes' > ok, i did it > > When

On Mon, Aug 29, 2016 at 6:13 PM, Jeremy Allison <jra at samba.org> wrote: > On Mon, Aug 29, 2016 at 11:41:53AM -0400, Jeff Hodge via samba wrote: > > During an ubuntu 14.04 update samba was updated from 4.1.6 to 4.3.9. We > > had no problems with any windows system accessing the server prior to the > > upgrade to 4.3.9. It seems to affect access to the entire samba

I just had something very strange happening, I'm curious if someone can understand what it was in spite of the limited available information. I'm running Samba 4.11.6 as an AD file server. Rowland checked my config recently and could not find any issue with it, it's really very standard, using the idmap backend. Only 2 users in the AD. Linux access is not a topic, the shares are only

Am 25.11.19 um 19:12 schrieb Tom via samba: > > socket options = TCP_NODELAY TCP_KEEPIDLE=240 TCP_KEEPCNT=4 > TCP_KEEPINTVL=15 This is the next thing you should remove. The kernel is handling everything with sockets and performance. By setting this parameter the kernel can't set the optimal settings. The parameter "store dos attributes is default depending of your samba4

I've just upgraded my DM from samba 4.5 to 4.8, using luois repos (also, debian jessie -> stretch). I'm experimenting some troubles on some shares, seems that both guest access and 'machine account' access does not work. The share is rather simple: [wpkg] browseable = No comment = WPKG Automated Software Deploying System force create mode = 0664 force directory mode =

Hello, I installed a fresh opensuse Tumbleweed with samba 4.8.2+git.30.690aa93c189-2.2. smb.conf looks as follows: [global]         server string = host12         workgroup = WORKGROUP         ; speed optimierungen         socket options = TCP_NODELAY         debug level = 10         getwd cache = yes         preserve case = yes         bind interfaces only = yes         interfaces = br0

Samba version : 3.6.3 Filesystem : BTRFS Clients : XP, Win7 Log Level : 5 When we start our samba server everything works fine. After a few days, some of our users are not allowed to connect to shares anymore. When we restart the clients they can connect for a short time and then say have the same problem again. When we restart the server everything works fine for a few days again.

Hello, I'm having a permissions problem I just can't quite figure out. I can not access any directory that is owned by my userid if the permissions are 700. If I change them to 770, with my default group on the directory, then I can access the directory. This was working fine with Fedora 19 for several years, and it broke when I upgraded to Fedora 22, and still broken with F23. my

Hi, I'm facing to an issue where I cannot find solution. Here is the test case : * Samba 4.7, multi-server setup (multiple DC) * Windows 7 and Windows 10 client (not domain member) * Shares can be listed but no access to them in some case >From my workstation if I access to \\myserver.domain\myshare I get an error like "//UNC// is not accessible . you might

If DNS is setup correct, then and your sure, then show ipconfig /all from a working and failing pc. And for i forget to mention. Did you check if the time is in sync? ( sorry must ask ) Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Gaetan SLONGO via samba > Verzonden: dinsdag 29 augustus 2017 11:47 > Aan:

Hello, First of all : Happy New Year to you all :-) I need your help for a problem. I've 2 servers on CentOS 7: a Samba DC+AD and a Samba Files Sharing. In the Samba file sharing server, all data is store in a RAID Disk partition wich is mounted in /data/ (fstab : UUID=a47ea879-7072-4e8f-a668-3f5a86e58ef2 /data ext4 defaults,user_xattr,acl,barrier=1?? ?1 2). Under Windows each user has

>> After mapping the Administrator of the domain, as root on unix, the >> Administrator lost access to sharing the fileserver. When trying to >> access the system asked for authentication but does not authenticate. >> When I comment the following line in smb.conf, the share opens >> normally: >> >> username map = /etc/samba/user.map >> >

Ok increased logging and got the error here is what got logged: 2020/04/23 14:03:17.514132, 3] ../../source3/smbd/smb2_server.c:3274(smbd_smb2_request_error_ex) smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1] status[NT_STATUS_SHARING_VIOLATION] || at ../../source3/smbd/smb2_create.c:334 [2020/04/23 14:03:17.514206, 3]

Same here, I had also wrote to the mailing list, 2 Customers has the same issue after upgrading to 4.12 Windows Clients get the error ?another prosscess is in use? or ?wrong handle? when a user try to open a network share. After restart samba it?s working for a little moment but mostly not. We?re using Debian 10 Buster and Samba Version is: Version 4.12.1-SerNet-Debian-5.buster Von: samba