search for: cromemco

...e thing. The other mistake is that there is no "force create group" parameter. The correct name of this parameter is "force group". So another change to your smb.conf is needed. Best regards, Axel Neumann ================================================================ Cromemco MPCT GmbH | Dietrich-Bonhoeffer-Str. 4 | D-61350 Bad Homburg Tel. Int+49-6172-967860 | Fax. Int.+49-6172-304519 E-Mail: amn@cromemco.com | Web: http://www.cromemco.com ================================================================

Hello, I am using Samba 2.0.3 on my FreeBSD 2.2.7 box. Works fine. It is already running for a few months with a small amount of windows95 users and last week we decided to move all our userfiles from our SCO box with visionfs over to the Samba machine. No problems so far. But, strange files are appearing in the directorys of the NT40 workstation users. Under Unix they look like Ne00: or Ne01: or

...ted to a Samba printer. Samba creates the empty file Ne01: in the directory where file resists. This bug has been reported under PR# 13685. I will now check if this bug has been fixed in Samba 2.0.3. Best regards, Axel Neumann =================================================================== Cromemco MPCT GmbH Tel: Int+49 6172 967860 Dietrich-Bonhoeffer-Str. 4 Fax: Int+49 6172 304519 D-61350 Bad Homburg E-Mail: amn@cromemco.com ==============...

...blem you have to advise the spooler to copy the file first into the spooling area before printing. An entry for SYSV printing in smb.conf would look like the following: print command = /usr/bin/lp -c -d%p %s; rm %s Axel Neumann =================================================================== Cromemco MPCT GmbH Tel: Int+49 6172 967860 Dietrich-Bonhoeffer-Str. 4 Fax: Int+49 6172 304519 D-61350 Bad Homburg E-Mail: amn@cromemco.com ========...

...already opened. So STRICT LOCKING is not necessary. It seems that Samba 2.03 has changed something in its locking behavior so that the application gets confused with the different lockings of a file. Best regards, Axel Neumann =================================================================== Cromemco MPCT GmbH Tel: Int+49 6172 967860 Dietrich-Bonhoeffer-Str. 4 Fax: Int+49 6172 304519 D-61350 Bad Homburg E-Mail: amn@cromemco.com =========...

.... In earlier releases of Samba (2.0.3 and before) I was able to start Outlook in the morning and sending mails in the evening without rebooting the NT. Right now I am back to Samba 2.0.3. Any clues? Best regards, Axel Neumann =================================================================== Cromemco MPCT GmbH Tel: Int+49 6172 967860 Dietrich-Bonhoeffer-Str. 4 Fax: Int+49 6172 304519 D-61350 Bad Homburg E-Mail: amn@cromemco.com =========...

...passwords but client uses encrypted password or vice versa - smbpasswd file is not setup correctly. Maybe this information (see also ENCRYPTION.TXT in the source distribution) helps you a little further. Regards, Axel Neumann =================================================================== Cromemco MPCT GmbH Tel: Int+49 6172 967860 Dietrich-Bonhoeffer-Str. 4 Fax: Int+49 6172 304519 D-61350 Bad Homburg E-Mail: amn@cromemco.com ==============...

...tly. If you doubt that the executables of Samba are not correct, you can download a binary version of Samba 2.0.5a from SCO. Please be aware that this version will not work on a SCO OS5 SMP system. Best regards, Axel Neumann =================================================================== Cromemco MPCT GmbH Tel: Int+49 6172 967860 Dietrich-Bonhoeffer-Str. 4 Fax: Int+49 6172 304519 D-61350 Bad Homburg E-Mail: amn@cromemco.com ==============...

On 17 May 99, Axel Neumann <amn@cromemco.com> had questions about DOS to UNIX Conversion: > It seems that a lot of people hate Windoze in such a way that they only > accept solutions that are not coming from M$. Maybe that's because the M$ "solutions" are crap, and much better alternatives already exist. &gt...

...a.org/listproc/ >Topics covered in this issue include: > > 1) strange share violation > by "Marek Les" <marek@ryston.cz> > 2) Re: Printing from UNIX to WIN? > by Kevin Ivory <Ivory@SerNet.de> > 3) AW: SAMBA digest 2177 > by Axel Neumann <amn@cromemco.com> > 4) Re: Paradox on a Samba share > by Paulo Almeida <seth@mail.telepac.pt> > 5) Samba and Quickbooks > by "Rickey Bell" <RickeyBell@TechnicalSolutionsSC.Com> > 6) Re: Security preferences with Samba 2.0.5 > by Kevin Ivory <Ivory@SerNet.de...

...tp://samba.org/listproc/ > Topics covered in this issue include: > > 1) Group-Shares > by Johannes Scherbaum <scherj@funkhaus.de> > 2) RE: Samba 2.0.3 > by Johan Roos <roos@byggdok.se> > 3) Printing Problems / SAMBA Digest 2072 > by Axel Neumann <amn@cromemco.com> > 4) I just want to thank you > by "Adilson G. Oliveira" <adilson@unimedsc.com.br> > 5) Re: An even more strange win95 browsing problem > by Hongwei Li <hongwei@morpheus.wustl.edu> > 6) Re: Samba 2.0.3 > by Herb Lewis <herb@chomps.engr.sgi...

When the world was much younger, Stephen L Arnold <arnold.steve@ensco.com> painted some strange hieroglyphs like this: >When the world was young, Axel Neumann <amn@cromemco.com> carved >some runes like this: >> I just want to inform you about a severe problem that I have >> found with Samba 2.0.5 installed on a SCO OpenServer 5.04. >[snip] >> INTERNAL ERROR: Signal 11 in pid 13646 (2.0.5) >[snip] ^^^^^^^^^ >I don'...

I am experiencing a problem with all time stamps having the same date and time stamp. I found this bug report http://us1.samba.org/listproc/samba/June1998/0239.html and see there is a fix. The question I have is has this issue been resolved in later versions of Samba code. It would be easier to upgrade than deal with a code change and re compilation. Scott Ranzal -------------- next part

On 07/29/2016 02:52 AM, Peter wrote: > On 29/07/16 18:10, John R Pierce wrote: >> also, try and scrounge another DDR2 SODIMM for that thing, according to >> my google search, it supports up to 2 x 4GB == 8GB, and you said you >> only have the stock 2GB. > > They are dirt cheap on ebay, from Hong Kong with free shipping. I would > go all the way and max it out. >

...m> >To: samba@samba.org >Subject: Re: Samba 2.0.5 Warning >Message-ID: <199907222204.SAA26419@sheffield.cnchost.com> >MIME-Version: 1.0 >Content-type: text/plain; charset=US-ASCII >Content-transfer-encoding: 7BIT > >When the world was young, Axel Neumann <amn@cromemco.com> carved >some runes like this: > >> I just want to inform you about a severe problem that I have >> found with Samba 2.0.5 installed on a SCO OpenServer 5.04. >[snip] > >> INTERNAL ERROR: Signal 11 in pid 13646 (2.0.5) >[snip] ^^^^^^^^^ &gt...

Donald H. Bennett, Jr. wrote: >Here is a problem which I hope someone can help me out on. We have three >SCO Unix Systems in our office. Two are running samba but the third keeps >on giving me core dumps. Here is a breakout of each computer. [snip...] >Computers 1 and 2 run samba with no problems at all. However, Computer 3 >gives me a core dump when ever I run the SAMBA startup

James A. Mutter wrote: >Does anyone know of any issues with 2.0.5 and SCO Openserver 5.0.5? A >friend told me that he had "real problems", but couldn't elaborate. >Is there something I should be aware of before I try this? >Thanks, >Jim Hi, As far as I know there are no problems with running Samba on a SCO system, beside the normal Samba configuration problems.

Mike Brodbelt wrote: >Hi, >I'm running Samba 2.0.6 here as our main file server. Authentication is >done against an NT PDC, and Samba is also responsible for printing. >I'm getting some odd files created which aren't being deleted. They are >all zero byte files, named after a network interface, so I assume they >may be temporary files which are not being deleted.

Hillel Bilman wrote: >I have a problem that if a user sends a file to be printed and checks >remotely and finds the printing of that file has been paused, that >user can't remove the pause as the system says he/she doesn't have >permission to do it. > >My smb.conf contains : >[global] > load printers = yes > printcap name = /etc/printcap > printing =

Michael Packer wrote: >Hello, >I've got a machine running SCO (Release 5.0) and am running samba version >2.03 (only version I could find already compiled for SCO). You can download Samba 2.05a directly from the SCO web site (http://www.sco.com/skunkware/net/index.html). It will work as long as do not have SMP installed. >My problem is when I print to a printer connected to