-Original Message-
From: Andrew Bartlett [mailto:abart...@samba.org]
Sent: Monday, May 27, 2013 5:03 PM
To: Robinson, Eric
Cc: samba@lists.samba.org
Subject: Re: [Samba] New Samba Error We Have Not Seen Before
On Mon, 2013-05-27 at 18:32 +, Robinson, Eric wrote:
We have
-Original Message-
From: Marc Muehlfeld [mailto:sa...@marc-muehlfeld.de]
Sent: Saturday, May 25, 2013 3:31 PM
To: Robinson, Eric
Cc: samba@lists.samba.org
Subject: Re: [Samba] Linux Servers in an AD Domain with
Multiple Windows Domain Controllers
Hello Eric,
Am 25.05.2013 18
We have about 40 samba servers in our domain. The two newest ones are throwing
an error we've never seen before.
[root@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
On 27 May 2013 19:14, Robinson, Eric
eric.robin...@psmnv.commailto:eric.robin...@psmnv.com wrote:
-Original Message-
From: Marc Muehlfeld
[mailto:sa...@marc-muehlfeld.demailto:sa...@marc-muehlfeld.de]
Sent: Saturday, May 25, 2013 3:31 PM
To: Robinson, Eric
Cc: samba
Thanks, I will try that. What about krb.conf? Any changes required there?
(Sorry about the top post. Your MUA's message quoting mechanism makes it hard
to bottom post as I am normally used to doing.)
--
Eric Robinson
From: Robinson, Eric
Sent: Monday, May 27
-Original Message-
From: Marc Muehlfeld [mailto:sa...@marc-muehlfeld.de]
Sent: Monday, May 27, 2013 2:46 PM
To: Robinson, Eric
Cc: samba@lists.samba.org
Subject: Re: [Samba] New Samba Error We Have Not Seen Before
Hello Eric,
Am 27.05.2013 20:32, schrieb Robinson, Eric:
We
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
...@lists.samba.org
[mailto:samba-boun...@lists.samba.org] On Behalf Of Robinson, Eric
Sent: Wednesday, November 02, 2011 6:54 AM
To: Marcel de Reuver; samba@lists.samba.org
Subject: Re: [Samba] How to Configure Samba to Use Multiple
AD Logon Serversfor Redundancy
Our samba boxes are integrated
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
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.
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
How do I configure samba such that AD authentication still works when a
DC is down?
Do I need multiple kdc, admin_server, and kpasswd_server entries in
krb5.conf?
--
Eric Robinson
Disclaimer - March 2, 2011
This email and any files transmitted
There are three DCs in my Windows 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
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
I just read the Samba list rules and did not see anything against
offering payment for expertise, so I'm letting the list know that I need
Samba help and am willing to pay normal consulting rates. If you are
interested, please respond by direct email.
We have a number of CentOS 5.2 and 5.3
I have two CentOS 5.2 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
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
Disclaimer - May 12, 2009
This email and any files transmitted with it are confidential and intended
solely for Robinson, Eric,sa...@lists.samba.org. If you are not the named
addressee you should not disseminate, distribute, copy or alter this email. Any
views or opinions presented in this email
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
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
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
maybe you are interested in using the 3.0.34 SerNet
packages available at ftp://ftp.sernet.de/pub/samba/tested/
(as a yum repo).
Thanks for the tip, Karolin!
--
Eric Robinson
Disclaimer - February 13, 2009
This email and any files transmitted with it are confidential and intended
solely
I have samba 3.0.28 installed on several servers and winbind dies every
couple of days on all of them. The deaths appear to correlate with the
following log messages:
[2009/01/25 04:02:09, 0] lib/util.c:smb_panic(1655)
PANIC (pid 13395): internal error
[2009/01/25 04:02:09, 0]
, February 11, 2009 1:57 PM
To: samba@lists.samba.org
Cc: Robinson, Eric
Subject: Re: [Samba] 4th Submission to Samba List -- No Response Yet
On Wednesday 11 February 2009 15:52:30 Robinson, Eric wrote:
I have samba 3.0.28 installed on several servers and winbind dies
every
couple of days on all
I have samba 3.0.28 installed on several servers and winbind dies every
couple of days on all of them. The deaths appear to correlate with the
following log messages:
[2009/01/25 04:02:09, 0] lib/util.c:smb_panic(1655)
PANIC (pid 13395): internal error
[2009/01/25 04:02:09, 0]
I have samba 3.0.28 installed on several servers and winbind dies every
couple of days on all of them. The deaths appear to correlate with the
following log messages:
[2009/01/25 04:02:09, 0] lib/util.c:smb_panic(1655)
PANIC (pid 13395): internal error
[2009/01/25 04:02:09, 0]
I have samba 3.0.28 installed on several servers and winbind dies every
couple of days on all of them. The deaths appear to correlate with the
following log messages:
[2009/01/25 04:02:09, 0] lib/util.c:smb_panic(1655)
PANIC (pid 13395): internal error
[2009/01/25 04:02:09, 0]
I have samba 3.0.28 installed on several servers and winbind dies every
couple of days on all of them. The deaths appear to correlate with the
following log messages:
[2009/01/25 04:02:09, 0] lib/util.c:smb_panic(1655)
PANIC (pid 13395): internal error
[2009/01/25 04:02:09, 0]
Inotify is your best bet because otherwise you won't see files that are
created in any other way except through samba. There's lots of ways
files get added, changed, or deleted. inotify catches them all. Of
course, you have to combine it with inotifywait and a script for a full
solution.
--
Eric
When trying to create a file or folder, or sometimes even rename a file,
on a samba share (3.0.28-0.el4.9) from a Windows 2003 R2 server, I
occasionally receive an error message stating that the target filesystem
does not support long filenames. It does not always happen. Also, I have
another
solely for Robinson, Eric,sa...@lists.samba.org. If you are not the named
addressee you should not disseminate, distribute, copy or alter this email. Any
views or opinions presented in this email are solely those of the author and
might not represent those of . Warning: Although has taken
When trying to create a file or folder on a samba 3.0.28-0.el4.9 share
from a Windows 2003 R2 server, I continually receive an error message
stating that the target filesystem does not support long filenames. I
have another samba 3.0.28-0.el4.9 server where this does not happen.
What causes this?
What does 'net ads testjoin' say? Sounds like the trust is broken.
Whevever we've seen those errors, we've fixed them by remove and
rejoining the computer to the domain.
--
Eric Robinson
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Mailing List SVR
QUESTION: It looks to me as though this function is designed to
convert a string such as MYDOMAIN\user into a SID starting with S-.
No. it is to convert a SID char * string (S-1-) to a binary
SID representation. What does your smb.conf look like?
I figured that out after posting. :-)
Does anyone know how I can tell which Kerberos libraries (MIT or
Heimdal) my Samba was built with?
--
Eric Robinson
Disclaimer - November 13, 2008
This email and any files transmitted with it are confidential and intended
solely for [EMAIL PROTECTED] If you are not the named addressee you
I've been struggling for almost 2 weeks to get Samba working on two new
servers.
When I try to open a Samba share from a Windows 2003 computer, I always
get a logon challenge. I always get the following lot message
[2008/11/13 16:05:06, 3] lib/util_sid.c:string_to_sid(228)
string_to_sid: Sid
Any kernel newer than 2.6.13 has a built in API called inotify that can
alert userspace apps of changes to the filesystem. The program for doing
that is called inotify-tools. You can specify what directories you want
to watch and what events you want to watch for (create, read, write,
rename,
Slight correction. The program is called inotifywait and it is parts of
the inotify-tools package.
--
Eric Robinson
Disclaimer - November 12, 2008
This email and any files transmitted with it are confidential and intended
solely for Nelson Serafica,[EMAIL PROTECTED] If you are not the
smbstatus will give you this information.
I don't think smbstatus shows realtime filesystem activity. Beyond that,
it definitely would not show changes to the filesystem that occur from
other processes besides samba. Perhaps I misunderstood, but I thought
Nelson wanted to watch a directory for
I believe that smbstatus does show realtime file access
Even so, you have the problem of tracking filesystem changes that occur
in other ways, such as scp, ftp, rsync, or local copying.
--
Eric Robinson
Disclaimer - November 12, 2008
This email and any files transmitted with it are
Inotifywait is not a statistical tool. It produces a real-time log of
filesystem changes that includes the path to the file and the events
that were triggered (file was opened, read, changed, deleted, etc.)
--
Eric Robinson
Disclaimer - November 12, 2008
This email and any files transmitted
Problem: When I try to open a samba share from a Windows 2003 R2
computer, I get a login challenge.
When winbind and smb start up, the logs look clean except for the
following:
smbd.log
[2008/11/11 04:42:16, 3] lib/privileges.c:get_privileges(261)
get_privileges: No privileges
42 matches
Mail list logo
