similar to: winbind stops authenticating until a restart.

As of RC3 and RC4, I've noticed that winbindd's wb_getpwuid function is using the form <FQDN-domain><winbind-seperator><username>, and before, it was simply <NetBIOS-domain><winbind-seperator><username>. The net effect of what I'm seeing is that users which have a UNIX account locally on the samba box and also a domain account are being

I'm hoping someone can shed some light on this one. Ever since beta3 I've been unable to get wbinfo to work properly. I finally worked around it today, and it seems that with the disable netbios = yes parameter in my smb.conf file, I get no results. Commenting out that parameter seems to work fine. It looks like the DNS queries for DCs is unsuccessful without NetBIOS enabled. I'm

I''ve just started to recently look at CBQ and HTB, but I''ve been wondering whether or not something like the following is possible: I''ve got two external links: +--+ | |-----ISP1 |FW| | |-----ISP2 +--+ One link has a bandwidth cap, and the other doesn''t. What I want to do is, punt all outbound traffic out via ISP1

While testing the latest Samba3.0.0beta3, I notice that if I don't specify a password server winbind appears to look it up via DNS, and with two DCs, picks one. However, my krb5.conf specifies a particular Kerberos server (one of the two DCs), and so occasionally, winbind will pick the first DC, and kerberos uses the other. When this happens, I can't seem to connect to any shares on the

Hi! I''ve got two FreeS/WAN gateways setup, with one subnet<->subnet tunnel setup, which is working fine. I''ve setup iproute2 to route anything for either subnet via the ipsec0 device using a src address of the local interface. This is to force locally generated traffic (ie, traffic generated on the server) to go through the VPN, rather than out with a source IP of the

hi all, Iam using the following CBQs to limit the FTP bandwidth pease tell what changes are rquired to make it work.... tc qdisc del dev eth0 root tc qdisc add dev eth0 root handle 1:0 cbq allot 1514 avpkt 1000 bandwidth 100Mbit tc class add dev eth0 parent 1:0 classid 1:1 cbq allot 1514 bandwidth 100Mbit rate .4Mbit weight .4 prio 2 maxburst 20 cell 8 avpkt 1000 tc class add dev eth0

Hello ALL, is there a way to have a device independent qdisc, or a qdisc on some kind of virtuall interface? Background: I have a 5-Interface-Router with one Internet-Uplink. The Router should connect the clients on the other Interfaces to the Internet and to each other client. As i understood the hole TC stuff i can only get influence of outgoing traffic. In my case i can reduce the traffic of

OS is smeserver, based on CentOS/RHEL 4. After update to samba 3.0.25b (included in RHEL U6) users who had "mapped" their home in Network places were unable to access the share. All other shares worked. On every attempt a line similar to the following was logged: Feb 14 10:11:49 nethservice smbd[6258]: '/home/e-smith/files/users/FRANCESCA/home' does not exist or permission

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have built RPMs of samba3.0.0beta3, which are parallel-installable with samba-2.2.x (for easy testing, though you can change that by rebuilding the srpm with other options) for Mandrake 8.1 through 9.1, which are available on my site. I hope to get these up on the samba ftp servers soon, but if you desperatly need packages, grab them from the

Hi - [problem] mount.smbfs is not working on 3.0.0beta3; it has been working thru 3.0.0beta2. When I re-install 3.0.0beta2, it works again. [configuration] *Linux host <hanako> Linux version 2.4.20-4GB-athlon (root@Athlon.suse.de) (SuSE Linux 8.2)) #1 Fri Jul 11 20:16:51 UTC 2003 *samba-3.0.0beta3 complied from source, with configuration option '--with-smbmount'. (same

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This patch is against samba-3.0.0beta3 (tested), but will also apply correctly to 3.0.0 (release) It makes wbinfo ask for a password if there is no password on the command line. So: wbinfo --set-auth-user=Administrator Will make it prompt Password: This is to make it easier to script wbinfo for nas appliances using expect to allow passwords with

Hi - My messages may not be reaching this list. Would someone at least confirm receipt of this message even if you have no suggestions/ comments re its content? I have sent several messages concerning mount.smbfs and I guess no one is using smbfs to mount a Windows machine -or- no one has encountered my problem. To recap the problem and give a solution: [problem] mount.smbfs is not working on

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Samba Team is proud to announce the availability of the third (and possible last) beta release of the Samba 3.0.0 code base. While we are significantly closer to the final release, you should be reminded that this is a non-production release provided for testing only. If all goes well, we will move onto a series of Release Candidate (RC)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Samba Team is proud to announce the availability of the third (and possible last) beta release of the Samba 3.0.0 code base. While we are significantly closer to the final release, you should be reminded that this is a non-production release provided for testing only. If all goes well, we will move onto a series of Release Candidate (RC)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Samba Team is proud to announce the availability of the first release candidate of the Samba 3.0.0 code base. A release candidate implies that the code is very close to a final release, but remember that this is still a non-production snapshot intended for testing purposes. Use at your own risk. One of the main additions in this release is

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Samba Team is proud to announce the availability of the first release candidate of the Samba 3.0.0 code base. A release candidate implies that the code is very close to a final release, but remember that this is still a non-production snapshot intended for testing purposes. Use at your own risk. One of the main additions in this release is

Hello I am currently setting up a new domain structure at work, and am trying to set up samba to authenticate against my Active directory domain. What I am having trouble doing is joining the Linux system to the domain. The system is running Redhat 8.0, no updates with samba-3.0.0beta3 Here is the error I get [2003/07/29 09:32:53, 3] libads/sasl.c:ads_sasl_spnego_bind(190) got

By logging into a smbd server with the username "HAENGINEERS\KMR", we are able to cause a smbd panic every time. Other usernames ("HAENGINEERS\_TestME") work. The stack trace is below, full logs and smb.conf are available on request (don't want to saturate the list.) I can't post to bugzilla as I can't register a new account as my incoming mail is crippled by

Hello, I originally posted this on samba-technical (http://lists.samba.org/pipermail/samba-technical/2003-July/046076.html), but I just verified that I'm also seeing the same error message with samba-3.0.0beta3. I have not tested if I'm also getting disconnects and Word saving problems that way. But, people using 2.2.7 must have also seen this. Here are some messages I've seen in

Hi, 'smbd' and 'nmbd' do behave well however 'smbclient' does not, so some of the other binaries neither i suppose. Running 'smbclient -s /etc/samba-pdc/config' gives me: params.c:OpenConfFile() - Unable to open configuration file "/opt/samba-3.0.0beta3/lib/smb.conf": No such file or directory bin/smbclient: Can't load