Displaying 4 results from an estimated 4 matches for "successless".
Did you mean:
successess
2008 Dec 04
2
Packet size limit for HDLC?
...MTU and MRU. They insist to use a size of 1500.
Since, using CAPI or ISDN4Linux (not via asterisk), pppd is working
well with the MTU/MRU value of 1500, I assume, there is some packet
size limitation in the asterisk part (including app_pppd).
I tried to find any too small buffer or similar, but successless.
May I ask you, where do you think, the limitation does come from:
- from app_pppd (I don't think so)
- from libpri
- from chan_dahdi
- from the dahdi kernel modules
- from the asterisk kernel
Any hint is welcome!
Regards,
Roger.
2016 Apr 16
7
After Update to 4.2, Samba is unusuable as member server / No user and goup resolution
Hello everybody,
I've bin running Samba as a AD member server for ages (Debian stable).
After the last update to 4.2, I just can't get it to work.
Symptoms: unable to map AD user / groups.
After two days of successlessly fiddling (and moving all data to another
server with still Samba 3.6, which I will definitely NOT update at the
moment), I decided to purge my Installation and start over again like
described in
<https://wiki.samba.org/index.php/Setup_Samba_as_an_AD_Domain_Member>
So now my setup is (a...
2016 Apr 19
0
After Update to 4.2, Samba is unusuable as member server / No user and goup resolution
...4.2016 um 19:08 schrieb Patrick G. Stoesser:
> Hello everybody,
>
> I've bin running Samba as a AD member server for ages (Debian stable).
> After the last update to 4.2, I just can't get it to work.
>
> Symptoms: unable to map AD user / groups.
>
> After two days of successlessly fiddling (and moving all data to another
> server with still Samba 3.6, which I will definitely NOT update at the
> moment), I decided to purge my Installation and start over again like
> described in
> <https://wiki.samba.org/index.php/Setup_Samba_as_an_AD_Domain_Member>
>
&...
2016 Apr 20
0
FW: FW: Domain member seems to work, wbinfo -u not (update10)
...rver for ages (Debian
> stable).
>
> > > > After the last update to 4.2, I just can't get it to work.
>
> > > >
>
> > > > Symptoms: unable to map AD user / groups.
>
> > > >
>
> > > > After two days of successlessly fiddling (and moving all data to
>
> > another
>
> > > > server with still Samba 3.6, which I will definitely NOT update at
> the
>
> > > > moment), I decided to purge my Installation and start over again
> like
>
> > > > d...