similar to: smbclient failing due to switch MAC addr table timeout

https://bugzilla.samba.org/show_bug.cgi?id=3794 Basically spnego fails with vista and you have somehow force to downgrade to ntlmssp. To samba devels: I see the bug submitter sent 2 emails to samba-technical that went unanswered. I don't understand why, the issue is real and blocking. Maybe you have some info that there will be changes in vista final which will solve the issue

My systems: rh61, 2.2.14 + smbfs-nls.patch. I refer to 2.0.7pre3 as 2.0.7 === 1) "ls" of an empty dir 1a) 1.9.18 doing "ls" to an empty samba dir: smb: \> ls 49550 blocks of size 16384. 33754 blocks available 1b) 2.0.7 doing "ls" to an empty samba dir: smb: \> ls ERRDOS - ERRbadfile (File not found.) listing \* <=======

Hello OPUS, It appears to me that multi-frame packets are not supported by opus_demo.c (e.g. 30ms packest containing 3 10ms frames), can you confirm. However RF6716 does support such packets. Thanks Cliff -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/opus/attachments/20131121/56bab79a/attachment.htm

Daniel Ballenger wrote: > I'm pretty sure that the protocol used by icecast is TCP so you also > have the overhead from TCP to add, though in the end, the overhead > probably isn't enough to be really noticed. > > -Daniel Do that for a few hundred connections, and the overhead can add up to something more significant. I'm basing this on a theoretical maximum of an

https://bugzilla.netfilter.org/show_bug.cgi?id=1164 Bug ID: 1164 Summary: FTP NAT fails in a specific scenario after upgrade to kernel 4.7+ Product: netfilter/iptables Version: unspecified Hardware: x86_64 OS: Fedora Status: NEW Severity: normal Priority: P5

At the moment I have 2 network connected in a VPN and I'm planning to extend this. Actual status: Network A has a public IP Network B is behind a provider-scale NAT. Actually I'm using openvpn with a single UDP connection from B to A, and hosts inside Network A can communicate with B. I tried with tinc, and I saw tinc has to go TCP-Only for accomplish this. This is because Tinc

Looks like this question was indeed solved prior (finally found the searchable archive). Solution is to add ssl CA certDir=/usr/share/ssl/certs to the smb.conf file (or appearently any other directory for that matter). Jamin W. Collins > -----Original Message----- > From: Giulio Orsero [mailto:giulioo@pobox.com] > Sent: Monday, April 16, 2001 1:02 PM > To:

We have ISDN PCI Adapter from Billion(using mISDN). When we connect it to the PSTN the incoming calls are OK. When we try to make a call we can't do that because the ISDN port is Down: CLI> misdn show port 1 BEGIN STACK_LIST: * Stack Addr: 40400001 Port 1 Type TE Prot. PMP L2Link DOWN L1Link:DOWN Idx: 0

Hello, i need help because my samba server is not working. I have a Samba TNG server which SUCCEEDS in authenticating all users stored in a LDAP Directory. They (admins before me) installed in a RH7.3 Box the rpms of Samba HEAD 2.2.3a which *sholud* make available some shares (e.g. users' home) while authenticating against the TNG. The previous version of Samba HEAD did work but since its

Hi. I'm trying to estabilish a trust between Win2k configured in mixed mode with SAMBA 3 server. I followed instructions from SAMBA HOWTO, however the trust is not working - I don't have any clue why is it not working - I didn't find any usefull message in SAMBA logs - I will continue debugging today evening. I want to achive that users from SMBDC domain can login into computers

Hello everyone, this is my first post, so please be kind :) I've a working Samba AD DC 4.7.6 installed on Ubuntu 18.04 I can join Windows Machine, manage everything with RSAT. Yesterday I tried to estabilish a Domain Trust between my Samba Domain and a Windows 2008 domain, using "Active Directory Domains and Trusts". The Win2008 AD is one-way on outgoing trust, and my Samba is

I downloaded nilo and oskit from www.nilo.org. Added pcnet32.c linux-2.0.39 driver to oskit. Compiled nilo with pcnet32 and produced boot floppy image. Use it inside vmware vm. My aim is to be able to test pxelinux using vmware+nilo and not a real machine. Floppy starts, detects nic, receives ip from dhcp server, requests boot image to tftpd-hpa, then crashes when talking to tftp. Is

SAMBA_2_0 as of 1 mar 2000, 11:00 GMT rh61 kernel-2.2.14. 1) smbpasswd the -x switch was added but now: a) you can't do "smbpasswd -an user" anymore, it asks for password. b) smbpasswd -n user -> seg fault 2) ./configure --with-utmp: make all ... Compiling smbd/connection.c smbd/connection.c: In function `utmp_update': smbd/connection.c:349: structure has no member named

3.0.25rc1 has the same issue. On Fri, 06 Apr 2007 22:52:05 +0200, Giulio <giulioo@gmail.com> wrote: >Vista32 >3.0.25pre2 (I understand vista patches for "share level" are already in) >security = share (with "valid users" on share definition) >host msdfs = no > >user/pass in smbpasswd file. > > >If I use "connect network

Suppose I have the latest and greatest e2fsprogs. >From reading the docs I understand that 1) boot ext3, clean umount - you can remount ext3 or ext2 2) boot ext3, unclean umount - you can remount ext3 - you can e2fsck and remount ext2 Does this mean that normal linux init script e2fsck will do it, in case fstab says ext2? Or you should make sure to run e2fsck by hand with -f? 3) boot

Hello! I've configured samba with winbind and pam_winbind module to authenticate users that connect to my linux box against MS AD. Works like a charm. If a user exists both in AD and locally, login should assume local users. Again, it works pretty well (It seems at least with my current config). If my AD server goes down for any reason, local users should be able to login. For example, root

I made some tests with smbclient and gzip, and it seems to me that what I'm doing should be safe, but I'd like to know if this kind of input and output redirection has some "hidden" drawbacks/problems: may it cause corruption of output files? backup: smbclient '\\server\share' -Tc - | gzip > file.tar.gz restore: gzip -dc file.tar.gz | smbclient

I have a win dir with 143 files and 3 dirs. smbclient '\\server\dir' -Tc file.tar --> "tar: dumped 146 tar files" smbclient '\\server\dir' -Tx file.tar --> "total of 143 tar files restored to share" When tarring it reports files+dirs, when untarring it reports files only; but the data is exactly the same: 143 files and 3 dirs, they are all tarred and

Local machine is CentOS 5.4, with samba 3.5.2 rpms from sernet. Remote machine is samba 3.0.something set up with share level security. On local machine: $ smbclient '\\srv\shr' -U% Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.0.30-1abc] Server not using user level security and no password supplied. Segmentation fault $ gettimeofday({1271431229, 455560}, NULL) = 0 select(10, [8 9], [],

Since the release of the first 2.0.x (jan1999) I noted that smbclient '\\server\share' -Tx filename.tar was terribly slow. smbclient '\\server\share' -Tc filename.tar is as fast as 1.9.18. If I use smbclient from 1.9.18 the performance is high (with the same target pc). These are some tests with: - Win98pc - lan 10Mbps - samba-2.0.5-pre4/rh60 - a dir containing 1,2MB in 52