similar to: Upgrade to 4.8, Now I Have to Use FQDNs?

Our samba boxes are integrated with our Windows 2003 AD domain, with Windows servers acting as AD domain controllers. Everything is working fine, but in my krb.conf and krb5.conf files on my Linux boxes, I currently only have one Windows server specified as the AD logon server. If that server is down, I suspect that Linux users could not login. How to I specify more than one AD domain controller

I have two CentOS servers running samba3-3.0.34-37. When I connect to a samba share from my Windows 2003 R2 servers, and then try to copy a file to it, I often get the message "target filesystem does not support long filenames." Sometimes it works and sometimes it doesn't. I've been fighting this problem for 2 years. I've replaced my Windows servers, changed my Windows

There are three DCs in my Windows 2003 AD domain, but I have noticed that only one of them is referenced in my krb.conf and krb5.conf. Should there be a reference to one or two of the other domain controllers? If the DC goes down, how will my Samba/Winbind servers authenticate? -- Eric Robinson Disclaimer - February 27, 2011 This email and any files

We have about 40 samba servers in our domain. The two newest ones are throwing an error we've never seen before. [root at vmhost06a samba]# net join Enter root's password: dos charset 'CP850' unavailable - using ASCII convert_string_talloc: Conversion not supported. Failed to join domain: failed to lookup DC info for domain 'MYCHARTS.MD' over rpc: Memory allocation error

> I have multiple CentOS servers running a couple versions of Samba > serving various Windows versions and I've never once ever seen > this message. Glad to hear it. That's the kind of behavior I would normally expect. One thing that might be different between our environments is that my users are all in Remote Desktop sessions connected to a pair of Windows terminal servers.

I have two CentOS servers running samba3-3.0.34-37. When I connect to a samba share from my Windows 2003 R2 servers, and then try to copy a file to it, I often get the message "target filesystem does not support long filenames." Sometimes it works and sometimes it doesn't. I've been fighting this problem for 2 years. I've replaced my Windows servers, changed my Windows

We have a lot of users on our AD domain, and the more we add the longer it takes to get a directory listing on my Linux servers. When I do 'ls -l' it might take 20 seconds before the listing starts. However, if I immediately do 'ls -l' again, it comes up quickly. I assume this is because samba/winbind is polling the AD domain controller on the first attempt. Is there any way to

We have three Windows domain controllers in our AD domain. They are DC01, DC02, and DC03. We have Linux (RHEL5 and 6) servers in the domain as well. The Linux servers are working fine with AD. However, they are currently configured in krb.conf and krb5.conf to use only DC01 for AD domain controller. if DC01 is down, Linux servers cannot authenticate. How do we configure the Linux servers to use

Attempting to install a fully virtualized instance of Windows 2003 fails on CentOS 5.2 x86_64 with xen-3.0.3-64.el5. After issuing the command... # virt-install --hvm -s 70 -f /vm/ts05/ts05.dsk -n ts05 --cdrom /download/Win2003x64/disk1.iso --vnc -r 1024 The script just hangs at... Creating domain... In another terminal window, I can see that vnc-viewer has been started and is

Hello, I stumbled upon weird error/bug. My setup: 4.8.3 AD on centos 7.5 (compiled from source). BIND as dns running on AD DC with secure dns updates setup and working. Most of the DNS updates are dynamic, some added manually using windows DNS manager. One of the PTR entries in reverse lookup zone went missing. It's not visible in the windows DNS manager, it's nowhere to be found

Hello friends and fellow R users, I have a problem to which I have been unable to find a solution: I am gathering survival data on patients undergoing treatment with a new kind of stent. I want to generate survival data and plot survival curves of these patients based (among other things) on the treating physician. My data set has been tabulated in the following manner: Date (the date the stent

Hi group, My case has N physicians with each seeing M patients. One physician could have seen a group of patients, or, a patient could have been seen by multiple number of physicians. In order words, there are overlaps. Now, I have the following NxM matrix Patient#1 Patient#2 Patient#3 ....... Patient#m Physician#1 1 0 1 ....... 0 Physician#2

On Mon, 10 Jul 2017 11:45:31 +0200 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > > (new thread, same migration project) > > I see GPOs applied, but network drives sometimes mapped, sometimes > not. > > Found something around hardened UNC paths, applied some GPO, dunno if > that is necessary or helps (I still have to check where to

On Tue, 11 Jul 2017 11:59:24 +0200 "Stefan G. Weichinger" <lists at xunil.at> wrote: > Am 2017-07-11 um 11:43 schrieb Rowland Penny: > > On Tue, 11 Jul 2017 10:21:37 +0200 > > "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > > > >> Am 2017-07-11 um 09:34 schrieb Stefan G. Weichinger via samba: > >> >

Am 2017-07-11 um 12:16 schrieb Rowland Penny: > Try running this: > > ldbsearch -H /path/to/sam.ldb -b "dc=secret,dc=at" -s sub > "(&(objectclass=user)(uidnumber=11029))" > > This will check if it is a user. Did so, no entry returned. -- plus: please note that yesterday all users could work normally .... > Can you post the smb.conf from the DM

Am 2017-07-11 um 12:51 schrieb Rowland Penny: > Well, that explains where '11029' is coming from, you are using the > 'rid' backend. The users (or group) ID will be calculated using this > formula: > > ID = RID - BASE_RID + LOW_RANGE_ID > > BASE_RID is by default '0', so it becomes: > > ID = RID + LOW_RANGE_ID > > So, in your case it

On Tue, 11 Jul 2017 14:19:09 +0200 "Stefan G. Weichinger" <lists at xunil.at> wrote: > Am 2017-07-11 um 14:00 schrieb Rowland Penny: > > >> template homedir = /home/%U > >> > >> works for me in this context, right? > > > > That should work. > > edited accordingly, and rm-ed that idmap schema line on DM. > > I now have on

On Tue, 11 Jul 2017 14:47:50 +0200 "Stefan G. Weichinger" <lists at xunil.at> wrote: > Am 2017-07-11 um 14:40 schrieb Rowland Penny: > > >> Restarted winbind, did "killall -HUP" on smbd and nmbd. > >> > >> still can't login to DM via smbclient and that mentioned user. > >> > >> I assume I need to restart all the

On Tue, 11 Jul 2017 16:47:14 +0200 "Stefan G. Weichinger" <lists at xunil.at> wrote: > Am 2017-07-11 um 14:57 schrieb Rowland Penny: > > On Tue, 11 Jul 2017 14:47:50 +0200 > > "Stefan G. Weichinger" <lists at xunil.at> wrote: > > > >> Am 2017-07-11 um 14:40 schrieb Rowland Penny: > >> > >>>> Restarted winbind,

On Tue, 11 Jul 2017 17:33:51 +0200 "Stefan G. Weichinger" <lists at xunil.at> wrote: > Am 2017-07-11 um 14:57 schrieb Rowland Penny: > > >> # smbclient \\\\server\\daten -Usgw%PW > >> session setup failed: NT_STATUS_UNSUCCESSFUL > > > > Restart all the Samba binaries on the DM > > > > Then check that the OS knows your user with: