Displaying 4 results from an estimated 4 matches for "worsk".
Did you mean:
work
2014 Jan 06
0
getent passwd/group worsk but user authentication does not work (SAMBA4/SSSD) (Urgent request)
Hi Expert,
I need this help urgently, as I need implement this ASAP..
I Have installed Samba4 by using this
https://wiki.samba.org/index.php/Samba_AD_DC_HOWTO#Paths
Specifically, by using this :
/usr/local/samba/bin/samba-tool domain provision --use-rfc2307 --interactive
Now I am using bellow link to configure authentication with SSSD
2006 Dec 07
5
CISCO 2600 - VWIC 1MFT-E1
Hi to all,
I got a Cisco 2651XM wired to an E1 PRI.
What I want to do is to pass all incoming calls to my asterisk.
This is my actual conf:
http://pastebin.ca/270677
with this I'm able to call my number from outside, but the call stop on the
2600, infact I can hear the tone, but I'm not able to forward calls to my
asterisk.
Anyone got an idea of my errors?
Thanks to all.
--
.:FaberK:.
2003 Dec 01
0
No subject
...List-Archive: <http://lists.samba.org/pipermail/samba/>
Date: Mon Sep 10 07:55:01 2001
X-Original-Date: Mon, 10 Sep 2001 16:58:15 +0200
Hi all,
i'm recently passed to 2.2.1a, but this prble was alway spresente
also with 2.2.0 and 2.0.7 (statiscs say lower times than now).
Three pces worsk on a share, with a sort of db (IDOL-VI) and lock soem
files to upgrade.
The system works well, but sometimes, not even periodci, the three
sysems blocks, and on th elogs the only things that i see, is this :
[2001/09/10 11:37:30, 0] smbd/oplock.c:request_oplock_break(997)
request_oplock_break: n...
2003 Dec 01
0
No subject
...nel oplocks = no' if you run a 2.4 kernel (linux)
dragos
On Monday 10 September 2001 05:58 pm, Mailing Manager wrote:
> Hi all,
> i'm recently passed to 2.2.1a, but this prble was alway spresente
> also with 2.2.0 and 2.0.7 (statiscs say lower times than now).
> Three pces worsk on a share, with a sort of db (IDOL-VI) and lock soem
> files to upgrade.
> The system works well, but sometimes, not even periodci, the three
> sysems blocks, and on th elogs the only things that i see, is this :
>
> [2001/09/10 11:37:30, 0] smbd/oplock.c:request_oplock_break(997)
&...