IPSI conference wrote:
Dear Dr. Samba,
Priceless!
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
it easy to identify the source and inform the
party of the infection. In such a case the owner is nearly always a
victim of the infection and not an intentional propagator and will
appreciate the tip.
Ray Simard
--
To unsubscribe from this list go to the following URL and read the
instructions
On Monday 27 January 2003 16:30, Michael Heironimus wrote:
On Mon, Jan 27, 2003 at 03:46:10PM -0800, Daniel Fenwick wrote:
The better solution is to block attachments to the list. That eliminates
almost all viruses as well as all the other junk that floats around in
attachments.
Except
. */
if (tcount nwritten+numtowrite) {
DEBUG(3,(Client overestimated the write %d %d %d\n,
Ray Simard
[EMAIL PROTECTED]
communications and don't use subnet broadcasts - unless I'm mistaken, a
very real possibility. :-)
Does anyone have a hint on what might cause this, how to troubleshoot it more
fully, or if it's really nothing to worry about?
Ray Simard
--
To unsubscribe from this list go to the following URL and read
I checked a little more carefully and noticed that many, though not all, of the
occurrences
of failed oplock breaks are followed by the message that you see here, ... Deleting
it to continue.
Looks a little scary; does it mean it's deleting the oplock or deleting the file?
Here's a chunk from
On Monday 09 August 2004 08:45, Prianggada I Tanaya wrote:
There are several things that might cause problems here.
...
$ smbclient -U% -L 10.1.45.12
added interface ip=10.1.45.13 bcast=10.1.255.255 nmask=255.255.0.0
error connecting to 10.1.45.12:139 (Connection refused)
Error connecting to
mentioned in the
previous note.
If I learn anything out of this that might be helpful to others, I'll post it
here.
Thanks again,
Ray Simard
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
I hope someone can shine some light here.
Per the docs, the ntconfig.pol file resides in the netlogon share, and it
seems to work fine for any policies that pertain to a user or all users
(Default user). But nothing I've tried has gotten policies for computers to
work. Nothing that is set in
