Just read the mentioned article but I think this does not describe my
problem. The error described there is more like a warning message to me.
Moreover even if I define "smb ports 139" the message still appears
which it should not according to the article. Also, as mentioned, the
backup fails. Here
I tried it with "smb ports 139" to no avail. Same problem.
The backup job takes that long because the windows box first runs an
integrity check. If I just copy the file manually it takes a couple of
minutes. As already mentioned the other samba server 3.4.7 works without
any problems.
What does th
Nice try. The backup fails exactly the moment the message appears in the
log. So I would say it is something to worry about.
Has really no one any ideas why this all of a sudden comes up.
Thanks for any hints
Rob
On Tue, 2010-10-12 at 08:41 +0200, Daniel Müller wrote:
> This message only says:
I don't think this is my problem. Samba on the ReadyNas works all right,
it is fast, I can mount shares etc. No worries at all.
Only if I copy that huge file which takes abaut an hour (depending on
the network load) or so the error pops up and the backup fails.
The ReadNas is a Debian based Linux.
Hello All
I used to back up a Mssql database (about 55GB) to a samba share without
any problems. The samba server "Server-A" was running version 3.4.7
We just got one of those "Netgear ReadyNas3200" things and I tried to
backup up to a share there which sometimes works and sometimes not in
wich ca
Hello there
I just installed 3.5.2 and encountered the following. Compile worked all
right but "getent group" would not give back any results, though "getent
passwd" did list those AD users. The server runs as AD member and
winbind seems to work normally. "wbinfo -u" and "wbinfo -g" return the
des
Hello all
I tried for a couple of days now to get our samba domain hooked up with
an AD controller. I followed these instructions:
http://www.msadfaq.de/wiki/ActiveDirectory/trust_relationship_samba_ad
I've solved a couple of problems over the years but this is a hard nut
to crack.
The setup is
Hello there
I've just been trying to get a NetApp FAS2020, DataOnTap 7.2.5.1 to join
our domain. No luck so far . The PDC is samba 3.2.4 with ldap backend.
I created the account manually and when I try to join the NetApp I get
these in the samba logs.
[2008/11/14 08:32:48, 0]
rpc_server/srv_netl
Ich werde ab 12.05.2008 nicht im Büro sein. Ich kehre zurück am
23.05.2008.
In dringenden Fällen Elmar Pöpperl o. Michael Feige kontaktieren
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Hello everyone
I hope this is not off topic.
The samba + cups thing is driving me nuts.
Samba runs as PDC and print server.
Everything is fine, printing works, automatic driver download works etc.
Now I want only certain people to be able to stop a printer under windows.
After digging around a b
Hello all
Compiled 3.0.28 from source and get continuous core dumps. The machine
running as PDC continous to work though.
Core dumps are reproduceable and happen when, for example, I am trying
to connect to a share that does not exist as well as when I install a
new printer driver using the Mi
Hello there
This morning our main Samba server was pretty unresponsive running at a
30+ load average.
After digging a bit what I found in the logs was the following.
No data on inotify fd?!
[2008/01/21 07:02:59, 0] smbd/notify_inotify.c:inotify_handler(234)
That entry appears a billion zillio
Hi there
I just upgraded from 3.0.23d to 3.0.25b. The server acts as PDC and
print server.
The setup is that Win clients automtically download the printers from
samba. Worked all right so far.
Here is what I did.
Compiled the new version and installed it.
Stopped smbd and nmbd and copied eve
Hi there
After having posted a while ago about the trouble I had with 3.0.23 I
gave it another try with 3.0.23d
I installed the current version on our samba PDC and BDC while the
member server was still running 3.0.22. This setup has worked for a
couple of weeks with no issues.
I then upgr
ock files = /*.xls/*.doc/*.mdb
level2 oplocks = No
strict locking = No
log level = 1
What am I missing or am I getting too old for the job??
Help is greatly appreciated.
--
Best Regards
Robert Gehr
"Technological progress has merely provided us
with more efficient means fo
al users and groups via ldap.
I also have in my smb.conf:
winbind trusted domains only = Yes
What am I missing??
Thanks
--
Best Regards
Robert Gehr
"Technological progress has merely provided us
with more efficient means for going backwards"
~ Aldous Huxley
--
To unsubscr
Hello
I just upgraded our PDC from 3.0.22 to 3.0.23 with all the bells and
whistles.
I am running OpenLdap as a backend and did what's been written in the
Changelog regarding indexing.
The new version started up fine and worked all right. Netlogons, shares,
printing etc. I could also assign
Hello everybody
I am running two Domaincontrollers PDC and BDC both with an LDAP Backend
(Master and Slave) and another samba fileserver FS1 who is a Domain
Member. We have about 180 win clients (W2k and XP) on the network. We
are also running a w2k terminalserver (TS) with about ten clients
hook
Ich werde ab 05.06.2006 nicht im Büro sein. Ich kehre zurück am
30.06.2006.
Ich werde Ihre Nachricht nach meiner Rückkehr beantworten.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
rwx
default:other::---
User joe does not get listed by name, but only via its idmap ID.
Now the problem is, user joe has no access to directory "temp" even though he
should.
What have I done wrong??
Anyone any ideas??
Thanks for helping.
--
Best Regards
Robert Gehr
/usr/local/samba/sbin/smbd(smbd_process+0x145) [0x80d3b65]
#16 /usr/local/samba/sbin/smbd(main+0x82b) [0x82454eb]
#17 /lib/tls/libc.so.6(__libc_start_main+0xe0) [0x4020d500]
#18 /usr/local/samba/sbin/smbd [0x8077eb1]
--
Best Regards
Robert Gehr
"It you want to live a happy
x)
>
> The linker:
>
> ld -version
> GNU ld version 2.15.90.0.1.1 20040303 (SuSE Linux)
> Copyright 2002 Free Software Foundation, Inc.
> This program is free software; you may redistribute it under the terms of
> the GNU General Public License. This program has absolutely no war
.3.1 and ld gives
2.14.90.0.5 20030722 (SuSE Linux)
What am I missing here?
--
Best Regards
Robert Gehr
"It you want to live a happy life, tie it to a goal -
not to people or things."
~ Albert Einstein
o
/\ /_ o__
o* ~(_) ,>
.1 and ld gives
2.14.90.0.5 20030722 (SuSE Linux)
What am I missing here?
--
Best Regards
Robert Gehr
"It you want to live a happy life, tie it to a goal -
not to people or things."
DAP.
As far as I remember ther was no sambaSID such attribute in the 2.2.x LDAP
scheme.
Anyone knows how to solve that Problem??
Help is greatly appreciated.
Best regards
Robert Gehr
"What one man can invent, another can discover"
Hi all
After running samba 3.0.0 for a couple of days I get messages like this in
my logs which look a bit suspicious :-) to me.
Anyone knows what this is all about? The result ist that copy jobs etc. are
just signing off.
Sorry for not entering this in the bugzilla thing. I am not too famili
chines.
Even though the person can not print anymore he/she can still access
his/her private shares which are bound to proper authentication as well.
Any ideas
Best regards
Robert Gehr
"It is an act of evil to accept the state of evil as either inevitable or
final"
- Heschel a
27 matches
Mail list logo