similar to: Samba 2_2_alpha3

Folks, Greetings. I just wanted to take a few moments a give everyone an update on the plans for the 2.2 branch. First we would like to thank everyone who has provided feedback regarding the 2.2.3a release. The positive feedback has been encouraging and the bug reports are proving to be very fruitful. Jeremy, Herb, and myself are planning on to continue development on the SAMBA_2_2 cvs tree

i've managed to catch the exploding connections database in the act. i was able to attach gdb to the smbd while it was going crazy: (gdb) bt #0 0xf55da in tdb_expand () #1 0xf5787 in tdb_allocate () #2 0xf6554 in tdb_store () #3 0x6534 in claim_connection () #4 0x406a2 in make_connection () #5 0x1e105 in reply_tcon_and_X () #6 0x3e256 in switch_message () #7 0x3e8c7 in chain_reply ()

Hi Jerry, It seems that the "samba-2.2.5-printing.patch" has only fixed the problem for PCL drivers. With PS drivers (Laserjet 4050 PS) are the duplex & tray settings still missing. Best regards, Khiem -----Urspr?ngliche Nachricht----- Von: Glen Gibb [mailto:grg@ridley.unimelb.edu.au] Gesendet: Mittwoch, 28. August 2002 07:41 An: Gerald Carter Cc: Samba Betreff: Re: [Samba]

FYI... I've just posted a snapshot of the current SAMBA_2_2 source code (tagged release-2-2-6pre2). This includes all of the post 2.2.5 printing fixes as well as fixing some other bugs (such as VxFS quota support). Please test and report back your experience. There have been some updates to the Mandrake packaging thanks to Buchan. We are not building RPMS or *debs for this pre-release.

Heads up everyone, Source release will be on download mirrors shorly. This is provided as a non-production release of the future 3.0 Samba codebase for testing purposes only. Use at your own risk. Now that I've cleared by conscience... :-) -- enjoy, -- The Samba Team Changes in alpha20 - Rework the 'guest account gets RID 501' code again... - Change

Just tried the latest cvs samba_2_2 (trying to avoid the winbind memory leak thing). It configured, compiled and installed fine, but when it came up there was an issue. When my Windows users (Win98 ad Win2K) went into explorer, they could see no names on the folders in samba shares, just blank folders. I quickly put it back to the older 2.2.2 configuration and everyone is back to normal. Was

Here's a rollup patch for most of the printing fixes in SAMBA_2_2. Issues fixed are * change notification never gets called on a SetPrinter() * alignment bug in marshalling PRINTER_INFO_2 causes problems viewing printer properties from win2k/XP clients * devmode unmarshalling bug causes ACT! 2000 on 2k client to fail to print Enjoy. Feedback welcome if this fixes (or does

Sure thing: cvs -d :pserver:cvs@pserver.samba.org:/cvsroot login <password is cvs > cvs -z5 -d :pserver:cvs@pserver.samba.org:/cvsroot co -r SAMBA_2_2 samba this will grab samba_2_2 and place it in a directory lableled samba. leaving out the SAMBA_2_2 grabs HEAD. you can get other modules as follows: SAMBA_2_2 HEAD APPLIANCE_HEAD APPLIANCE_TNG there are others but I haven't tried

FYI.... I've posted a patch file which contains the major spoolss fixes in the SAMBA_2_2 cvs tree. These include * security descriptor parsing fix for Win2k clients * correct access checks for modofying forms using a print server handle * add check for 0 length printer data in EnumPrinterDataEx() * fix alignment/offset bug in EnumPrinterDataEx() * fix bug in DeletPrinterDriver() so that

Sorry, not sure which list this should've gone to, but, I didn't notice any further info on the profile directories with 000 for permissions with Win2k SP1 and Samba_2_2 tree since Jeremy last asked for a log level 10. Was going to get him one of those with the current CVS tree code. Thought you'd like to know that yesterday's CVS snapshot I downloaded had profiles being created

FYI... We've put up a snapshot of the current SAMBA_2_2 code as 2.2.6pre1 for testing. The distribution is available from http://download.samba.org/samba/ftp/pre/samba-2.2.6pre1.tar.bz2 ( a gzipped version is also available ). This is a non-production release made available for testing purposes only. The relavant section of the release notes follow. The full test is available from

Hi List, I'm using Samba 3.0.1 as PDC and Openldap 2.1.23 as backend on a Suse 8.2 System, both are build from scratch. Nearly everything is fine, expect I'm not able to change the security setting of subfolders on my shares via my Win2k box. More details: Changing the security setting of my top level shares (created in smb.conf) works fine with the SRVMGR, but everytime I try to

Hi, I have an R script (transferred from SPLUS) and would like to compile a standalone EXE (or DLL) for WINNT. Would somebody know how this works or how it could be done ? Thanks so much for any hints and suggestions; best regards F. Falk Huettmann Geography Dept.-Earth Science- 2500 University Drive N.W. University of Calgary Calgary AB, T2N 1N4 CANADA Email: falk at ucalgary.ca Tel. 403

Hi, I implemented a samba(3.0.14a-Debian) server here on my network. But i'm having problems with 2 stations. One is a win2k(profissional) and the other is a win 2k server (working like a station). When i tried join in a domain using the win2k(profissional) i receive the msg: unknown interface The strange is that it is happening only with this win2k station. I have others stations with

---------- Forwarded message ---------- From: wally.hall@gmail.com <wally.hall@gmail.com> Date: Apr 27, 2006 4:22 PM Subject: Conistent problem with clients joining domain To: Hey everyone, firstly thanks for your time, I've spent hours, a lot straight days too, for the last couple of weeks trying to solve this issue. The only thing (afai can see) I've got left is asking the

Gentlemen, I could not join Win2K station into PDC Domain. I get the message: "The specified user does not exist!" when I tried to join. I read a lot how-to's and all procedures that is available in the web and still not working. In the same network I have Win98 working fine. Any help will be appreciated. Thanks in advance ... The procedures that I followed to join Win2k box in

Hi folks, today I tried to switch from a samba 2.2.2 PDC to a samba 2.2.7 PDC. Everything semed to be working fine with smbclient. Windows user couldn't log on, but with following differences: * users belonging to the domain admin group could log on from Win2k boxes * normal users couldn't log on from win2k boxes, with the usual "check if you didn't mis-type

On Thu, 6 Jun 2002 Volker.Lendecke@SerNet.DE wrote: > One thing that struck me today is the fact that if you copy the > secrets.tdb to another machine, smbd will generate a new SID for the > machine and hand this out on lsaquery. The only way to create a working > BDC with 2.2.5 is to manually generate a MACHINE.SID from the PDC with > rpcclient/lsaquery, copy this over to the BDC

I hope this doc below helps out. But from what I have seen it looks like you created the machines accounts but did not create the smbpasswd for the machine accounts. See docs below Machine accounts: the manual approach As noted, Samba will not allow you to add an entry to the smbpasswd file (user or machine) unless there is a existing UNIX account for that user. So the first step is to create an

I've recently figured out something that others may find useful...we have an ftp proxy, and I couldn't get cvs to work through it. I finally got wget working, and can now mirror my source to the current samba_2_2 version by downloading only the newer files. Then I can run ./configure, etc to update my system. ----------------------------------------------------- The command line is in